There is also the native VoiceOver that comes on OS X. In my understanding, JAWS is the most popular screen reader. VoiceOverĪll the research mentioned so far has been for JAWS.
He uses JAWS as a screen reader and navigation in lists makes it harder for him. Reinhard Stebner made it pretty darn clear. We touched on ARIA as a way to help deal with some of this, and instead of using lists for links, he would like to see more and s used. Yet, there’s no easy way to identify a list as a set of links, so a page with 12 sets of links can be very confusing. We use HTML to apply meaningful mark-up to content – making things lists seems like a good ides. Putting a navigation structure, which is just a collection of hyperlinks, in a list is supposed to allow screen readers to pause between each link instead of reading all the links as a sentence. List, 6 items…” With divs and spans, the content is immediately available to the screen readers. Stebner was tabbing through the far too many lists on and they gave no clue as to where he was on the page and no information other than “List, 10 items. The span tag is not recognized by the screen reader, so it is one of the ways you can simplify your content for accessibility.ĭivs and spans are the way to go as they’re invisible to screen readers. This list structure, however, is not conducive to the screen reader’s logic. One of the first things you’re taught about coding is how to structure a navigation and this is normally done with an unordered list. I think everyone in the room scratched their heads when this was said.
Reinhard suggests not using lists for navigation, and instead using divs and spans. He is completely blind, and talks about markup accessibility. In January 2011, Reinhard spoke at a Refresh event in Baltimore and apparently made a HUGE impression on the audience.
Dustin’s article talks about semantics, accessibility, and screen readers, but has no research and doesn’t explain why the listless navigation is un-semantic or would present screen reader problems. The conclusion was that lists are best, but it was being compared against marking up lists in tables, so that makes sense.Ģ007: I posted about listless navigation and Dustin Brewer strongly disagreed that this should ever be used. Or if pre-HTML5, there would be no tag and instead Alternative: Listless Nav Ģ005: Bruce Lawson does actual research with screen readers. Note: make sure to check out the wrapup post of what we learned about all this after this post came out.
0 kommentar(er)
