- From: <Bruce_Roberts/CAM/Lotus@lotus.com>
- Date: Wed, 2 Jun 1999 14:48:09 -0400
- To: w3c-wai-au@w3.org
I'm still uncomfortable with having multiple tool accessibility checkpoints. I'm O.K. (marginally) with the checkpoint for following the operating system standards with a large list of techniques behind it. Beyond that, I would like to be convinced that this group has the correct expertise and can spend the appropriate time to define other UI accessiblity requirements. I know I don't have that expertise or the time. Can other folks speak to this? -- Bruce Charles McCathieNevile <charles@w3.org>@w3.org on 06/01/99 06:53:47 PM Sent by: w3c-wai-au-request@w3.org To: WAI AU Guidelines <w3c-wai-au@w3.org> cc: Subject: Guideline 2.1 proposals The current checkpoints: 2.1.1 Use operating system and accessibility standards and conventions for the platform(s) the tool runs on. [P1] 2.1.2 Ensure that user agent functionality offered by the tool (e.g., in a preview mode) conforms to the W3C's User Agent Accessibility Guidelines[1]. [WAI-USERAGENT][2] [P1] 2.1.3 Ensure the rendering used while authoring is independent of styles used for the published document (e.g., the font size, letter and line spacing, and text and background color, etc.). [P1] 2.1.4 Allow the author to display a textual equivalent of content while editing. [P1] 2.1.5 For each element of a document, the properties of that element must be accessible to the author. [P1] 2.1.6 Enable navigation and editing via the structure of the document. [P1] 2.1.7 Enable editing of the structure of the document. [P2] I propose we: remove 2.1.2 (redundant with 2.1.1), 2.1.3 (belongs in 2.6 perhaps? it's about providing multiple views - the rest is in 2.1.5) and 2.1.4 (as noted in previous email). I suggest we add a checkpoint - "make the tool accessible" (with the techniques I suggested earlier), and add reading and editing to 2.1.5. Along with some slight edits, this is the new checkpoints I am proposing: 2.1.1. Make the tool accessible [P1] 2.1.2. Follow operating system conventions and guidelines [P1] 2.1.3. Allow the author to read and edit all properties of every element of the document [P1] 2.1.4. Enable navigation and editing via the structure of the document P2] 2.1.5. Enable editing of the structure of the document [P2] In addition, we remove 2.4.1 (redundant with the new 2.1.3) and we have a new checkpoint in section 2.6: Provide multiple views for editing [P3] (this has been there before. It is a helpful thing to do, but I don't think it rates a higher priority than that) Charles McCN
Received on Wednesday, 2 June 1999 14:43:30 UTC