Category Archives: HTML 5

HTML5 Accessibility Chops: data for the masses

One of the stumbling blocks for working out what the effects on the accessibility of new (and old) HTML5 features is not having any publicly accessible usage data. It is difficult without data to argue for the inclusion of features … Continue reading

Posted in Accessibility, HTML 5, HTML5, W3C, Web Accessibility | 11 Comments

Is NVDA Strictly a Web Accessibility Screen Reader?

Last week, Jamie and Mick of NVDA announced that their open source, free screen reader organization is in need of funding: Blind Ambition Plea for Funds to Keep Free Software Project Alive NVDA is perhaps the cream of the crop … Continue reading

Posted in Accessibility, accessibility testing, Assistive Technology, Firefox, General, Google, Google Chrome, HTML, HTML 5, IAccessible2, Internet Explorer, JAWS, microsoft, mobile, Mozilla, MSAA, NVDA, open source, Opera, Safari, Screen Readers, WAI-ARIA, WCAG 2.0, Web Accessibility, Window Eyes | Tagged , , , , | 18 Comments

HTML5 canvas accessibility discussions 2009-2011

Charles Pritchard has taken the time to provide an email overview of Canvas accessibility discussions which have taken place on the public-canvas-api over the past 3 years. I have reformatted it here and added some headings, as it is an … Continue reading

Posted in canvas, HTML 5, Internet Explorer, JavaScript, W3C, Web Accessibility | 9 Comments

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 are used on HTML elements with a doctype other than … Continue reading

Posted in accessibility testing, HTML, HTML 5, HTML5, Standards, W3C, W3C Validator, WAI-ARIA, Web Accessibility | 1 Comment

HTML5 Accessibility Chops: section elements

HTML5 introduces new section elements. The new elements include header, footer, section, article, nav and aside. What is the accessibility potential of these new elements for users of assistive technology such as screen readers?

Posted in Assistive Technology, HTML, HTML 5, HTML5, JAWS, landmark roles, NVDA, VoiceOver, W3C, Web Accessibility | 5 Comments