Re: Feedback on the current editor's draft

Quoting Lars Gunther <gunther@keryx.se>:


>> *<nav>
>>   A section with navigation links (uses HTMLElement).
>
> I see a use case where this will make skip links redundant. However, we
> already have aria roles that do the same. The one advantage I see is
> that this element might see more use, being simpler to remember and
> type.

It is a definite goal that authors not have to learn relatively  
complex technologies like aria in order to do simple things like allow  
AT to identify which section of the page contains navigation. The  
reason for this is simply that the number of authors that learn aria  
is likely to be smaller than the number that use the HTML elements in  
an appropriate way. As a consequence, the more accessible their pages  
are by "just" using appropriate HTML, the better the overall  
accessibility of the web will be. It's the same for things like input  
type=date; by making the native control accessible rather than forcing  
authors to use custom controls plus aria, we bring accessible markup  
within range of many many more authors.

Received on Monday, 10 August 2009 07:16:08 UTC