Matthew King wrote: “I do not understand what currentfor would do for end users. In the above example, "2" is the button representing the currently displayed content. Pressing it again, if it is not also disabled, would refresh that content.” The more I look at this, the more I tend to agree we’d be better keeping it simple. Which leads us back to aria-current being allowed on all elements of the base markup, and for it to identify the current item within any scope? Léonie. -- Senior Accessibility Engineer, TPG @LeonieWatson @PacielloGroup
Received on Thursday, 6 November 2014 21:52:19 UTC