W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2015

Re: "Bypass Blocks" Question

From: Michiel Bijl <michiel@agosto.nl>
Date: Mon, 20 Jul 2015 18:59:06 +0200
Cc: Web Accessibility Initiative Interest Group <w3c-wai-ig@w3.org>
Message-Id: <668EEE54-597D-419B-911A-D70423C4DC44@agosto.nl>
To: Phill Jenkins <pjenkins@us.ibm.com>
There is no native way to navigate landmarks within browsers. There have been proposals for this, see this bug report on Mozilla’s Bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=670928


> On 20 Jul 2015, at 18:49, Phill Jenkins <pjenkins@us.ibm.com> wrote:
> "People who do not use screen readers have yet no possibility to use the comfort of jumping from one block to another . . ." 
> No true, there are many plug-ins and extensions  for browsers such as  IE, Firefox, and others to navigate by heading or WAI-ARIA landmark / region. 
> ". . . it is still necessary to offer internal links to the top of the blocs" 
> No, it is not!   
> In my opinion 
> 1. It would be better to educate end users on how to install and use the plug-ins available, 
> 2. It would be more efficient to request more capabilities from the developers / manufacturers of the relatively very few browsers.   
> 3. It would much more effective to request more or better plug-in and extensions from the open source community that is creating them. 
> I just did a search on "browser heading keyboard navigation" and didn't find what I was looking for - just more guidance on why keyboard nav for web developers and too much mention of screen readers and nothing on browser capabilities. 
> I tried another search by "browser WAI-ARIA keyboard navigation" and found a couple.   
> So the problem seems to be "us", the accessibility community, for not posting resources about the various capabilities in the browsers, plug-in, and extensions, including JavaScript frameworks for keyboard navigation for end-users.  Below is an initial resource list.  Please copy, add-to, and post to increase the community awareness.  We are never going to make the progress we need to by asking the millions of web sites to add skip nav links when a relatively very few browsers and open source community folks can solve the problem for us.  Asking web site owners to go beyond using the structural mark-up and adding skip nav links too, that we have been asking for for over a decade, is not working.  Lets all try to be more efficient in our recommendations by using all the guidelines we have, including UAAG <http://www.w3.org/TR/UAAG20/> . 
> Browser Keyboard Navigation Resources for end users: 
> 47 Keyboard Shortcuts That Work in All Web Browsers <http://www.howtogeek.com/114518/47-keyboard-shortcuts-that-work-in-all-web-browsers/> 
> http://www.howtogeek.com/114518/47-keyboard-shortcuts-that-work-in-all-web-browsers/ <http://www.howtogeek.com/114518/47-keyboard-shortcuts-that-work-in-all-web-browsers/> 
> ARIA Keyboard Navigation 
> http://irama.org/web/dhtml/aria/key-nav/ <http://irama.org/web/dhtml/aria/key-nav/> 
> HeadingsMap - extension generates a documentmap or index of web document structured with headings (you can access directly to the content by clicking on any of its items), and now, it shows the HTML 5 outline. 
> https://addons.mozilla.org/en-US/firefox/addon/headingsmap/ <https://addons.mozilla.org/en-US/firefox/addon/headingsmap/> 
> GreaseMonkey User keyboard scripts - Greasemonkey is a Firefox extension that allows you to customize the way webpages function, Hundreds of scripts are already available for free. And if you're the tinkerer sort, you can also write your own 
> http://www.greasespot.net/ <http://www.greasespot.net/> 
> etc. 
> ____________________________________________
> Regards,
> Phill Jenkins, 
> Senior Engineer & Business Development Executive
> IBM Accessibility
Received on Monday, 20 July 2015 17:00:15 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:57 UTC