[Accessibility] Screen readers and WCAG - current state of art

[Steve Lee]

Looking at source for [1] it's largely a bunch of divs and spans so my
thoughts are a reader would have to rely on heuristics to make sense
of it. Also focus rect is almost invisible in tabs.

If this is one of the sites being discussed and WCAG 2 has been
followed then something has been overlooked. At a minimum highlights
how basic user testing is critical in addition to following standards.

Steve

2009/9/3 Alexander Surkov <surkov.alexander at gmail.com>:
> The [3] is just an accusation without any technical details or if you
> like proof of guilt. The report doesn't say even what browser and what
> version of JAWS or NVDA they used. However this is a key thing I
> believe. I agree with James it would be more helpful to get additional
> information.
>
> Thank you.
> Alex.
>
>
> On Wed, Sep 2, 2009 at 10:04 PM, Alexey
> Khoroshilov<khoroshilov at ispras.ru> wrote:
>> Hello everyone,
>>
>> My friends from "ICO Information for All" [1] have spent significant
>> efforts to make their web-sites friendly to people with disabilities
>> according to Web Content Accessibility Guidelines 2.0 [2]. But as they
>> report in [3], the efforts almost had no sense, since the leading screen
>> readers NVDA and Jaws does not support standard instructions especially
>> introduced for such kind of software.
>>
>> Is it a correct understanding of the current state of art?
>>
>> [1] http://www.ifap.ru/eng/index.htm
>> [2] http://www.w3.org/TR/WCAG20/
>> [3] http://community.livejournal.com/ifap_ru/13520.html (in Russian)
>>
>> --
>> Alexey
>> _______________________________________________
>> Accessibility mailing list
>> Accessibility at lists.linux-foundation.org
>> https://lists.linux-foundation.org/mailman/listinfo/accessibility
>>
> _______________________________________________
> Accessibility mailing list
> Accessibility at lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/accessibility
>