E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 3 (In chronological order)

From: Donald Evans
Date: Thu, Aug 04 2011 9:18AM
Subject: WCAG 2.0 SC 2.1.1?
No previous message | Next message →

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 ADDRESS REMOVED =
Download FireEyes Free: http://www.deque.com/products/worldspace-fireeyes

<http://www.deque.com>;

From: Jeevan Reddy
Date: Fri, Aug 05 2011 5:45AM
Subject: Re: WCAG 2.0 SC 2.1.1?
← Previous message | Next message →

HI Donald,
if the APP controls are operable by Keyboard and same info is not exposing
To AT users, that will be violation of WCAG 2..0 SC 4.1.2(Name, Role,
Value). or else, the same info is exposing and are not operable by keyboard
when using AT, then it is certainly violation SC 2.1.1!.

On Thu, Aug 4, 2011 at 8:46 PM, Donald Evans < = EMAIL ADDRESS 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 ADDRESS REMOVED =
> Download FireEyes Free: http://www.deque.com/products/worldspace-fireeyes
>
> <http://www.deque.com>;
>

From: Sailesh Panchang
Date: Fri, Aug 05 2011 6:39AM
Subject: Re: WCAG 2.0 SC 2.1.1?
← Previous message | No next message

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 ADDRESS 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 ADDRESS REMOVED =
>> Download FireEyes Free: http://www.deque.com/products/worldspace-fireeyes
>>
>> <http://www.deque.com>;
>>