- From: Bailey, Bruce <Bruce_Bailey@ed.gov>
- Date: Thu, 21 Dec 2000 10:36:35 -0500
- To: "'GL - WAI Guidelines WG (E-mail)'" <w3c-wai-gl@w3.org>
- Cc: "'gv@trace.wisc.edu'" <gv@trace.wisc.edu>, "'Robert Neff'" <rneff@bbnow.net>
Dear Group, Section 1194.22 should be of the most interest to this group. There is a table at the end of this section that makes a direct analogy the WCAG 1.0. For my own edification, I would especially like to have comments from this group comparing: (l) plus (m) to 6.3 (n) to 10.2 plus 12.4 I could not find an equivalent (even P3) for (o) and (p). They might be covered by Guideline 13 and 7 (respectively). Please note that the E&IT Accessibility Standards imply no such reference. Thank you. Bruce Bailey Ref: <http://www.access-board.gov/sec508/508standards.htm#PART%201194> > -----Original Message----- > From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On > Behalf Of Robert Neff [snip] > Start Snippet for 1194.22 > > Section 1194.22 Web-based intranet and internet information and > applications. > > (a) A text equivalent for every non-text element shall > be provided (e.g., via "alt", "longdesc", or in element content). > > (b) Equivalent alternatives for any multimedia > presentation shall be synchronized with the presentation. > > (c) Web pages shall be designed so that all information > conveyed with color is also available > without color, for example from context or markup. > > (d) Documents shall be organized so they are readable > without requiring an associated style sheet. > > (e) Redundant text links shall be provided for each > active region of a server-side image map. > > (f) Client-side image maps shall be provided instead of > server-side image maps except where > the regions cannot be defined with an available geometric shape. > > (g) Row and column headers shall be identified for data tables. > > (h) Markup shall be used to associate data cells and > header cells for data tables that have two > or more logical levels of row or column headers. > > (i) Frames shall be titled with text that facilitates frame > identification and navigation. > > (j) Pages shall be designed to avoid causing the screen > to flicker with a frequency greater than 2 Hz and lower than 55 Hz. > > (k) A text-only page, with equivalent information or > functionality, shall be provided to make a > web site comply with the provisions of this part, when > compliance cannot be accomplished in any other > way. The content of the text-only page shall be updated > whenever the primary page changes. > > (l) When pages utilize scripting languages to display > content, or to create interface elements, the > information provided by the script shall be identified with > functional text that can be read by assistive technology. > > (m) When a web page requires that an applet, plug-in or other > application be present on the client system to interpret page > content, the page must provide a link to a plug-in or applet that > complies with 1194.21(a) through (l). > > (n) When electronic forms are designed to be completed > on-line, the form shall allow people > using assistive technology to access the information, field > elements, and functionality required for > completion and submission of the form, including all > directions and cues. > > (o) A method shall be provided that permits users to > skip repetitive navigation links. > > (p) When a timed response is required, the user shall be > alerted and given sufficient time to indicate more time is required. > > Note to 1194.22: 1. The Board interprets paragraphs (a) > through (k) of this section as > consistent with the following priority 1 Checkpoints of the > Web Content Accessibility Guidelines 1.0 > (WCAG 1.0) (May 5, 1999) published by the Web Accessibility > Initiative of the World Wide Web Consortium: > > Section 1194.22 Paragraph (a) WCAG 1.0 Checkpoint 1.1 > Section 1194.22 Paragraph (b) WCAG 1.0 Checkpoint 1.4 > Section 1194.22 Paragraph (c) WCAG 1.0 Checkpoint 2.1 > Section 1194.22 Paragraph (d) WCAG 1.0 Checkpoint 6.1 > Section 1194.22 Paragraph (e) WCAG 1.0 Checkpoint 1.2 > Section 1194.22 Paragraph (f) WCAG 1.0 Checkpoint 9.1 > Section 1194.22 Paragraph (g) WCAG 1.0 Checkpoint 5.1 > Section 1194.22 Paragraph (h) WCAG 1.0 Checkpoint 5.2 > Section 1194.22 Paragraph (i) WCAG 1.0 Checkpoint 12.1 > Section 1194.22 Paragraph (j) WCAG 1.0 Checkpoint 7.1 > Section 1194.22 Paragraph (k) WCAG 1.0 Checkpoint 11.4 > > 2. Paragraphs (l), (m), (n), (o), and (p) of this section are > different from WCAG 1.0. Web > pages that conform to WCAG 1.0, level A (i.e., all priority 1 > checkpoints) must also meet paragraphs > (l), (m), (n), (o), and (p) of this section to comply with > this section. WCAG 1.0 is available at > http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505.
Received on Thursday, 21 December 2000 10:36:55 UTC