This document:Public document·View comments·Disposition of Comments·
Nearby:Accessibility Guidelines Working Group Other specs in this tool Accessibility Guidelines Working Group's Issue tracker
Quick access to LC-2585 LC-2586 LC-2597 LC-2603 LC-2604 LC-2607 LC-2608 LC-2614 LC-2615 LC-2616 LC-2617 LC-2618 LC-2621 LC-2624 LC-2629 LC-2630 LC-2633 LC-2634 LC-2717 LC-2722 LC-2733 LC-2744 LC-2747 LC-2748 LC-2749 LC-2774 LC-2781 LC-2782 LC-2783 LC-2828 LC-2829
Previous: LC-2604 Next: LC-2617
I understand that it's called "focus order", but this SC refers to “navigationâ€Â, as does the Guideline. I get how tabbing between links / fields might seem like "navigation", but that seems very HTML/Flash-specific and it's not even fair to those formats (frankly) either, since that's hardly the only (or primary) means of "navigation" in HTML, at least. SC 2.4.3 is the _only_ Level A criterion that mentions "navigation", and yet judging by the Techniques (HTML and PDF) it's understood to be only applicable to content that includes focusable (read "input") elements. I don't understand this at all, and I did not find the "Understanding" text enlightening. Indeed, that text is suggestive in appearing to support (in part) my understanding of SC 2.4.3 that the SC's intent is more general than the traditional elements than "receive focus". Since the SC appears to pertain to navigation, and if "focus" reasonably also includes structure elements, I would expect PDF9 to apply to this SC. Proposed Change: Add PDF9 to this SC. Also, I suggest considering that "navigation" goes beyond input elements - that's certainly the case in PDF, for example, and I would suspect, in other formats as well.