Re: Re: Spam Bots/E-mail Addys

On Fri, 14 Jun 2002, Analysis & Solutions wrote: > On Thu, Jun 13, 2002 at 10:36:56PM -0500, Miguel Cruz wrote: >> If you're doing the site for the US government, you're (thank goodness) >> required by law to make sure it works without JavaScript. > > REALLY?! That's good news. Could you please provide a source for that? Section 508 of the Rehabilitation Act Amendments (which is so exciting that it has its own web site, www.section508.gov) requires that information made available to the public through electronic means be done so in a manner that provides broad accessibility to people with a wide variety of impairments. It took a long time (the law was passed in 1998) to figure out what that would mean - I was working for the government at the time and it was a bit frustrating, as expectations for the final requirements kept changing, even though the compliance deadline was expected to arrive before the guidelines! Reading the final law, it looks like they eased up from the position taken in the penultimate proposal which was looking solid as I left for the private sector. That position was that any scripted process had to be accompanied by a non-client-side-scripted alternative. In the final version, that's been replaced with a not-too-clear statement (paragraph l) which may or may not say the same thing. Here's the full set of requirements as put forth in 36 CFR 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. miguel