WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: WCAG 2.0 SC 2.1.1?

for

From: Sailesh Panchang
Date: Aug 5, 2011 6:39AM

Well the fact that it works with Internet Explorer means that it can
indeed be made keyboard operable. So one needs to point out to the
developers / clients that it does not work in Firefox ... a browser
that is quite popular amongst AT users too.
Perhaps the code needs tweeking a bit or there is something that is
not valid etc. And an example of similar content that works in IE and
Firefox could also be made available perhaps.
After all it is upto the org whether it chooses to address it or not.
If for instance the application was used internally and FF is their
primary browser, it fails 2.1.1 for sure.
Sailesh

> On Thu, Aug 4, 2011 at 8:46 PM, Donald Evans < <EMAIL REMOVED> > wrote:
>
>> If I have a web app with controls that are keyboard accessible for the
>> non-AT user, the JAWS user and the NVDA user in Internet Explorer;
>> however,
>> are not accessible to these users in FireFox, does it fail S.C. 2.1.1?
>>
>> --
>> Donald F. Evans,
>> Making Websites Accessible
>> Senior Accessibility Architect
>> Deque Systems
>> Email: <EMAIL REMOVED>
>> Download FireEyes Free: http://www.deque.com/products/worldspace-fireeyes
>>
>> <http://www.deque.com>;
>>