In-Page Links and Input Focus [Again]
That in-page links work and properly update the page's input focus can be crucial for users that rely on keyboard navigation, especially if they do not also use a screen reader. Often discussed in the...
View Articletabindex, Keyboard Focus and Some ARIA in Screen Readers
These test cases are in no way comprehensive or robust: They should really be supplemented with examples using a greater variety of HTML5 elements and ARIA roles, but I just can't be bothered at this...
View ArticleNVDA and JAWS with Links to Previously Hidden Anchors
Each of the anchors (both the a elements and heading anchors) below have an id and tabindex="-1". Target anchors 3 and 6 are hidden with display:none until they are targetted with the link at which...
View ArticleAccessible ARIA Tabs
The WAI-ARIA specification remains unfinished and its implementation incomplete. All the same, some of it, e.g., landmark roles, can be used right now to improve the accessibility of web content and...
View ArticleAn ARIA alert Test Case
Based on a comment to my article, Not All ARIA Widgets Deserve role="application", I put together a few examples of ARIA alerts and tested them with JAWS and NVDA in Firefox 3.6, Internet Explorer 7...
View ArticleHTML5, ARIA Roles, and Screen Readers in March 2011
Last year, in HTML5, ARIA Roles, and Screen Readers in March 2010, I took a look at how then current screen readers behaved with some of the HTML5 section elements and related WAI-ARIA document and...
View ArticleResponsive Data Tables and Screen Reader Accessibility
When Chris Coyier presented his approach to responsive data tables, I wondered about the implications for accessibility, particularly for screen readers. This was especially so since the approach...
View Article
