Hi John,
I like the term “purpose” for this, but I’m confused as to why “consistently” and “across a set of web pages” have been added?
If the point is to identify conventional controls across *websites*, each site having its own version is not desirable.
The changes imply that it will be different on different sites, so how does a user agent know what to do with these programmatically determined controls?
In the same way that name/role/value needs ARIA to specify things beyond native semantics, there needs to be a central / standardised way of saying what the purpose is.
I’m missing what it achieves at AA at the moment.
-Alastair
From: John Foliot [mailto:john.foliot@deque.com]
@(AA):
In content implemented using markup languages, the purpose of conventional controls[1] can be consistently, programmatically determined across a set of web pages.
@(AAA):
In content implemented using markup languages, the purpose of conventional controls[1] can be consistently, programmatically determined and modified across a set of web pages through the use of metadata or semantics.