Thread Subject: Grouping of the current 28 software/webstandards

From: Jim Thatcher
Date: Wed, Oct 11 2006 11:35 AM

• Return to this mailing list's archives
• View all messages in this thread
• Next message in thread: Tamas Babinszki: "Re: Grouping of the current 28 software/webstandards"
• Previous message in thread: None
• Messages sorted by: Author | Thread | Date

All,

I think the grouping of standards will be very helpful. I like Peter Korn's
suggestion but have modified it somewhat. I find 4 groups as indicated
below. I think we will want to look at some web and software at the same
time since the requirements are similar or identical - See "don't use color
alone" as a prime example.

We entered the EITAAC (previous Advisory Committee) effort for software with
existing wording from Dept. Of Ed. and from IBM. That was a huge help. (The
fact that the software committee was only 8 members was a help too.)
Similarly, today we can bring in WCAG 2.0 and other guidelines addressing
these issues.

Can anyone provide a list of (recent) existing software guidelines?

Jim

Accessibility Consulting: http://jimthatcher.com/
512-306-0931


Group A: Interaction and operating system

21(a) When software is designed to run on a system that has a keyboard,
product functions shall be executable from a keyboard where the function
itself or the result of performing a function can be discerned textually.

21(b) Applications shall not disrupt or disable activated features of other
products that are identified as accessibility features, where those features
are developed and documented according to industry standards. Applications
also shall not disrupt or disable activated features of any operating system
that are identified as accessibility features where the application
programming interface for those accessibility features has been documented
by the manufacturer of the operating system and is available to the product
developer.

21(g) Applications shall not override user selected contrast and color
selections and other individual display attributes.

21(j) When a product permits a user to adjust color and contrast settings, a
variety of color selections capable of producing a range of contrast levels
shall be provided.


Group B: Requirements by content type

21(e) When bitmap images are used to identify controls, status indicators,
or other programmatic elements, the meaning assigned to those images shall
be consistent throughout an application's performance.

21(h) When animation is displayed, the information shall be displayable in
at least one non-animated presentation mode at the option of the user.

21(i) Color coding shall not be used as the only means of conveying
information, indicating an action, prompting a response, or distinguishing a
visual element.

21(k) Software shall not use flashing or blinking text, objects, or other
elements having a flash or blink frequency greater than 2 Hz and lower than
55 Hz.

22(j) Pages shall be designed to avoid causing the screen to flicker with a
frequency greater than 2 Hz and lower than 55 Hz.

22(a) A text equivalent for every non-text element shall be provided (e.g.,
via "alt", "longdesc", or in element content).

22(b) Equivalent alternatives for any multimedia presentation shall be
synchronized with the presentation.

22(c) Web pages shall be designed so that all information conveyed with
color is also available without color, for example from context or markup.

22(e) Redundant text links shall be provided for each active region of a
server-side image map.

22(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.

22(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.

22(p) When a timed response is required, the user shall be alerted and given
sufficient time to indicate more time is required.


Group C: Programmatic exposure of information:

21(c) A well-defined on-screen indication of the current focus shall be
provided that moves among interactive interface elements as the input focus
changes. The focus shall be programmatically exposed so that assistive
technology can track focus and focus changes.

21(d) Sufficient information about a user interface element including the
identity, operation and state of the element shall be available to assistive
technology. When an image represents a program element, the information
conveyed by the image must also be available in text.

21(f) Textual information shall be provided through operating system
functions for displaying text. The minimum information that shall be made
available is text content, text input caret location, and text attributes.

22(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.

22(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).


Group D: Correct coding

22(d) Documents shall be organized so they are readable without requiring an
associated style sheet.

22(g) Row and column headers shall be identified for data tables.

22(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.

22(i) Frames shall be titled with text that facilitates frame identification
and navigation.

21(l) When electronic forms are used, 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.

22(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.

22(o) A method shall be provided that permits users to skip repetitive
navigation links.

• Next message in Thread: Tamas Babinszki: "Re: Grouping of the current 28 software/webstandards"
• Previous message in Thread: None