Examples of ‘skip links’ on some bank sites

Posted on August 21, 2012 by Steve Faulkner

While discussing long descriptions on the HTML working group mailing list I took a look at how some sites provide skip links as an example of contingent visible display of content as a more palatable design concept for some accessibility features, as against always displayed or always visually hidden. Continue reading →

Posted in accessibility testing, WCAG 2.0, Web Accessibility | 3 Comments

Notes on accessible CSS image sprites

Posted on August 20, 2012 by Steve Faulkner

The issue of CSS image sprites has been raised again on the Web Accessibility Initiative Interest Group mailing list. Here is the advice we provide on the issue:

Continue reading →

Posted in Assistive Technology, CSS, Firefox, Google Chrome, high contrast, HTML, HTML5, Internet Explorer, JavaScript, WCAG 2.0, Web Accessibility | 13 Comments

latest aViewer alpha 2012

Posted on July 27, 2012 by Steve Faulkner

Refer to: aViewer 2013

Posted in accessibility testing, HTML5, IAccessible2, Internet Explorer, MSAA, tools, UI Automation, WAI-ARIA, Web Accessibility | 4 Comments

W3C HTML and WHATWG HTML ‘split’ effect on HTML Accessibility?

Posted on July 23, 2012 by Steve Faulkner

The recent formalisation of the ‘HTML split’ between the W3C and the WHATWG, is not news to those working in either group. Work continues pretty much as it has, prior to Hixie’s communication to the WHATWG.

Continue reading →

Posted in HTML, HTML5, W3C, Web Accessibility | 10 Comments

Google Chrome accessibility update

Posted on July 16, 2012 by Steve Faulkner

Google Chrome has come a long way in the past 3 years, and the improvements definitely extend to accessibility support. The Google Access team have been working hard to make Chrome more accessible to a range of users.

Google Chrome accessibility

You can read about the technical details of Chrome keyboard, low vision and screen reader support in the Accessibility Technical Documentation. Suffice to say from a technical view point Chrome is almost up there with Internet Explorer on Windows, but still has a way to go to reach Firefox’s level of accessibility support. On OSX and iOS it’s close to Safari’s level of support.  On Linux Firefox is still the only choice. The technical improvements strongly suggest Chrome is nearing practical support for users with disabilities, but that can only be confirmed by the users themselves.

Chrome still has a way to go in regards to HTML and ARIA implementation and improved support for new HTML5 features is required, but the commitment is there and the work is being done. The people responsible deserve congratulations for their efforts to date and the hope is it will continue apace. Like browser development in general, accessibility support involves continuous work.

Chrome Frame

Chrome Frame pretty much inherits all improvements in HTML and ARIA support found in Chrome. A notable exception is that it does not support Windows High Contrast mode as this is provided in Chrome by a High Contrast extension.

Further Reading

Posted in Google Chrome, high contrast, HTML, HTML5, Web Accessibility | 3 Comments