Re: 1.3.1 question

Agree

ARIA is a technique - not an outcome. 

In WCAG we never required a technology but rather an outcome — what an author much achieve but not how to achieve it.   Giving authors the ability to use any ‘accessibility supported’ techniques they want to achieve it.      This is part of the ‘technology independent’ nature of WCAG.  

If we REQUIRE    ARIA  — then are we requiring HTML
If we require ARIA for HTML only — then what happens when we have some other way?   What if something works better on some page for some reason?




I think Sufficient labels — with the safe harbor and guidance they provide is the best method for encouraging this   —  along with recommendations or strong recommendations in the Understanding WCAG 2.0 doc. 



gregg