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

Re: AW: AW: "Bypass Blocks" Question

From: Phill Jenkins <pjenkins@us.ibm.com>
Date: Tue, 21 Jul 2015 21:03:03 -0500
To: Web Accessibility Initiative Interest Group <w3c-wai-ig@w3.org>
Message-ID: <OFC41A2AD6.629C1CAC-ON86257E8A.000A6916-86257E8A.000B451B@us.ibm.com>
Sounds like we are all in agreement that the best place to solve this is 
in the browser.  So, where is the pressure on the browser developers? 
where are the regulations?  where are the contracts from the federal gov 
asking the browsers to implement keyboard navigation.  Is there a petition 
I can sign? 

Regarding the "interim solution", I still feel it is more effective and 
efficient to help the end user install the plug-ins.  Users all seem to be 
able (with or without assistance) to download PDF viewers, etc.  And 
besides, it is usually the plug-ins and extensions approach that is a 
precursor to it being eventually part of the browser. Think of them as 
reference implementations.  as an example, Sync was a Firefox extension 
that is now integrated into the browser.

If you all want to continue to lobby for skip links, go ahead, but it sure 
hasn't gotten us very far over the last decade.
Phill Jenkins, 
Received on Wednesday, 22 July 2015 02:03:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:53 UTC