Note: This site is not actively maintained.
I still work in accessibility, just no longer on this website.
I may rekindle it at some point, but for now…
There seems to be a bit more talk about this these days. And certainly, within the accessibility community, visually indicating focus is well-understood to be a crucial step in ensuring access for sighted keyboard users. Yet, the practice is still not as widespread as it should be. Continue reading Visible Keyboard Focus
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 point they are made visible and focus is set to them. 1. Link to visible simple anchor 2. Link programmatically setting focus to visible simple… Continue reading NVDA and JAWS with Links to Previously Hidden Anchors
tabindex, Keyboard Focus and Some ARIA in Screen ReadersThese 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 point. Nonetheless, they reveal some interesting, if not slightly worrying, behaviour on the part of at least two screen readers. At least two things are… Continue reading tabindex, Keyboard Focus and Some ARIA in Screen Readers
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 context of “skip links”, this has been something of an issue for years, the various reasons for and effects of which have been documented well… Continue reading In-Page Links and Input Focus [Again]