- From: Jonathan Avila <jon.avila@ssbbartgroup.com>
- Date: Wed, 27 Jul 2016 20:30:59 +0000
- To: WAI IG <w3c-wai-ig@w3.org>
> I'm starting to feel that the best way for a developer to handle tab strips on web pages is to put the ARIA application role around them to force the screen reader to use that mode Jim, in my view you should not use role of application. Screen readers like NVDA and JAWS support automatically going into forms and focus mode when you tab to the tab controls. Using application may prevent some screen readers like NVDA from showing the user the content within the role application in the virtual cursor or browse mode. The user should be in control not be forced into a mode by the developer. Jonathan Jonathan Avila Chief Accessibility Officer SSB BART Group jon.avila@ssbbartgroup.com 703.637.8957 (Office) Visit us online: Website | Twitter | Facebook | Linkedin | Blog Check out our Digital Accessibility Webinars! -----Original Message----- From: Jim Homme [mailto:jhomme@benderconsult.com] Sent: Wednesday, July 27, 2016 4:15 PM To: WAI IG Subject: Handling Tab Strips On The Web Hi, I'm starting to feel that the best way for a developer to handle tab strips on web pages is to put the ARIA application role around them to force the screen reader to use that mode, but wanted to get some opinions on how to handle this sort of thing. I'm asking about this because I'm a screen reader user trying to understand what to tell developers to do, and trying to keep my personal opinions out of the answer and failing to some degree. I'm looking at a web page that has tab controls part way down and thinking to myself that I'm torn between wanting the screen reader to automatically go into application mode and not wanting it to do that because I want to keep reading past the tab controls to see what else is there because that's how normal browse mode works. I hope this half made sense. Thanks. Jim
Received on Wednesday, 27 July 2016 20:31:35 UTC