Draft: Mapping Comparison Between
U.S. Section 508 Standards (Combined Subparts B,C & D) and
UAAG 1.0 Requirements & Priorities

Combined = (Subpart B) Technical Standards (1194.21 - Software) and (1194.22 - Web),
(Subpart C) Functional Performance Criteria (1194.31), and (Subpart D) Information, Documentation, and Support (1194.41)

W3C Internal Working Draft - November 1, 2001

This version:: http://www.w3.org/WAI/GL/508/508-UAAG.html
Last Updated: $Date: 2001/12/20 19:40:47 $
Authors & Editors:: Jim Allan, Texas School for the Blind and Visually Impaired; Katie Haritos-Shea

Abstract

This document describes the comparison of the User Agent Accessibility Guidelines (UAAG) 1.0 [UAAG10] requirements, as they relate to the United States Workforce Investment Act of 1998. The Workforce Investment Act legislation includes the Rehabilitation Act Amendments of 1998. It is Section 508 of the Rehabilitation Act Amendments, that requires US Federal agencies to ensure that the electronic and information technology allows Federal employees with disabilities to use information and data that is comparable to information and data used by Federal employees who are not individuals with disabilities. Section 508 also requires that individuals with disabilities, who are members of the public seeking information or services from a US Federal agency, have access to and use of information and data that is comparable to that provided to the public who are not individuals with disabilities.

User Agents (Browsers) clearly are governed by Subpart B of the Technical Standards of Section 508 under § 1194.21 for software applications and operating systems.Additionally, UAAG has relevance to § 1194.22 Web-based intranet and internet information and applications, in that you must have a browser that supports (allows control of presentation) these requirements. UAAG also has relevance to Subpart C - Functional Performance Criteria (1194.31) and Subpart D Information, Documentation, and Support (1194.41).

Our aim is to assist software/web developers and device/application producers in understanding what is comparable in the U.S. Section 508 Standards and UAAG 1.0 Requirements. The goal proposed by these two provisions are essentially the same, that of achieving Accessible User Agent (browser) and other software products, as well as improving communication between assistive technologies and other types of user agents.

Please refer to some of the initial work on this comparison document of the
User Agent Accessibility Guidelines (UAAG) 1.0 and Section 508 of the US Workforce Investment Act of 1988 at: http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JanMar/0561
Source: http://lists.w3.org/Archives/Public/w3c-wai-ua/2001JulSep/0272
Done: http://lists.w3.org/Archives/Public/w3c-wai-ua/2001OctDec/0050

Status Of This Document

This document has been produced as a tool for developers to understand where the 508 Requirements and UAAG 1.0 Requirements converge and depart. This work is part of a suite of comparison documents being done by the User Agent Accessibility Guidelines (UAWG) Working Group. These are initial notes by the authors; this document does not represent Working Group consensus.

It is also important to note that the United States Access Board (or The Architectural and Transportation Barriers Compliance Board) has not reviewed or sanctioned this document. The Access Board was the agency designated in (Section 508(a)(2)(A) to publish standards setting forth a definition of electronic and information technology and the technical and functional performance criteria necessary for accessibility for such technology, for the United States Government.)

This document is part of a series of accessibility documents published by the Web Accessibility Initiative (WAI) of the World Wide Web Consortium (W3C). WAI Accessibility Guidelines are produced as part of the WAI Technical Activity. The goals of the User Agent Accessibility Guidelines Working Group are described in the charter.

Status Of This Document
How This Document Is Organized
Combined 508 Standards v. UAAG 1.0 Requirements
508 Software Standards (Subpart B)(1194.21) v. UAAG 1.0 Requirements
508 Web Standards (Subpart B)(1194.22) v. UAAG 1.0 Requirements
508 Functional Performance Criteria (Subpart C)(1194.31) v. UAAG 1.0 Requirements
508 Information, Documentation, and Support (Subpart D)(1194.41) v. UAAG 1.0 Requirements
Glossary
References

How This Document is Organized

W3C Web Accessibility Initiative's Priority Levels as used in UAAG 1.0 Requirements:

[Priority 1]
(P1) This checkpoint must be satisfied by user agents, otherwise one or more groups of users with disabilities will find it impossible to access the Web. Satisfying this checkpoint is a basic requirement for enabling some people to access the Web.
[Priority 2]
(P2) This checkpoint should be satisfied by user agents, otherwise one or more groups of users with disabilities will find it difficult to access the Web. Satisfying this checkpoint will remove significant barriers to Web access for some people.
[Priority 3]
(P3) This checkpoint may be satisfied by user agents to make it easier for one or more groups of users with disabilities to access information. Satisfying this checkpoint will improve access to the Web for some people

@@ * Discussion here about how Software is the primary source in order followed by the Web Requirements of 508, and how these two standards in unison are compared to UAAG 1.0 Requirements * @@

WCAG10: Web Content Accessibility Guidelines 1.0, 1999-5-5 WCAG 1.0
WCAG20-Draft: Web Content Accessibility Guidelines 2.0, 2001-0-0 WCAG 2.0
ATAG10: Authoring Tools Accessibility Guidelines 1.0, 2000-02-03 ATAG 1.0
UAAG10: Working Draft User Agent Accessibility Guidelines, 2000-07-28 UAAG 1.0

508 v. UAAG 1.0 Requirements

1. Keyboard

Relevance to Accessibility

When keyboard access to a programs' controls and features is provided, a person who cannot use a mouse or other pointing device will still be able to run the product. For example, a person with a disability that affects dexterity may find it impossible to move or hold a pointing device with enough accuracy to activate desired features. A person who cannot see the screen, therefore relying on assistive technology, may have no problems moving the pointer but will be unable to determine what is being pointed to.

Users without a pointing device need to be able to activate form controls and links (including the links in a client-side image map).

508 Software (Subpart B)(1194.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.

508 Web (Subpart B)(1194.22)

None or In Progress of Mapping

508 Functional Performance (Subpart C)

(a)
At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for assistive technology used by people who are blind or visually impaired shall be provided.

(f)
At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and which is operable with limited reach and strength must be provided.

508 Information, Documentation, and Support (Subpart D)

None or In Progress of Mapping

Comparison

Comment:
UAAG * always * requires keyboard support

UAAG 1.0 Requirements & Priority

1.1 Full Keyboard access
Ensure that the user can operate the user agent fully through keyboard input alone.

Both content and user agent.

Who benefits:

Users with blindness are most likely to benefit from direct access through the keyboard, including navigation of user interface controls; this is a logical navigation, not a spatial navigation.
Users with physical disabilities are most likely to benefit from a combination of direct access and spatial access through the keyboard. For some users with physical disabilities, moving the pointing device through a physical mouse may be significantly more difficult than moving the pointing device with arrow keys, for example.
This checkpoint will also benefit users of many other alternative input devices (which make use of the keyboard API) and also anyone without a mouse.

[Priority 1]

1.2 Activate event handlers
For the element with content focus, allow the user to activate any explicitly associated input device event handlers through keyboard input alone.

Who benefits: Users with blindness or some users with a physical disability, and anyone without a pointing device.

[Priority 1]

2. Operating Conventions of Accessibility Features

Relevance to Accessibility: Many commercially available software applications and operating systems have features built into the program that are labeled as accessibility features. These features can typically be turned on or off by a user. Examples of these features include: reversing the color scheme (to assist people with low vision), showing a visual prompt when an error tone is sounded (to assist persons who are deaf or hard of hearing), or providing "sticky keys" that allow a user to press key combinations (such as control-C) sequentially rather than simultaneously (to assist persons with dexterity disabilities). This requirement prohibits software programs from disabling these features when they have been activated prior to running the application.
508 Software (Subpart B)(1194.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.
508 Web (Subpart B)(1194.22): None or In Progress of Mapping
508 Functional Performance (Subpart C): None or In Progress of Mapping
508 Information, Documentation, and Support (Subpart D): @@ Not real sure about this.....; (a)
When an agency provides end-user documentation to users of technology, the agency must ensure that the documentation is available upon request in alternate formats.; (b)
Requires that agencies supply end-users with information about accessibility or compatibility features that are built-into a product, upon request.
Comparison: In Progress
UAAG 1.0 Requirements & Priority: 7.1 Focus and selection conventions
Follow operating environment conventions that benefit accessibility when implementing the selection, content focus, and user interface focus.; Who benefits: Many users with many types of disabilities.; [Priority 1]; 7.2 Respect input configuration conventions
Ensure that default input configurations do not interfere with operating environment accessibility conventions.; Who benefits: Many users with many types of disabilities.; [Priority 1]; 7.3 Operating environment conventions
Follow operating environment conventions that benefit accessibility. In particular, follow conventions that benefit accessibility for user interface design, keyboard configuration, product installation, and documentation.; Who benefits: Many users with many types of disabilities.; [Priority 2]; 7.4 Input configuration indications
Follow operating environment conventions to indicate the input configuration.; Who benefits: Many users with many types of disabilities.; [Priority 2]

3. Focus

Relevance to Accessibility: Providing a visual indication of the focus allows someone who is viewing the screen to accurately access the programs' features. When a computer is being operated by a person who is also running a screen enlargement program or a speech or Braille output system, the assistive technology must discern the focus point. This provision requires that the position of the programs' focus be made available through its code to assistive technology. When, for example, a screen enlargement program magnifies a section of the screen, it must be able to follow the focus as the focus changes. If the magnified area does not move with the focus, the user may easily move down through a list of choices with the arrow keys but the magnified area remains stationary and very shortly the user has no idea what items will be activated if an action is taken.
508 Software (Subpart B)(1194.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
508 Web (Subpart B)(1194.22): None or In Progress of Mapping
508 Functional Performance (Subpart C): (a)
At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for assistive technology used by people who are blind or visually impaired shall be provided.; (b)
At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 (when corrected with glasses) must be provided in audio and enlarged print output that works together or independently. In the alternative, support for assistive technology used by people who are blind or who have low vision must be provided.
508 Information, Documentation, and Support (Subpart D): None or In Progress of Mapping
Comparison: In Progress
UAAG 1.0 Requirements & Priority: 5.4 Selection and focus in viewport
Ensure that when a viewport's selection or content focus changes, it is at least partially in the viewport after the change.; Who benefits: Users who may be disoriented by a change in focus or selection that is not reflected in the viewport. This includes some users with blindness or low vision, and some users with a cognitive disability.; [Priority 2]; 6.5 Programmatic alert of changes
Using standard APIs, provide programmatic alert of changes to content, user interface controls, selection, content focus, and user interface focus.; Who benefits: Users with a disability who rely on assistive technologies for output.; [Priority 1]; 10.6 Provide link information
Provide a mechanism for highlighting the selection and content focus. Allow the user to configure the highlight styles. The highlight mechanism must not rely on color alone. For graphical viewports, if the highlight mechanism involves colors or text decorations, allow the user to choose from among the full range of colors or text decorations supported by the operating environment.; Who benefits: Users for whom following a link may lead to loss of context upon return, including some users with blindness and low vision, a memory or cognitive disability, or a physical disability.; [Priority 3]

4. User Interface Elements

Relevance to Accessibility: Text needs to be associated with each interface element. The text must identify the element and its current state or condition. For example, a button that shows a hand for getting more help must have the word "help" associated with the button. If a checkbox is present, a text label must indicate what is being checked, and whether the checkbox is checked or unchecked. There are many ways to accomplish this depending on the program language being used.
508 Software (Subpart B)(1194.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
508 Web (Subpart B)(1194.22): None or In Progress of Mapping
508 Functional Performance (Subpart C): (a)
At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for assistive technology used by people who are blind or visually impaired shall be provided.
508 Information, Documentation, and Support (Subpart D): None or In Progress of Mapping
Notes: Examples of user interface elements include button checkboxes, menus, toolbars, scroll bars, and any other feature of a program that is intended to allow the user to perform some action.
UAAG 1.0 Requirements & Priority: 1.2 Activate event handlers
Ensure that every message (e.g., prompt, alert, notification, etc.) that is a non-text element and is part of the user agent user interface has a text equivalent.; Who benefits: Users with blindness or some users with a physical disability, and anyone without a pointing device.; [Priority 1]; 6.4 Programmatic operation
Provide programmatic read and write access to user agent user interface controls.; Who benefits: Users with a disability who rely on assistive technologies for input and output.; [Priority 1]

5. (Consistency in) Programmatic Elements of Images

Relevance to Accessibility

This component is important to avoid user confusion while navigating within the program. Most screen reading programs allow users to assign text names to bitmap images. If the bitmap image changes meaning during a program's or user agent's execution, the assigned identifier is no longer valid and is confusing to the user.

508 Software (Subpart B)(1194.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.

508 Web (Subpart B)(1194.22)

None or In Progress of Mapping

508 Functional Performance (Subpart C)

(b)
At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 (when corrected with glasses) must be provided in audio and enlarged print output that works together or independently. In the alternative, support for assistive technology used by people who are blind or who have low vision must be provided.

508 Information, Documentation, and Support (Subpart D)

None or In Progress of Mapping

Comparison

Comment:
No corresponding requirement. However, checkpoint 6.4 Programmatic operation, may have some relevance. Consistent use and meaning of images still requires that users have access to these controls in an accessible manner.
Also,consistency in the UI is probably covered by checkpoint 7.3:

UAAG 1.0 Requirements & Priority

6.4 Programmatic operation

Provide programmatic read access to user agent user interface controls.
Provide programmatic write access for those controls that the user can modify through the user interface. For security reasons, user agents are not required to allow instructions in content to modify user agent user interface controls. To satisfy these requirements, implement at least one API that is either
* defined by a W3C Recommendation, or *
a publicly documented API designed to enable interoperability with assistive technologies.
If no such API is available, or if available APIs do not enable the user agent to satisfy the requirements, implement at least one publicly documented API that allows programmatic operation of all of the functionalities that are available through the user agent user interface, and follow operating environment conventions for the use of input and output APIs
An API is considered available if the specification of the API is published (e.g., as a W3C Recommendation) in time for integration into a user agent's development cycle.

Who benefits: Users with a disability who rely on assistive technologies for input and output.

[Priority 1]

7.3 Operating environment conventions
Follow operating environment conventions that benefit accessibility. In particular, follow conventions that benefit accessibility for user interface design, keyboard configuration, product installation, and documentation.

Who benefits: Many users with many types of disabilities.

[Priority 2]

6. Text

Relevance to Accessibility

The operating system is the "core" computer software that controls basic functions, such as receiving information from the keyboard, displaying information on the computer screen, and storing data on the hard disk. Other software programs use the standard protocols dictated by the operating system for displaying their own information or processing the output of other computer programs. When programs are written using unique schemes for writing text on the screen or use graphics, other programs such as software for assistive technology may not be able to interpret the information. This provision does not prohibit or limit an application programmer from developing unique display techniques. It requires that when a unique method is used, the text should also be written to the screen through the operating system.

A text equivalent means adding words to represent the purpose of a non-text element. This provision requires that when an image indicates a navigational action such as "move to the next screen" or "go back to the top of the page," the image must be accompanied by actual text that states the purpose of the image. This provision also requires that when an image is used to represent page content, the image must have a text description accompanying it that explains the meaning of the image.

The types of non-text elements requiring actual text descriptions are limited to those elements that provide information required for comprehension of content or those used to facilitate navigation.

Audio is a non-textual element and therefore requires that when audio presentations are available on a multimedia web page, or a multimedia presentation, the audio portion must be captioned. A text equivalent of the audio must be provided if the audio is part of a multimedia presentation, Multimedia includes both audio and video. If the presentation is audio only, a text transcript would meet this requirement.

User agents should use modality-specific text messages in the user interface (e.g., graphical scroll bars, beeps, and flashes) as long as redundant mechanisms are available or possible. These redundant mechanisms will benefit all users, not just users with disabilities.

508 Software (Subpart B)(1194.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.

508 Web (Subpart B)(1194.22)

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

508 Functional Performance (Subpart C)

508 Information, Documentation, and Support (Subpart D)

None or In Progress of Mapping

Comparison

Comment:
The first thing that comes to mind for text input is the address bar and form controls. Both, allow the user to input text information or make selections. UAAG does have requirements pertaining to "content focus" such as: focus and selection conventions 7.1, input configuration 7.2, highlight selection and content focus 10.2, and current user binding 11.1. All of these checkpoints imply the user knows where they (focus and selection) are in a v iewport and can interact (input configuration and binding) with the content. An important text attribute is "selection," that is, is the content selected or highlighted.

UAAG 1.0 Requirements & Priority

1.3 Provide text messages
Ensure that every message (e.g., prompt, alert, notification, etc.) that is a non-text element and is part of the user agent user interface has a text equivalent.

Who benefits: Users with blindness, deafness, or who are hard of hearing. Mechanisms that are redundant to audio will benefit individuals who are deaf, hard of hearing, or operating the user agent in a noisy or silent environment where the use of sound is not practical.

[Priority 1]

2.1 Render content according to specification

Render content according to format specification (e.g., for a markup language or style sheet).
When a rendering requirement of another specification contradicts a requirement of the current document, the user agent may disregard the rendering requirement of the other specification and still satisfy this checkpoint.
Rendering requirements include format-defined interactions between author preferences and user preferences/capabilities (e.g., when to render the "alt" attribute in HTML, the rendering order of nested OBJECT elements in HTML, test attributes in SMIL, and the cascade in CSS2).

Who benefits: Users with disabilities when specifications include features that promote accessibility (e.g., scalable graphics benefit users with low vision, style sheets allow users to override author and user style sheets).

[Priority 1]

6.6 Conventional keyboard APIs
Implement standard accessibility APIs (e.g., of the operating environment). Where these APIs do not enable the user agent to satisfy the requirements of this document, use the standard input and output APIs of the operating environment.

Who benefits: Users with a disability who rely on assistive technologies for input.

[Priority 1]

6.8 DOM CSS access
For an API implemented to satisfy requirements of this document, support the character encodings required for that API.

Who benefits: Users with a disability who rely on assistive technologies for input and output.

[Priority 1]

7.1 Focus and selection conventions
Follow operating environment conventions that benefit accessibility when implementing the selection , content focus , and user interface focus.

Who benefits: Many users with many types of disabilities.

[Priority 1]

7.2 Respect input configuration conventions
Ensure that default input configurations of the user agent do not interfere with operating environment accessibility conventions (e.g., for keyboard accessibility).

Who benefits: Many users with many types of disabilities.

[Priority 1]

10.2 Highlight selection and content focus

Provide a mechanism for highlighting the selection and content focus of each viewport.
The highlight mechanism must not rely on color alone.
Allow global configuration of selection and focus highlight styles.
For graphical viewports, if the highlight mechanism involves colors or text decorations , offer a range of colors or text decorations to the user that includes at least:
*the range offered by the conventional utility available in the operating environment that allows users to choose colors or text decorations, *or,
if no such utility is available, the range of colors or text decorations supported by the conventional APIs of the operating environment for specifying colors or drawing text.

Who benefits: Users with color deficiencies or blindness, for whom color will not be useful. Also, some devices may not render colors (e.g., speech synthesizers, black and white screens).

[Priority 1]

11.1Current user bindings
Provide information to the user about current user preferences for input configurations. To satisfy this checkpoint, the user agent may make available binding information in a centralized fashion (e.g., a list of bindings) or a distributed fashion (e.g., by listing keyboard shortcuts in user interface menus).

Who benefits: Many users benefit from direct access to important user agent functionalities (e.g., via a single key stroke or short voice command): users with blindness (for whom the pointing device is not useful), users with poor physical control (who might mistakenly repeat a key stroke), users who fatigue easily (for whom the composition of key sequences is a significant effort), users who cannot remember key combinations, and any user who wants to operate the user agent efficiently.

[Priority 1]

7. Contrast, Color and Other User Settings / Selections

Relevance to Accessibility

This requirement can often improve accessibility for persons with disabilities through increasing their efficiency with a system by selecting colors, contrast, keyboard repeat rate, and keyboard sensitivity settings provided by an operating system. When an application disables these system-wide settings, accessibility is reduced. This provision is aimed at allowing users to select personalized settings which cannot be disabled by software programs. Does this provision mean that programs may not use any custom settings? This provision allows programs to have unlimited options for customizing the display of the programs' content. However, there must be a section in the software that tells the program not to use its own setting, but to use whatever settings are already in place before the program starts. A simple menu selection, for example under a view, or options menu, might be a checkbox that lets the user check "use system display setting."

508 Software (Subpart B)(1194.21)

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

508 Web (Subpart B)(1194.22)

None or In Progress of Mapping

508 Functional Performance (Subpart C)

(c)
At least one mode of operation and information retrieval that does not require user hearing must be provided, or support for assistive technology used by people who are deaf or hard of hearing shall be provided. This provision is met when a product provides visual redundancy for any audible cues or audio output. If this redundancy cannot be built-into a product then the product shall support the use of assistive technology.

(d)
Requires that audio information important for the use of a product, must be provided in an enhanced auditory fashion by allowing for an increase in volume and/or altering the tonal quality or increasing the signal-to-noise ratio.

(e)
At least one mode of operation and information retrieval which does not require user speech must be provided, or support for assistive technology shall be provided. Most products do not require speech input. However, if speech input is required to operate a product, this paragraph requires that at least one alternative input mode also be provided. For example, an interactive telephone menu that requires the user to say or press "one" would meet this provision.

508 Information, Documentation, and Support (Subpart D)

None or In Progress of Mapping

Comparison

Comment:
The checkpoints of Guideline 4 require configuration and control of color, text size, playback rates, some audio characteristics, and some speech characteristics. The UAAG checkpoint 7.3 Operating Environment Conventions requires the user agent to follow operating environment conventions. These conventions while also including input conventions (mouse keys, etc.) also cover the setting of environment colors (foreground, background, selection, high contrast mode, etc.). The user agent should not override these user settings.

UAAG 1.0 Requirements & Priority

@@ What do you think?

2.12
Render content according to specification.

Render content according to format specification (e.g., for a markup language or style sheet).
When a rendering requirement of another specification contradicts a requirement of the current document, the user agent may disregard the rendering requirement of the other specification and still satisfy this checkpoint.
Rendering requirements include format-defined interactions between author preferences and user preferences/capabilities (e.g., when to render the "alt" attribute in HTML, the rendering order of nested OBJECT elements in HTML, test attributes in SMIL, and the cascade in CSS2).

Who benefits:

[Priority 1]

3.1 Toggle background images
Allow configuration not to render background image content.

Who benefits: Some users with a cognitive disability or color deficiencies who may find it difficult or impossible to read superimposed text or understand other superimposed content.

[Priority 1]

3.2 Toggle audio, video, animated images
Allow configuration not to render audio, video, or animated image content, except on explicit user request. This configuration is required for content rendered without any user interaction (including content rendered on load or as the result of a script), as well as content rendered as the result of user interaction (e.g., when the user activates a link)

Who benefits: Some users with a cognitive disability, for whom an excess of visual information (and in particular animated information) might it impossible to understand parts of content. Also, audio rendered automatically on load may interfere with speech synthesizers.

[Priority 1]

3.5 Toggle content refresh

Allow configuration so that the user agent only refreshes content on explicit user request.
In this configuration, alert the user of the refresh rate specified in content, and allow the user to request fresh content manually (e.g., by following a link or confirming a prompt).
When the user chooses not to refresh content, the user agent may ignore that content; buffering is not required.

Who benefits: Automatically changing content can disorient some users with a cognitive disability, users with blindness or low vision, and most users.

[Priority 1]

4.1 Configure text size

Allow global configuration of the reference size of visually rendered text, with an option to override reference sizes specified by the author or user agent defaults.
Offer a range of text sizes to the user

Who benefits: Users with low vision benefit from the ability to increase the text size. Note that some users may also benefit from the ability to choose small font sizes (e.g., users of screen readers who wish to have more content per screen so they have to scroll less frequently).

[Priority 1]

4.2 Configure font family

Allow global configuration of the font family of all visually rendered text, with an option to override font families specified by the author or by user agent defaults.
Offer a range of font families to the use

Who benefits: Users with low vision or some users with a cognitive disability or reading disorder require the ability to change the font family of text in order to read it.

[Priority 1]

4.3 Configure text colors

Allow global configuration of the foreground and background color of all visually rendered text, with an option to override foreground and background colors specified by the author or user agent defaults.
Offer a range of colors to the user

Who benefits: Users with color deficiencies and some users with a cognitive disability.

[Priority 1]

4.4 Slow multimedia.

Allow the user to slow the presentation rate of rendered audio and animations (including video and animated images).
For a visual track , provide at least one setting between 40% and 60% of the original speed.
For a prerecorded audio track including audio-only presentations , provide at least one setting between 75% and 80% of the original speed.
When the user agent allows the user to slow the visual track of a synchronized multimedia presentation to between 100% and 80% of its original speed, synchronize the visual and audio tracks. Below 80%, the user agent is not required to render the audio track.

Who benefits: Some users with a learning or cognitive disability, or some users with newly acquired sensory limitations (such as a person who is newly blind and learning to use a screen reader). Users who have beginning familiarity with a natural language may also benefit.

[Priority 1]

4.5 Start, stop, pause, and navigate multimedia

Allow the user to stop, pause, and resume rendered audio and animations (including video and animated images) that last three or more seconds at their default playback rate.
Allow the user to navigate efficiently within audio and animations (including video and animated images) that last three or more seconds at their default playback rate. The user agent may satisfy this requirement through forward and backward sequential access techniques (e.g., advance three seconds), or direct access techniques (e.g., play starting at the 10-minute mark), or some combination.
When serial techniques are used to satisfy the previous requirement, the user agent is not required to play back content during serial advance or rewind (though doing so may help orient the user).
The user agent is not required to satisfy this checkpoint for audio and animations whose recognized role is to create a purely stylistic effect.
When the user pauses a real-time audio or animation, the user agent may discard packets that continue to arrive during the pause.

Who benefits: Some users with a cognitive disability. Some users with a physical disability who may not have fine control over advance and rewind functionalities will find useful the ability to advance or rewind the presentation in (configurable) increments.

[Priority 1]

4.6 Position captions

For graphical viewports, allow the user to position rendered captions with respect to synchronized visual tracks as follows: o if the user agent satisfies this checkpoint by using a markup language or style sheet language to provide configuration or control, then the user agent must allow the user to choose from among at least the range of positions enabled by the format o otherwise the user agent must allow both non-overlapping and overlapping positions (e.g., by rendering captions in a separate viewport that may be positioned on top of the visual track).
In either case, the user agent must allow the user to override the author's specified position.
The user agent is not required to change the layout of other content (i.e., reflow) after the user has changed the position of captions.
The user agent is not required to make the captions background transparent when those captions are rendered above a related video track.

Who benefits: Some users (e.g., with a cognitive disability) may need to be able to position captions, etc. so that they do not obscure other content or are not obscured by other content. Other users (e.g., users with a screen magnifier) may require pieces of content to be in a particular relation to one another, even if this means that some content will obscure other content.

[Priority 1]

Follow operating environment conventions that benefit accessibility. In particular, follow conventions that benefit accessibility for user interface design, keyboard configuration, product installation, and documentation .
For the purposes of this checkpoint, an operating environment convention that benefits accessibility is either *one identified as such in operating environment design or accessibility guidelines, or *one that allows the author to satisfy any requirement of the "Web Content Accessibility Guidelines 1.0" [WCAG10] or of the current document.

Who benefits: Many users with many types of disabilities.

[Priority 2]

10.6 Provide link information
Provide a mechanism for highlighting the selection and content focus. Allow the user to configure the highlight styles. The highlight mechanism must not rely on color alone. For graphical viewports, if the highlight mechanism involves colors or text decorations, allow the user to choose from among the full range of colors or text decorations supported by the operating environment.

Who benefits: Users for whom following a link may lead to loss of context upon return, including some users with blindness and low vision, a memory or cognitive disability, or a physical disability.

[Priority 3]

8. Animation and Multimedia

Relevance to Accessibility

Captioning for the audio portion and audio description of visual information of multimedia presentations are considered equivalent alternatives. This provision requires that when an audio portion of a multimedia production is captioned, as required in provision (a), the captioning must be synchronized with the audio. Synchronized captioning would be required so someone reading the captions could also watch the speaker and associate relevant body language with the speech.

The use of animation on a screen can pose serious access problems for users of screen readers or other assistive technology applications. When important elements such as push-buttons or relevant text are animated, the user of assistive technology cannot access the application reliably. This provision requires that in addition to the animation, an application shall provide an option to turn off animation.

508 Software (Subpart B)(1194.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.

508 Web (Subpart B)(1194.22)

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

508 Functional Performance (Subpart C)

508 Information, Documentation, and Support (Subpart D)

None or In Progress of Mapping

Comparison

Comment:
This is an interesting one because it sounds like an authoring requirement to me. Our checkpoints for control of animation (including video, animated images, and animated text) are: 3.2, 3.3, 4.4, 4.5, 4.7, and 4.8.

UAAG 1.0 Requirements & Priority

2.1 Render content according to specification

Render content according to format specification (e.g., for a markup language or style sheet).
When a rendering requirement of another specification contradicts a requirement of the current document, the user agent may disregard the rendering requirement of the other specification and still satisfy this checkpoint.
Rendering requirements include format-defined interactions between author preferences and user preferences/capabilities (e.g., when to render the "alt" attribute in HTML, the rendering order of nested OBJECT elements in HTML, test attributes in SMIL, and the cascade in CSS2).

[Priority 1]

2.5 Make captions, transcripts available
Allow configuration or control to render text transcripts , collated text transcripts , captions , and auditory descriptions at the same time as the associated audio tracks and visual tracks.

Who benefits: Users with blindness or low vision (auditory descriptions and text captions, etc.) and users with deafness or who are hard of hearing.

[Priority 1]

2.6 Respect synchronization cues
Respect synchronization cues (e.g., in markup) during rendering.

Who benefits: Users with deafness or who are hard of hearing (e.g., for auditory descriptions and audio tracks), and some users with a cognitive disability.

[Priority 1]

4.4 Slow multimedia.

Allow the user to slow the presentation rate of rendered audio and animations (including video and animated images).
For a visual track , provide at least one setting between 40% and 60% of the original speed.
For a prerecorded audio track including audio-only presentations , provide at least one setting between 75% and 80% of the original speed.
When the user agent allows the user to slow the visual track of a synchronized multimedia presentation to between 100% and 80% of its original speed, synchronize the visual and audio tracks. Below 80%, the user agent is not required to render the audio track.

[Priority 1]

4.5 Start, stop, pause, and navigate multimedia

Allow the user to stop, pause, and resume rendered audio and animations (including video and animated images) that last three or more seconds at their default playback rate.
Allow the user to navigate efficiently within audio and animations (including video and animated images) that last three or more seconds at their default playback rate. The user agent may satisfy this requirement through forward and backward sequential access techniques (e.g., advance three seconds), or direct access techniques (e.g., play starting at the 10-minute mark), or some combination.
When serial techniques are used to satisfy the previous requirement, the user agent is not required to play back content during serial advance or rewind (though doing so may help orient the user).
The user agent is not required to satisfy this checkpoint for audio and animations whose recognized role is to create a purely stylistic effect.
When the user pauses a real-time audio or animation, the user agent may discard packets that continue to arrive during the pause.

[Priority 1]

4.6 Position captions

For graphical viewports, allow the user to position rendered captions with respect to synchronized visual tracks as follows: o if the user agent satisfies this checkpoint by using a markup language or style sheet language to provide configuration or control, then the user agent must allow the user to choose from among at least the range of positions enabled by the format o otherwise the user agent must allow both non-overlapping and overlapping positions (e.g., by rendering captions in a separate viewport that may be positioned on top of the visual track).
In either case, the user agent must allow the user to override the author's specified position.
The user agent is not required to change the layout of other content (i.e., reflow) after the user has changed the position of captions.
The user agent is not required to make the captions background transparent when those captions are rendered above a related video track.

[Priority 1]

9. Color Conveying Information

Relevance to Accessibility

When colors are used as the sole method for identifying screen elements or controls, persons who are color blind as well as those people who are blind or have low vision may find the information unusable. A software program that requires a user to distinguish between otherwise identical red and blue squares for different functions (e.g., printing a document versus saving a file) would pose problems for anyone who was color blind and would generally be very difficult to run with assistive technology. Screen reading software can announce color changes. However, this is an "on/off" feature. This means that if a user had to identify a specific color, they would have to have all colors announce which would greatly reduce the usability of the software for that person.

It is necessary to require that some other method of identification, such as text labels, must be combined with the use of color. This provision addresses not only the problem of using color to indicate emphasized text, but also the use of color to indicate an action. For example, a web page that directs a user to "press the green button to start" should also identify the green button in some other fashion than simply by color.

508 Software (Subpart B)(1194.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.

508 Web (Subpart B)(1194.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.

508 Functional Performance (Subpart C)

508 Information, Documentation, and Support (Subpart D)

None or In Progress of Mapping

Comparison

In Progress

UAAG 1.0 Requirements & Priority

2.12 Render content according to specification
Render content according to specification.

Render content according to format specification (e.g., for a markup language or style sheet).
When a rendering requirement of another specification contradicts a requirement of the current document, the user agent may disregard the rendering requirement of the other specification and still satisfy this checkpoint.
Rendering requirements include format-defined interactions between author preferences and user preferences/capabilities (e.g., when to render the "alt" attribute in HTML, the rendering order of nested OBJECT elements in HTML, test attributes in SMIL, and the cascade in CSS2).

Who benefits:

[Priority 1]

10.2 Highlight selection and content focus
Ensure that all of the default highlight styles for the selection, content focus, enabled elements, recently visited links, and fee links (1) do not rely on color alone, and (2) differ from each other, and not by color alone.

Who benefits: Users with color deficiencies or blindness, for whom color will not be useful. Also, some devices may not render colors (e.g., speech synthesizers, black and white screens).

[Priority 1]

10.6 Provide link information
Provide a mechanism for highlighting the selection and content focus. Allow the user to configure the highlight styles. The highlight mechanism must not rely on color alone. For graphical viewports, if the highlight mechanism involves colors or text decorations, allow the user to choose from among the full range of colors or text decorations supported by the operating environment.

[Priority 3]

10.7 Highlight current viewport
Provide a mechanism for highlighting the viewport with the current focus. For graphical viewports, the default highlight mechanism must not rely on color alone.

Who benefits: Users with color deficiencies or blindness, for whom color will not be useful. Also, some devices may not render colors (e.g., speech synthesizers, black and white screens).

[Priority 1]

10. Color and Contrast Variety

Relevance to Accessibility

This provision requires more than just providing color choices. The available choices must also allow for different levels of contrast. Many people experience a high degree of sensitivity to bright displays. People with this condition cannot focus on a bright screen for long because they will soon be unable to distinguish individual letters. An overly bright background causes a visual "white-out". To alleviate this problem, the user must be able to select a softer background and appropriate foreground colors. On the other hand, many people with low vision can work most efficiently when the screen is set with very sharp contrast settings. Because there is such a variance in individual needs it is necessary for a program to have a variety of color and contrast settings.

508 Software (Subpart B)(1194.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.

508 Web (Subpart B)(1194.22)

None or In Progress of Mapping

508 Functional Performance (Subpart C)

508 Information, Documentation, and Support (Subpart D)

None or In Progress of Mapping

Comparison

Comment:
All of our color requirements refer to "the full range of colors supported by the operating environment".

UAAG 1.0 Requirements & Priority

2.1 Render content according to specification

Render content according to format specification (e.g., for a markup language or style sheet).
When a rendering requirement of another specification contradicts a requirement of the current document, the user agent may disregard the rendering requirement of the other specification and still satisfy this checkpoint.
Rendering requirements include format-defined interactions between author preferences and user preferences/capabilities (e.g., when to render the "alt" attribute in HTML, the rendering order of nested OBJECT elements in HTML, test attributes in SMIL, and the cascade in CSS2).

[Priority 1]

2.3 Render conditional content.

Allow configuration to provide access to each piece of unrendered conditional content "C".
The configuration may be a switch that, for all content, turns on or off the access mechanisms described in the next provision.
When a specification does not explain how to provide access to this content, do so as follows:
- If C is a summary, title, alternative, description, or expansion of another piece of content D, provide access through at least one of the following mechanisms:
  - (1a) render C in place of D;
  - (2a) render C in addition to D;
  - (3a) provide access to C by querying D. In this case, the user agent must also alert the user, on a per-element basis, to the existence of C (so that the user knows to query D);
  - (4a) allow the user to follow a link to C from the context of D.
- Otherwise, provide access to C through at least one of the following mechanisms:
  - (1b) render a placeholder for C, and allow the user to view the original author-supplied content associated with each placeholder;
  - (2b) provide access to C by query (e.g., allow the user to query an element for its attributes). In this case, the user agent must also alert the user, on a per-element basis, to the existence of C;
  - (3b) allow the user to follow a link in context to C.
To satisfy this checkpoint, the user agent may provide access on a per-element basis (e.g., by allowing the user to query individual elements) or for all elements (e.g., by offering a configuration to render conditional content all the time).

Who benefits:

[Priority 1]

3.1 Toggle background images
Allow configuration not to render background image content.

Who benefits: Some users with a cognitive disability or color deficiencies who may find it difficult or impossible to read superimposed text or understand other superimposed content.

[Priority 1]

4.1 Configure text size

Allow global configuration of the reference size of visually rendered text, with an option to override reference sizes specified by the author or user agent defaults.
Offer a range of text sizes to the user

[Priority 1]

4.3 Configure text colors

Allow global configuration of the foreground and background color of all visually rendered text, with an option to override foreground and background colors specified by the author or user agent defaults.
Offer a range of colors to the user

Who benefits: Users with color deficiencies and some users with a cognitive disability.

[Priority 1]

5.4 Selection and focus in viewport
Ensure that when a viewport's selection or content focus changes, it is at least partially in the viewport after the change.

Who benefits: Users who may be disoriented by a change in focus or selection that is not reflected in the viewport. This includes some users with blindness or low vision, and some users with a cognitive disability.

[Priority 2]

10.2 Highlight selection and content focus

Provide a mechanism for highlighting the selection and content focus of each viewport.
The highlight mechanism must not rely on color alone.
Allow global configuration of selection and focus highlight styles.
For graphical viewports, if the highlight mechanism involves colors or text decorations , offer a range of colors or text decorations to the user that includes at least:
*the range offered by the conventional utility available in the operating environment that allows users to choose colors or text decorations, *or,
if no such utility is available, the range of colors or text decorations supported by the conventional APIs of the operating environment for specifying colors or drawing text.

Who benefits: Users with color deficiencies or blindness, for whom color will not be useful. Also, some devices may not render colors (e.g., speech synthesizers, black and white screens).

[Priority 1]

Who benefits: Users with color deficiencies or blindness, for whom color will not be useful. Also, some devices may not render colors (e.g., speech synthesizers, black and white screens).

[Priority 1]

11. Blinking and Flicker

Relevance to Accessibility

This requirement is necessary because some individuals with photosensitive epilepsy can have a seizure triggered by displays that flicker or flash, particularly if the flash has a high intensity and is within certain frequency ranges. The 2 Hz limit was chosen to be consistent with proposed revisions to the ADA Accessibility Guidelines which, in turn, are being harmonized with the International Code Council (ICC)/ANSI A117 standard, "Accessible and Usable Buildings and Facilities", ICC/ANSI A117.1-1998 which references a 2 Hz limit. An upper limit was identified at 55 Hz.

Flashing or flickering elements are usually added through technologies such as animated gif's, Java applets, or third-party plug-ins or applications.

508 Software (Subpart B)(1194.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.

508 Web (Subpart B)(1194.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.

508 Functional Performance (Subpart C)

None or In Progress of Mapping

508 Information, Documentation, and Support (Subpart D)

None or In Progress of Mapping

Comparison

Comment:
We have explicitly chosen * not * to include this requirement for the user interface. We discussed whether our content requirements should be extended to the user interface in general, and decided against this.

UAAG 1.0 Requirements & Priority

3.3 Toggle animated / blinking text***

Allow configuration to render animated or blinking text as motionless, unblinking text.
In this configuration, the user must still have access to the same text content, but the user agent may render it in a separate viewport (e.g., for large amounts of streaming text).

Who benefits: Flashing content may trigger seizures in people with photosensitive epilepsy, or may make a Web page too distracting to be usable by someone with a cognitive disability. Blinking text can affect screen reader users, since screen readers (in conjunction with speech synthesizers or braille displays) may re-render the text every time it blinks.

[Priority 1]

3.4 Toggle scripts

Allow configuration not to execute any executable content (e.g., scripts and applets).
In this configuration, provide an option to alert the user when executable content is available (but has not been executed).
The user agent is only required to alert the user to the presence of more than zero scripts or applets (i.e., per-element alerts are not required).

Who benefits: Control of executable content is particularly important as it can cause the screen to flicker, since people with photosensitive epilepsy can have seizures triggered by flickering or flashing, particularly in the 4 to 59 flashes per second (Hertz) range. Peak sensitivity to flickering or flashing occurs at 20 Hertz.

[Priority 1]

12. Form Controls

Relevance to Accessibility

If keyboard alternatives are provided for navigating through a form, and all elements of the form are labeled with text located in close proximity to the field that is to be completed, the form will most likely meet this provision. Attention must be paid to the placement of field labels. On a webpage, a label can have a direct association with a particular field that is indicated in the HTML code. Assistive technology can interpret the HTML and correctly announce the appropriate label. There is no similar method for forms in software programs. Therefore, the label must be in a logical position relative to the input areas. For example, placing labels to the immediate left of where the user is to enter information is by far the most logical position for the label.

508 Software (Subpart B)(1194.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.

508 Web (Subpart B)(1194.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.

508 Functional Performance (Subpart C)

508 Information, Documentation, and Support (Subpart D)

None or In Progress of Mapping

Comparison

In Progress

UAAG 1.0 Requirements & Priority

2.1 Render content according to specification

Render content according to format specification (e.g., for a markup language or style sheet).
When a rendering requirement of another specification contradicts a requirement of the current document, the user agent may disregard the rendering requirement of the other specification and still satisfy this checkpoint.
Rendering requirements include format-defined interactions between author preferences and user preferences/capabilities (e.g., when to render the "alt" attribute in HTML, the rendering order of nested OBJECT elements in HTML, test attributes in SMIL, and the cascade in CSS2).

[Priority 1]

2.3 Render conditional content

Allow configuration to provide access to each piece of unrendered conditional content "C".
The configuration may be a switch that, for all content, turns on or off the access mechanisms described in the next provision.
When a specification does not explain how to provide access to this content, do so as follows:
- If C is a summary, title, alternative, description, or expansion of another piece of content D, provide access through at least one of the following mechanisms:
  - (1a) render C in place of D;
  - (2a) render C in addition to D;
  - (3a) provide access to C by querying D. In this case, the user agent must also alert the user, on a per-element basis, to the existence of C (so that the user knows to query D);
  - (4a) allow the user to follow a link to C from the context of D.
- Otherwise, provide access to C through at least one of the following mechanisms:
  - (1b) render a placeholder for C, and allow the user to view the original author-supplied content associated with each placeholder;
  - (2b) provide access to C by query (e.g., allow the user to query an element for its attributes). In this case, the user agent must also alert the user, on a per-element basis, to the existence of C;
  - (3b) allow the user to follow a link in context to C.
To satisfy this checkpoint, the user agent may provide access on a per-element basis (e.g., by allowing the user to query individual elements) or for all elements (e.g., by offering a configuration to render conditional content all the time).

Who benefits: Any user for whom the author has provided conditional content for accessibility purposes. This includes: text equivalents for users with blindness or low vision, or users who are deaf-blind, and captions, for users who with deafness or who are hard of hearing.

[Priority 1]

5.5 Confirm form submission

Allow configuration to prompt the user to confirm (or cancel) any form submission.
Configuration is preferred, but it not required if forms can only ever be submitted on explicit user request.

Who benefits: Any user who might be disoriented by an automatic form submission (e.g., users with blindness who are are navigating serially through select box options, or some users with a cognitive disability) or who might inadvertently submit a form (e.g., some users with a physical disability).

[Priority 2]

10.5 Outline view

Make available to the user an "outline" view of content, composed of labels for important structural elements (e.g., heading text, table titles, form titles, @@ frame titles, @@ etc.).
What constitutes a label is defined by each markup language specification. A label is not required to be text only.

Who benefits: The outline view is a type of summary view, and will benefit some users with a memory or cognitive disability, as well as users for whom serial access is time consuming (e.g., some users with blindness or a physical disability, or some users with low vision). A navigable outline view will add further benefits for these users.

[Priority 2]

13. Tables and Table Markup

Relevance to Accessibility

Paragraphs (g) and (h) permit the use of tables, but require that the tables be coded according to the rules of the markup language being used for creating tables. Large tables of data can be difficult to interpret if a person is using a non-visual means of accessing the web. Users of screen readers can easily get "lost" inside a table because it may be impossible to associate a particular cell that a screen reader is reading with the corresponding column headings and row names. For instance, assume that a salary table includes the salaries for federal employees by grade and step. Each row in the table may represent a grade scale and each column may represent a step. Thus, finding the salary corresponding to a grade 9, step 5 may involve finding the cell in the ninth row and the fifth column. For a salary chart of 15 grade scales and 10 steps, the table will have at least 150 cells. Without a method to associate the headings with each cell, it is easy to imagine the difficulty a user of assistive technology may encounter with the table. Section 1194.22 (g) and (h) state that when information is displayed in a table format, the information shall be laid out using appropriate table tags as opposed to using a preformatted table in association with the "<pre>" tag. Web authors are also required to use one of several methods to provide an association between a header and its related information.

508 Software (Subpart B)(1194.21)

508 Web (Subpart B)(1194.22)

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

508 Functional Performance (Subpart C)

508 Information, Documentation, and Support (Subpart D)

None or In Progress of Mapping

Comparison

In Progress

UAAG 1.0 Requirements & Priority

2.1 Render content according to specification (Both (g) and (h))

Render content according to format specification (e.g., for a markup language or style sheet).
When a rendering requirement of another specification contradicts a requirement of the current document, the user agent may disregard the rendering requirement of the other specification and still satisfy this checkpoint.
Rendering requirements include format-defined interactions between author preferences and user preferences/capabilities (e.g., when to render the "alt" attribute in HTML, the rendering order of nested OBJECT elements in HTML, test attributes in SMIL, and the cascade in CSS2).

[Priority 1]

10.1 Table orientation (Both (g) and (h))
Make available to the user the purpose of each rendered table (e.g., as expressed in a summary or table caption) and the relationships among the table cells and headers

Who benefits: Users for whom summaries are important (e.g., some users with a cognitive or memory disability), and for whom two-dimensional relationships may be difficult to process (e.g., users with blindness who have serial access to the content, or some users with a cognitive disability). Renderings that provide easy access to cell header information will also help some users with low vision or a physical disability, for whom it may be time-consuming to scroll in order to locate relevant headers.

[Priority 1]

10.5 Outline view

Make available to the user an "outline" view of content, composed of labels for important structural elements (e.g., heading text, table titles, form titles, @@ frame titles, @@ etc.).
What constitutes a label is defined by each markup language specification. A label is not required to be text only.

[Priority 2]

14. Frames ( Labels, Titles & Outlines )

Relevance to Accessibility

Frames provide a means of visually dividing the computer screen into distinct areas that can be separately rewritten. Unfortunately, frames can also present difficulties for users with disabilities when those frames are not easily identifiable to assistive technology. For instance, a popular use of frames is to create "navigational bars" in a fixed position on the screen and have the content of the web site retrievable by activating one of those navigational buttons. The new content is displayed another area of the screen. Because the navigational bar doesn't change, it provides a stable "frame-of-reference" for users and makes navigation much easier. However, users with disabilities may become lost if the differences between the two frames are not clearly established.

The most obvious way to accomplish this requirement is to include text within the body of each frame that clearly identifies the frame. For instance, in the case of the navigation bar, a web developer should consider putting words such as "Navigational Links" at the beginning of the contents of the frame to let all users know that the frame depicts navigational links. Providing titles like this at the top of the contents of each frame will satisfy these requirements. An additional measure that should be considered by agencies is to include meaningful text in the <frame> tag's "title" attribute. Although not currently supported by major manufacturers of assistive technology, the "title" attribute is part of the HTML 4.0 specification and was intended to let web developers include a description of the frame as a quote-enclosed string. Demonstrating the use of the "title" attribute requires a basic understanding of how frames are constructed. When frames are used in a web page, the first page that is loaded must include a <frameset> tag that encloses the basic layout of the frames on the page. Within the <frameset> tag, <frame> tags specify the name, initial contents, and appearance of each separate frame. Thus, the following example uses the "title" attribute to label one frame "Navigational Links Frame" and the second frame "Contents Frame."

508 Software (Subpart B)(1194.21)

508 Web (Subpart B)(1194.22)

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

508 Functional Performance (Subpart C)

508 Information, Documentation, and Support (Subpart D)

None or In Progress of Mapping

Comparison

Comment:
We have frame titles being included in the outline view. To see related information in 9.9 Structured Navigation where FRAME is specifically mentioned in the UAAG 1.0 Techniques Document as a navigable element.

@@ SEE: Orientation @@

UAAG 1.0 Requirements & Priority

2.1 Render content according to specification (Both (g) and (h))

Render content according to format specification (e.g., for a markup language or style sheet).
When a rendering requirement of another specification contradicts a requirement of the current document, the user agent may disregard the rendering requirement of the other specification and still satisfy this checkpoint.
Rendering requirements include format-defined interactions between author preferences and user preferences/capabilities (e.g., when to render the "alt" attribute in HTML, the rendering order of nested OBJECT elements in HTML, test attributes in SMIL, and the cascade in CSS2).

[Priority 1]

10.5 Outline view

Make available to the user an "outline" view of content, composed of labels for important structural elements (e.g., heading text, table titles, form titles, etc.).
What constitutes a label is defined by each markup language specification. A label is not required to be text only.

[Priority 2]

15. Style Sheets

Relevance to Accessibility

Style sheets can enable users to define specific viewing preferences to accommodate their disability. For instance, users with low vision may create their own style sheet so that, regardless of what web pages they visit, all text is displayed in an extra large font with white characters on a black background. If designers set up their pages to override user-defined style sheets, people with disabilities may not be able to use those pages. For good access, therefore, it is critical that designers ensure that their web pages do not interfere with user-defined style sheets.

508 Software (Subpart B)(1194.21)

508 Web (Subpart B)(1194.22)

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

508 Functional Performance (Subpart C)

508 Information, Documentation, and Support (Subpart D)

None or In Progress of Mapping

Comparison

In Progress

UAAG 1.0 Requirements & Priority

4.17 Choose style sheets

For user agents that support style sheets:

Allow the user to choose from and apply available author style sheets (in content).
Allow the user to choose from and apply available user style sheets.
Allow the user to ignore author and user style sheets.

Who benefits: Any user with a disability who needs to override the author's style sheets or user agent default style sheets in order to have control over style and presentation, or who needs to tailor the style of rendered content to meet their own needs.

[Priority 1]

16. Image Maps

Relevance to Accessibility

An "image map" is a picture (often an actual map) on a web page that provides different "links" to other web pages, depending on where a user clicks on the image. There are two basic types of image maps: "client-side image maps" and "server-side image maps". With client-side image maps, each "active region" in a picture can be assigned its own "link" (called a URL or "Uniform Resource Locator") that specifies what web page to retrieve when a portion of the picture is selected. HTML allows each active region to have its own alternative text, just like a picture can have alternative text ( see §1194.22(a)). By contrast, clicking on a location of a server-side image map only specifies the coordinates within the image when the mouse was depressed. The ultimate selection of the link or URL must be deciphered by the computer serving the web page.

When a web page uses a server-side image map to present the user with a selection of options, browsers cannot indicate to the user the URL that will be followed when a region of the map is activated. Therefore, the redundant text link is necessary to provide access to the page for anyone not able to see or accurately click on the map.

Unlike server-side image maps, the client-side image map allow an author to assign text to each image map "hot spots". This feature means that someone using a screen reader can easily identify and activate regions of the map. An explanation of how these image maps are constructed will help clarify this issue.

508 Software (Subpart B)(1194.21)

Not applicable.

508 Web (Subpart B)(1194.22)

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

(f)
Client-Side Image Map
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.

508 Functional Performance (Subpart C)

508 Information, Documentation, and Support (Subpart D)

None or In Progress of Mapping

Comparison

In Progress

@@ Katie: Needs Work --- SEE: Navigation @@

UAAG 1.0 Requirements & Priority

2.1 Render content according to specification

Render content according to format specification (e.g., for a markup language or style sheet).
When a rendering requirement of another specification contradicts a requirement of the current document, the user agent may disregard the rendering requirement of the other specification and still satisfy this checkpoint.
Rendering requirements include format-defined interactions between author preferences and user preferences/capabilities (e.g., when to render the "alt" attribute in HTML, the rendering order of nested OBJECT elements in HTML, test attributes in SMIL, and the cascade in CSS2).

[Priority 1]

17. Scripting

Relevance to Accessibility

Web page authors have a responsibility to provide script information in a fashion that can be read by assistive technology. When authors do not put functional text with a script, a screen reader will often read the content of the script itself in a meaningless jumble of numbers and letters. Although this jumble is text, it cannot be interpreted or used.

508 Software (Subpart B)(1194.21)

508 Web (Subpart B)(1194.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.

508 Functional Performance (Subpart C)

508 Information, Documentation, and Support (Subpart D)

None or In Progress of Mapping

Comparison

In Progress

UAAG 1.0 Requirements & Priority

[Priority 1]

3.4 Toggle scripts

Allow configuration not to execute any executable content (e.g., scripts and applets).
In this configuration, provide an option to alert the user when executable content is available (but has not been executed).
The user agent is only required to alert the user to the presence of more than zero scripts or applets (i.e., per-element alerts are not required).

[Priority 1]

18. Applets and Plug-ins

Relevance to Accessibility

While most web browsers can easily read HTML and display it to the user, several private companies have developed proprietary file formats for transmitting and displaying special content, such as multimedia or very precisely defined documents. Because these file formats are proprietary, web browsers cannot ordinarily display them. To make it possible for these files to be viewed by web browsers, add-on programs or "plug-ins" can be downloaded and installed on the user's computer that will make it possible for their web browsers to display or play the content of the files. This provision requires that web pages that provide content such as Real Audio or PDF (Adobe Acrobat's Portable Document Format) files also provide a link to a plug-in that will meet the software provisions. It is very common for a web page to provide links to needed plug-ins. For example, web pages containing Real Audio almost always have a link to a source for the necessary player. This provision places a responsibility on the web page author to know that a compliant application exists, before requiring a plug-in.

508 Software (Subpart B)(1194.21)

508 Web (Subpart B)(1194.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).

508 Functional Performance (Subpart C)

508 Information, Documentation, and Support (Subpart D)

None or In Progress of Mapping

Comparison

In Progress

@@ Katie: Needs Work --- SEE: Plug-ins @@

UAAG 1.0 Requirements & Priority

2.1 Render content according to specification (Both (g) and (h))

Render content according to format specification (e.g., for a markup language or style sheet).
When a rendering requirement of another specification contradicts a requirement of the current document, the user agent may disregard the rendering requirement of the other specification and still satisfy this checkpoint.
Rendering requirements include format-defined interactions between author preferences and user preferences/capabilities (e.g., when to render the "alt" attribute in HTML, the rendering order of nested OBJECT elements in HTML, test attributes in SMIL, and the cascade in CSS2).

[Priority 1]

3.4 Toggle scripts

Allow configuration not to execute any executable content (e.g., scripts and applets).
In this configuration, provide an option to alert the user when executable content is available (but has not been executed).
The user agent is only required to alert the user to the presence of more than zero scripts or applets (i.e., per-element alerts are not required).

[Priority 1]

19. Skip Navigation Links

Relevance to Accessibility: This provision provides a method to facilitate the easy tracking of page content that provides users of assistive technology the option to skip repetitive navigation links. Web developers routinely place a host of routine navigational links at a standard location, often across the top, bottom, or side of a page. If a nondisabled user returns to a web page and knows that he or she wants to view the contents of that particular page instead of selecting a navigation link to go to another page, he or she may simply look past the links and begin reading wherever the desired text is located. For those who use screen readers or other types of assistive technologies, however, it can be a tedious and time-consuming chore to wait for the assistive technology to work through and announce each of the standard navigational links before getting to the intended location. In order to alleviate this problem, the section 508 rule requires that when repetitive navigational links are used, there must be a mechanism for users to skip repetitive navigational links.
508 Software (Subpart B)(1194.21)
508 Web (Subpart B)(1194.22): (o)
A method shall be provided that permits users to skip repetitive navigation links.
508 Functional Performance (Subpart C): (a)
At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for assistive technology used by people who are blind or visually impaired shall be provided.; (b)
At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 (when corrected with glasses) must be provided in audio and enlarged print output that works together or independently. In the alternative, support for assistive technology used by people who are blind or who have low vision must be provided.
508 Information, Documentation, and Support (Subpart D): None or In Progress of Mapping
Comparison: Comment:
This is an authoring requirement.
UAAG 1.0 Requirements & Priority

20. Timed Response

Relevance to Accessibility

Web pages can be designed with scripts so that the web page disappears or "expires" if a response is not received within a specified amount of time. Sometimes, this technique is used for security reasons or to reduce the demands on the computer serving the web pages. Someone's disability can have a direct impact on the speed with which he or she can read, move around, or fill in a web form. For instance, someone with extremely low vision may be a slower-than-average reader. A page may "time out" before he is able to finish reading it. Many forms, when they "time out" automatically, also delete whatever data has been entered. The result is that someone with a disability who is slow to enter data cannot complete the form. For this reason, when a timed response is required, the user shall be alerted via a prompt and given sufficient time to indicate whether additional time is needed.

508 Software (Subpart B)(1194.21)

508 Web (Subpart B)(1194.22)

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

508 Functional Performance (Subpart C)

508 Information, Documentation, and Support (Subpart D)

None or In Progress of Mapping

Comparison

Comment:
This is an authoring requirement.

UAAG 1.0 Requirements & Priority

2.4 Allow time-independent interaction.

For rendered content where user input is only possible within a finite time interval controlled by the user agent, allow configuration to provide a view where user interaction is time-independent.
The user agent may satisfy this checkpoint by pausing processing automatically to allow for user input, and resuming processing on explicit user request. When this technique is used, pause at the end of each time interval where user input is possible. In the paused state:
- Alert the user that the rendered content has been paused (e.g., highlight the "pause" button in a multimedia player's control panel).
- Highlight which enabled elements are time-sensitive.
- Allow the user to interact with the enabled elements.
- Allow the user to resume on explicit user request (e.g., by pressing the "play" button in a multimedia player's control panel; see also checkpoint 4.5).
The user agent may satisfy this checkpoint by generating a time-independent ("static") view, based on the original content, that offers the user the same opportunities for interaction. The static view should reflect the structure and flow of the original time-sensitive presentation; orientation cues will help users understand the context for various interaction opportunities.
When satisfying this checkpoint for a real-time presentation, the user agent may discard packets that continue to arrive after the construction of the time-independent view (e.g., when paused or after the construction of a static view).

Who benefits: Some users with a physical disability who may not have the time to interact with the content. Also, users who may be accessing the content serially (e.g,. users with blindness or some users with a physical disability) and require more time to reach the timed content.

[Priority 1]

3.5 Toggle content refresh

Allow configuration so that the user agent only refreshes content on explicit user request.
In this configuration, alert the user of the refresh rate specified in content, and allow the user to request fresh content manually (e.g., by following a link or confirming a prompt).
When the user chooses not to refresh content, the user agent may ignore that content; buffering is not required.

Who benefits: Automatically changing content can disorient some users with a cognitive disability, users with blindness or low vision, and most users.

[Priority 1]

21. Text Only Page

Relevance to Accessibility
508 Software (Subpart B)(1194.21): Not applicable.
508 Web (Subpart B)(1194.22): (k)
A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of these standards, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.
508 Functional Performance (Subpart C): (a)
At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for assistive technology used by people who are blind or visually impaired shall be provided.; (b)
At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 (when corrected with glasses) must be provided in audio and enlarged print output that works together or independently. In the alternative, support for assistive technology used by people who are blind or who have low vision must be provided.
508 Information, Documentation, and Support (Subpart D): None or In Progress of Mapping
Comparison: In Progress
UAAG 1.0 Requirements & Priority

References


[UAAG10]: "User Agent Accessibility Guidelines 1.0", I. Jacobs, J. Gunderson, E. Hansen, eds. The latest draft of the guidelines is available at http://www.w3.org/TR/UAAG10/.
[UAAG10-TECHS]: "Techniques for User Agent Accessibility Guidelines 1.0", I. Jacobs, J. Gunderson, E. Hansen, eds., W3C Working Draft, 12 September 2001. The latest version of this document is available at http://www.w3.org/TR/UAAG10-TECHS/.
Guide to the United States Access Board Section 508 Standards: Technical Standards (1194.21 - Software) http://www.access-board.gov/sec508/guide/1194.21.htm; Technical Standards (1194.22 - Web) http://www.access-board.gov/sec508/guide/1194.22.htm; Functional Performance Criteria (1194.31) http://www.access-board.gov/sec508/guide/1194.31.htm; @@ Link not yet functional; Information, Documentation, and Support (1194.41) http://www.access-board.gov/sec508/guide/1194.41.htm; @@ Link not yet functional

Last Updated: $Date: 2001/12/20 19:40:47 $
by: Katie Haritos-Shea

Draft: Mapping Comparison Between U.S. Section 508 Standards (Combined Subparts B,C & D) and UAAG 1.0 Requirements & Priorities

W3C Internal Working Draft - November 1, 2001

Abstract

Status Of This Document

Contents

How This Document is Organized

508 v. UAAG 1.0 Requirements

1. Keyboard

2. Operating Conventions of Accessibility Features

3. Focus

4. User Interface Elements

5. (Consistency in) Programmatic Elements of Images

6. Text

7. Contrast, Color and Other User Settings / Selections

8. Animation and Multimedia

9. Color Conveying Information

10. Color and Contrast Variety

11. Blinking and Flicker

12. Form Controls

13. Tables and Table Markup

14. Frames ( Labels, Titles & Outlines )

15. Style Sheets

16. Image Maps

17. Scripting

18. Applets and Plug-ins

19. Skip Navigation Links

20. Timed Response

21. Text Only Page

References

Draft: Mapping Comparison Between
U.S. Section 508 Standards (Combined Subparts B,C & D) and
UAAG 1.0 Requirements & Priorities