W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > October to December 2006

Pre-Christmas musing on the structure of UAAG X.Y

From: Jan Richards <jan.richards@utoronto.ca>
Date: Thu, 21 Dec 2006 13:50:40 -0500
Message-ID: <458AD780.60602@utoronto.ca>
To: WAI-UA list <w3c-wai-ua@w3.org>

I've spent some time comparing ATAG 2.0 and UAAG 1.0 and thinking about 
why they are structured so differently...and I've come up with an idea 
for reordering UAAG to fit better with ATAG (which in turn has been 
organized to fit with WCAG)...

NOTES:
- This is just an idea to stimulate discussion - so far we haven't made 
any decision on how to proceed as a group.

- Full disclosure: I am an editor of ATAG 2.0 and I tend to think that 
it is fairly well organized. (though it could always get better - and 
since it is not yet set in stone, it might be a good time for the UAWG 
to reflect back on ATAG 2.0's structure)

- On the other hand, maybe I've just had too much eggnog. Happy 
holidays!  :)

---

PART A: Make the user agent user interface accessible.
   Guideline A.1: User agent user interface must be perceivable
   Guideline A.2: User agent user interface must be operable
   Guideline A.3: User agent user interface must be understandable
   Guideline A.4: User agent user interface must be access system
     friendly

PART B: Enhance the accessibility of rendered content.
   Guideline B.1: Perceivability of rendered content must be enhanced
   Guideline B.2: Operability of rendered content must be enhanced.
   Guideline B.3: Understandability of rendered content must be enhanced.
   Guideline B.4: Access system friendliness of rendered content must be
     enhanced.

---

Cheers,
Jan
Received on Thursday, 21 December 2006 18:51:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:51:37 GMT