Steve Faulkner

Steve was the Chief Accessibility Officer at TPGi before he left in October 2023. He joined TPGi in 2006 and was previously a Senior Web Accessibility Consultant at vision australia. Steve is a member of several groups, including the W3C Web Platforms Working Group and the W3C ARIA Working Group. He is an editor of several specifications at the W3C including ARIA in HTML and HTML Accessibility API Mappings 1.0. He also develops and maintains HTML5accessibility and the JAWS bug tracker/standards support.

Detecting if images are disabled in browsers

I received an email from an old friend and colleague pointing out that with images disabled in the browser, the support information in the data tables on HTML5Accessibility.com disappears. An…

October 21, 2011Development
CSS, HTML, ARIA, browsers, assistive technology and interoperability

A number of issues are being debated in accessibility circles at the moment. These primarily revolve around how browsers and assistive technology interpret and represent HTML semantics via accessibility APIs…

October 17, 2011Development
Opera doesn’t work with screen readers – does it matter?

One thing that should be obvious to anybody who has read my recent posts Rough Guide: browsers, operating systems and screen reader support and a Brief history of browser accessibility…

October 14, 2011Development
Browser & Assistive Technology Tests Redux

I am always looking back through the TPGi blog archives to find tests I have done in the past, as often I have forgotten where the tests reside. To remind…

October 6, 2011Development
Brief history of browser accessibility support

The development of a ‘Brief history of browser accessibility support‘ was prompted by Google’s Evolution of the Web interactive infographic. I was dazzled by its coolness, but noticed that amongst…

October 5, 2011Development
Google Chrome Frame – still an accessibility black hole?

Back in 2009 I wrote Google Chrome Frame – accessibility black hole, now 2 years on what has changed? This quick revisit has been prompted by some recent tweets.

September 23, 2011Development
HTML5 Accessibility Chops: the figure and figcaption elements

The figure and figcaption elements are 2 of the new elements in HTML5. Together they provide the promise of being able to mark-up, with meaning, the structure and relationship between…

August 23, 2011Development
HTML5 Accessibility Chops: SVG text alternative example

The W3C HTML5 specification contains an SVG (Scalable Vector Graphics) based interactive Venn diagram. The diagram illustrates the relationship between HTML content categories. Currently the content and interactivity of the…

August 17, 2011Development
Accessibility Notes: 2nd August 2011

Bits & Bobs about web accessibility.

August 2, 2011Development
HTML5 Accessibility Chops: ARIA landmark support

The ARIA landmark roles can be used in HTML5 to markup regions of a page. Landmark roles add a new means to navigate page content for users of supporting assistive…

July 11, 2011Development
HTML5 Accessibility Chops: form control labeling

There are 2 methods of labelling a form control using the HTML label element. You can wrap the control inside the label element or you can include the for attribute…

July 4, 2011Development
Web Accessibility Toolbar 2011 – Updated

We have been working on bug fixes to the Web Accessibility Toolbar 2011, the update is now available for download, includes the latest version of aViewer.

June 29, 2011Development
aViewer beta – updated

Refer to: aViewer 2013

June 28, 2011Development
HTML5 Accessibility Chops: Block Links

It is conforming in HTML5 for links to include block level elements such as headings and paragraphs, this was forbidden in previous versions of HTML. A recent article by @feather…

June 17, 2011Development
HTML5 Accessibility Chops: Conflicting advice and requirements

HTML is currently defined in multiple documents, each purporting to be THE definition of HTML/HTML5. The documents are developed, published and maintained by 2 separate organisations. The 2 organisations have…

June 13, 2011Development
HTML5 Accessibility Chops: ARIA & validation

I tweeted the other day, suggesting people switch to the HTML5 doctype as the use of ARIA is conforming in HTML5. As things stand, if ARIA roles, states and properties…

June 2, 2011Development
HTML5 Accessibility Chops: the alt decision

A recent decision by the W3C HTML working group has caused much discussion and some consternation within the accessibility community and wider web development community.

April 27, 2011Development
HTML5 Accessibility Chops: Just use a (native HTML) button

Many User interface widgets can be developed using HTML, CSS and JavaScript, in some cases developers build custom versions of native HTML controls because they cannot achieve the exact look…

April 19, 2011Development

ARC Platform Overview

ARC Analytics

ARC Content

Platform & Programs

Companion Tools

Start Now

Solutions Overview

Accessibility Services

Conformance

JAWS Solutions

Solutions by Org Size

Resources

Conformance & Compliance

Top Content

Free Tools

Steve Faulkner

Detecting if images are disabled in browsers

CSS, HTML, ARIA, browsers, assistive technology and interoperability

Opera doesn’t work with screen readers – does it matter?

Browser & Assistive Technology Tests Redux

Brief history of browser accessibility support

Google Chrome Frame – still an accessibility black hole?

HTML5 Accessibility Chops: the figure and figcaption elements

HTML5 Accessibility Chops: SVG text alternative example

Accessibility Notes: 2nd August 2011

HTML5 Accessibility Chops: ARIA landmark support

HTML5 Accessibility Chops: form control labeling

Web Accessibility Toolbar 2011 – Updated

aViewer beta – updated

HTML5 Accessibility Chops: Block Links

HTML5 Accessibility Chops: Conflicting advice and requirements

HTML5 Accessibility Chops: ARIA & validation

HTML5 Accessibility Chops: the alt decision

HTML5 Accessibility Chops: Just use a (native HTML) button