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

Re: 2.4.3, 1.3.2

From: Loretta Guarino Reid <lorettaguarino@google.com>
Date: Tue, 2 Aug 2011 06:42:48 -0700
Message-ID: <CAHu5OWbraF=3Jw2=HUUM5Kk=hYbLPSm0TMDXsnPamd1NV8PqMw@mail.gmail.com>
To: adam solomon <adam.solomon2@gmail.com>
Cc: WCAG <w3c-wai-gl@w3.org>
Andrew should weigh in on this, but I believe this is the way things work in
Flash, that tabindex can be used to control the reading order of all the
content, not just interactive content.

Using tabindex in HTML is not a sufficient technique for 1.3.2.

On Tue, Aug 2, 2011 at 2:03 AM, adam solomon <adam.solomon2@gmail.com>wrote:

> We have Using tabindex in flash<http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/FLASH37>as a sufficient technique in 2.4.3 and 1.3.2. 1.3.2 stipulates meaningful
> sequence to be programmatically determined. Can someone explain how tabindex
> facilitates this? Tabindex will never fix a bad sequence for screen readers,
> so how can it satisfy 1.3.2?
>
Received on Tuesday, 2 August 2011 13:43:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 August 2011 13:43:25 GMT