- From: Loretta Guarino Reid <lorettaguarino@google.com>
- Date: Mon, 5 Mar 2007 14:28:04 -0800
- To: public-bpwg-comments@w3.org
- Message-ID: <824e742c0703051428j3ce84f83k23b7c25e953c483a@mail.gmail.com>
These are comments from some members of the WCAG working group (specifically, Sorcha Moore, Tim Boland, Loretta Guarino Reid, Gregg Vanderheiden, and Michael Cooper). We are attaching a spreadsheet that covers an analysis of the overlap between WCAG, MobileOK Basic Tests, and Mobile Web Best Practices. We are concerned that the statement "Content which passes the tests has taken some steps to provide a functional user experience for users of basic mobile devices whose capabilities at least match those of the Default Delivery Context (DDC)." would lead authors to conclude that these guidelines will also meet the basic functional needs of users with disabilities who use basic mobile devices. here is much in common but these guidelines do not cover all of WCAG. We recommend adding "To accommodate users with disabilities, WCAG should also be met.", or "You should follow other guidelines that are applicable to Web content, including the Web Content Accessibility Guidelines." We like the similarity in approach to the descriptions of these test and WCAG2 techniques. For MobileOK Basic Tests 1.0, the tests are written in "programmatic" style. Test outcomes for MobileOK Basic 1.0 tests are pass, fail, and informative warnings. WCAG2.0 test outcomes are "true", or "false". It would be worth exploring whether we could use consistent language. MobileOK Basic 1.0 limits itself to machine-testable properties, while WCAG2 includes human-testable as well as machine-testable properties. There may be occasions where MobileOK Basic tests can be used to test all or part of a WCAG2 technique. Loretta Guarino Reid
Attachments
- application/vnd.ms-excel attachment: mwi_wcag.xls
Received on Monday, 5 March 2007 22:28:28 UTC