2.4.3, 1.3.2 from adam solomon on 2011-08-02 (w3c-wai-gl@w3.org from July to September 2011)

From: adam solomon <adam.solomon2@gmail.com>
Date: Tue, 2 Aug 2011 12:03:51 +0300
To: WCAG <w3c-wai-gl@w3.org>
Message-ID: <CALKv3=ga4OUSVmzXD6Ot2wLzjebW=atpH66QKNL1a2yz88sqGA@mail.gmail.com>

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 09:04:27 UTC