Note

This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional and up-to-date details on the updates to section 508 and section 255 can be found at the Access Board web site.

EWG:Draft May 30

Editorial Working Group > Working Draft May 30

TEITAC Working Draft - Released on May 30, 2007.

This page contains the full text of all provisions as presented at the May 22-24 meeting.

Updates are due from the subcommittees by Friday, June 30. See the updated delivery plan.

How to make comments:

  • To make comments on the contents of a provision, or suggest edits, use the links below each provision or group of closely related provisions
  • Note (12 June): with concurrence of the sub-committee chairs, short headings have been added to this draft to make it easier to find a specific provision.


Contents

1. Requirements for All Product and Services

[1.1] Functional Performance Criteria

A. Without Vision

At least one mode shall be provided that allows full use of product without using vision, directly or with users' AT.

B. With Limited Vision

At least one mode shall be provided that allows full use of product without requiring visual acuity greater than 20/70, and that allows audio and enlarged text output to work together or independently, directly or with users' AT.

C. Without Hearing

At least one mode shall be provided that allows full use of product without using hearing, directly or with users' AT.

D. With Limited Hearing

Where audio information is important for the use of a product, at least one mode shall be provided that allows full use of product with enhanced audio, directly or with users' AT.

E. Without Speech

At least one mode shall be provided that allows full use of product without using speech, directly or with users' AT.

F. With Limited Reach, Strength, or Manipulation

At least one mode shall be provided that allows full use of product with limited reach and strength and without simultaneous actions, directly or with users' AT.

G. With Cognitive, Language or Learning Limitations

At least one mode shall be provided that accommodates cognitive, language or learning impairments, directly or with users' AT.

H. With Photo-Seizure Disorder

At LEAST needs to be 50 HZ - should be changed to limit to flashing no more than 3 per 1 second period that are larger that is greater 25% of the central 10 degrees of vision. (that can be made simpler by assuming viewing distance) That will eliminate worrying about small indicators or areas of the screen. Haven't worked on this yet. NOTE: Keeping flashing to less than 3 per 1 second period would meet the above spec.

(New) With Color Vision Deficits

(New) With No Reach or Touch

[1.2] General Technical Requirements

{New section. No specific provisions are yet mapped to this section}

Three new provisions in this section are proposed by Self Contained/Closed:

2. Provisions for Hardware Aspects of Products

[2.1] All Products with Hardware

{Hardware Requirements that apply to all products go here: tactile key indicators, standard ports and connections for alternative input/output devices and alternative to biometric ID}

A. Touch Operated

If a product utilizes touch screens or touch-operated controls, an input method shall be provided that complies with § 1194.23 (k) (1) through (4).

B. Free-Standing

Products which are freestanding, non-portable, and intended to be used in one location and which have operable controls shall comply with the following:

  1. The position of any operable control shall be determined with respect to a vertical plane, which is 48 inches in length, centered on the operable control, and at the maximum protrusion of the product within the 48 inch length (see Figure 1 of this part).
  2. Where any operable control is 10 inches or less behind the reference plane, the height shall be 48 inches maximum and 15 inches minimum above the floor.
  3. Where any operable control is more than 10 inches and not more than 24 inches behind the reference plane, the height shall be 46 inches maximum and 15 inches minimum above the floor.
  4. Operable controls shall not be more than 24 inches behind the reference plane (see Figure 2 of this part).

C. Standard Connection

Where provided, at least one of each type of expansion slots, ports, connectors, and wireless connection shall comply with publicly available industry standards.

D. Biometric ID

When biometric forms of user identification or control are used, an alternative form of identification or activation, which does not require the user to possess particular biological characteristics, shall also be provided.

[2.2] If the Product has Physical Controls

{Requirements for physical controls go here: ADAAG approach and reach specs for products that stand independently, ADAAG control specs for tactilely discernable, pinch/twist/grasp, repeat and status indication}

A. Mechanical Controls

All mechanically operated controls and keys shall comply with § 1194.23(k) (1) through (4)

  1. Controls and keys shall be tactilely discernible without activating the controls or keys.
  2. Controls and keys shall be operable with one hand and shall not require pinching, twisting of the wrist, or tight grasping. The force required to activate controls and keys shall be 5 lbs. (22.2 N) maximum.
  3. If key repeat is supported, the delay before repeat shall be adjustable to at least 2 seconds. Key repeat rate shall be adjustable to 2 seconds per character.
  4. The status of all locking or toggle controls or keys shall be visually discernible, and discernible either through touch or sound.

[2.3] If the product has Audio Output

{Requirements for audio output: connectors, amplification, compatibility with hearing aids}

A. Magnetic Coupling

Where a telecommunications product delivers output by an audio transducer which is normally held up to the ear, a means for effective magnetic wireless coupling to hearing technologies shall be provided that allows the user of such technologies to effectively utilize the telecommunication product. This guideline shall apply to wireless, wireline, cordless and Bluetooth?? applications.

B. Interference with Hearing Device

Interference to hearing technologies (including hearing aids, cochlear implants, and assistive listening devices) shall be reduced to the lowest possible level that allows a user of hearing technologies to utilize the telecommunications product.

C. Volume (Public Area)

When products deliver voice output in a public area, incremental volume control shall be provided with output amplification up to a level of at least 65 dB. Where the ambient noise level of the environment is above 45 dB, a volume gain of at least 20 dB above the ambient level shall be user selectable. A function shall be provided to automatically reset the volume to the default level after every use.

D. Volume (General)

For receive transmitted voice signals,

  1. line powered telecommunications products shall comply with FCC regulation §68.317 for volume control,

OR

  1. telecommunications products shall provide a built-in gain adjustable up to a minimum of 20 dB. For incremental volume control, at least one intermediate step of 12 dB of gain shall be provided.
  2. all other telecommunications products or systems that provide a function allowing voice communication shall provide a gain adjustable up to a minimum of 20? dB with incremental volume control of at least one intermediate step of 12 dB of gain provided as measured and documented in accordance with the provisions of the FCC regulation &sect68.317 for volume control.

E. Volume Reset

If the telecommunications product allows a user to adjust the receive volume, a function shall be provided to automatically reset the volume to a safe level after every use if the volume is capable of greater than 18 dB of gain along with an option for user override of that automatic default.

F. Audio Connection

When products provide auditory output, the audio signal shall be provided at a standard signal level through an industry standard connector that will allow for private listening.

3. Software & General Behavior Provisions

[3.1] All products

{Requirements that apply to all products: equivalence for visual information (active and passive), consistent use of images, no interference with access features, time/repeat adjustments, flashing, etc.}

A. Disruption of Access Features

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.

B. Timing (IVR etc)

Voice mail, messaging, auto-attendant, and interactive voice response telecommunications systems that require a response from a user within a time interval, shall give an alert when the time interval is about to run out, and shall provide sufficient time for the user to indicate more time is required.

C. Pass Through

Products that transmit or conduct information or communication shall pass through cross-manufacturer, non-proprietary, industry-standard codes, translation protocols, formats or other information necessary to provide the information or communication in a usable format. Technologies which use encoding, signal compression, format transformation, or similar techniques shall not remove information needed for access or shall restore it upon delivery. Firewalls, routers, gateways and other products that pass real-time voice communication shall also pass real-time text communication signals (including mixed voice & real-time text) that are standard for that technology platform without distortion or error beyond 1%.

  • for PSTN this would be TIA/EIA 825 Baudot.

NOTE: Only phones that are passing text signals onto another device, e.g. TTY, would be subject to this provision.

D. Timing

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

[3.2] If the Product has Visual Output or Display

{Requirements relating to active display of information: color, moving text or animation, visible focus/cursors, no override of display settings}’’

A. Contrast

When a product permits a user to adjust color and contrast settings, at least one color selection capable of producing a minimum luminosity contrast ratio of n:1 shall be provided. Default combinations of foreground and background colours (hue and luminance) should produce a minimum luminosity contrast ratio of n:1

B. Color

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

C. Color (Web)

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

D. Animation

When an informational animation is displayed that will last for more than three seconds, software shall give the user a means to pause and restart the animation. When a decorative animation is displayed that will last for more than three seconds, software shall give the user a means to stop the animation.

E. Display Attributes

Applications shall utilize user selected contrast and color selections and other individual display attributes when the availability of those selections are developed and documented according to industry standards.

F. Color Settings

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

[3.3] If the Product has Standard Keyboard or Keyboard Interface

{Requirements for keyboard operation}

A. Keyboard

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.

[3.4] If Software runs on platform with Operating System with AT Support

{Requirements for software (and driver) support for assistive technology}’’

A. AT Interoperability

Software that provides user interface objects shall either use the accessibility services provided by platform software or other services to cooperate with assistive technologies when such services allow the software to meet the accessibility provisions of this standard. Using such services, software shall:

  • provide assistive technology with object information including but not limited to:
    • role, state(s), boundary, name, and description
    • any table row & column, and row & column headers (if the object is in a table)
    • current value and any minimum or maximum (if the object represents one of a range of values)
    • relationship this object has as a label for another, or being labelled by another
    • parent or containing element, and any children objects
    • text contents, text attributes, and the boundary of text rendered to the screen
    • provide assistive technology with a list of actions that can be executed on an object and allow assistive technology to programmatically execute any of those actions;
    • allow assistive technology to track and modify focus, text insertion point, and selection attributes of user interface objects;
    • provide assistive technology with notification of events relevant to user interactions, including but not limited to changes in the object's state(s), value, name, description, or boundary
  • Source: {508}1194.21(d)
  • Subcommitee: Web/Software
  • Comments and updates for this provision

B. Bitmap Icons

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.

C. Focus Indicator

Software shall provide a visual indication of which user interface object currently has the keyboard focus. If the object is a text entry field, a visual indication of the text insertion point shall be provided, and is sufficient.

[3.5] If Software runs on “Closed” system (no AT Support)

{Requirements to make products that are closed to any type of AT usable without that AT}

A. Closed

If any functionality of a hardware or software product is closed for any reason, including hardware, setting or policy, such that assistive technology for a particular user group cannot be used with the product, then the product functionality must be fully usable by that group without AT. (Headsets for private listening are not considered AT).

4. Additional Provisions for Audio-Visual Content or Players/Displays

{Requirements for support for captions, descriptions and cross-ref to other applicable requirements in a product (hardware or software plays or displays A-V material}

A. Caption Playback

All analog television displays measured 13 inches diagonally and larger, and computer equipment that includes analog television receiver or display circuitry, shall be equipped with caption decoder circuitry which appropriately receives, decodes, and displays CEA 608-standard closed captions from broadcast, cable, satellite, videotape, and DVD signals. Wide-screen (16:9) digital television (DTV) displays measuring at least 7.8 inches vertically, DTV sets with conventional (4:3) displays measuring at least 13 inches diagonally, and stand-alone DTV tuners, whether or not they are marketed with display screens, and computer equipment that includes DTV receiver or display circuitry, shall be equipped with CEA 708-standard caption decoder circuitry which appropriately receives, decodes, and displays closed captions from broadcast, cable, satellite, videotape, and DVD signals. HD-DVD, BluRay and other digital video source devices must either pass CEA 708 data, when available, to the caption decoding circuitry of DTV displays or must decode CEA 708 data, when available, and pass an open-captioned signal to the DTV display.

B. Supplemental Audio Playback

Analog-signal television tuners, including tuner cards for use in computers, shall be equipped with secondary audio program playback circuitry for support of video description. Digital-signal television tuners, including tuner cards for use in computers, shall be equipped with ancillary audio program playback circuitry for support of video description.

C. Play Control (Audio)

The product must provide the ability to interrupt, pause, and restart the audio at anytime.

5. Additional Provisions for Real-time Voice Conversation Functionality

{Requirements for voice conversation: applications, auto-reset, text with voice conversations, IVR, Caller ID and alternative support for connections for text terminal/mic toggle. Includes VOIP}

A. Accessibility Configuration

In complying with this subpart, each agency shall:

  1. Activate accessibility features and configure telecommunications products so that they are accessible to and usable by people with disabilities.
  2. Ensure access to and use of all telecommunications relay services for incoming and outgoing calls as approved by the Federal Communications Commission pursuant to its authority under 47 U.S.C. Sec. 225, as needed to achieve functionally equivalent communication access by people with disabilities.

B. Voice Terminals without R-Text

Telecommunications terminals and other terminals capable of providing real-time voice communications which do not themselves provide TTY or other real-time text conversation functionality shall comply with the following:

  1. All analog and TDM-digital wired terminals shall support the connection of a TTY in the same location and with the permissions for use as the telephone. This shall be accomplished by providing an RJ-11 jack on the telephone, or, in the case of an analog telephone, by the use of a Y-adapter that allows both the analog telephone and the TTY to be plugged into the same line outlet, or have built in capability to support an RJ11 module that can provide a connection point for TTYs;
  2. Other types of terminals covered by this section shall support the connection of real-time text capable devices in conjunction with the voice call capability in the same location and the same permissions for use as the terminal.

    Definition: Any device that terminates one end (sender or receiver) of a communicated signal and with which an end user interacts is a terminal device.

OR
Terminal: device or devices with which the end user directly interacts and that provide the user interface.

  1. Shall be capable of allowing simultaneous speech and text conversation without interference or its microphone shall be capable of being turned on and off to allow the user to intermix speech with text [TTY] use.

C. VOIP Terminals and R-Text

The user interface of IP terminals that provide real-time voice communication shall meet the following provisions:

  1. IP terminal user interfaces that have a multiline display shall display any real-time text that is received in the standard format for that platform;
  2. IP terminal user interfaces that have the ability to generate text shall allow sending real-time text in the standard real-time text format for that platform;
  3. Such real time text send and receive capabilities shall be synchronized with voice as part of the same communication session.

D. R-Text Interoperability

Products that provide real-time voice conversation text functionality shall do so in the standard format that is supported for that transport medium.

  1. products that connect directly to the PSTN shall support TIA 825 Baudot where they interface to the PSTN;
  2. Products that connect directly to the Internet via SIP shall support RFC 4103 where they interface to the Internet via SIP
  3. All other Products (including PBX, cellular, and peer to peer Internet phones) that do not connect to PSTN or use SIP over the Internet shall support the standard real-time text format for that system. These systems only need to support TIA 825 Baudot at the juncture to the PSTN (if any) and only need to support RFC 4103 at the point where they connect to public SIP systems (if any)

E. R-Text within Voice Systems

Systems that support real-time voice communication shall support at least one standard (for the system) means for real time text communication that is supported by all terminal, router, gateway and other products on that system, and that meets the following requirements:

  1. Provides transmission of character with less than 1 second delay from entry;
  2. Provides transmission with less than 1% character error under normal but heavy network traffic;
  3. Support intermixing of speech and text in both directions (simultaneously if and only if IP based).
  4. IP systems cannot rely upon audio channels for transmission of real-time text.

F. IVR etc.

Voice mail, messaging, auto-attendant, and interactive voice response telecommunications systems shall:

  1. Voice mail, messaging, auto-attendant, and interactive voice response telecommunications systems shall make information available and be capable of recording Baudot TTY signals and shall:
    1. Use the ITU-T G.711 standard for encoding and storing audio information. If an audio encoder other than G711 is employed, the vendor must provide evidence that the intelligibility is equal to or better than that provided by G.711;
    2. Provide full player controls that allow users to pause, rewind, slow down and repeat all messages and prompts, and adjust volume;
    3. Provide prompts (either as provided by the vendor or by the user) without any background sounds that would reduce intelligibility.
  2. In using such systems agencies shall:
    1. Preferably present the system user with 4, but no more than 6, menu choices at one time unless the user requests to hear more options;
    2. Provide easy to understand and act upon menu items and other navigational messages;

G. Caller and Status Information

Where provided, visual interfaces for telecommunications status information such as caller identification and similar telecommunications functions as part of interactive voice response systems or equivalents shall also be available for users of TTYs or other text conversation systems, and for users who cannot see displays and shall meet all accessibility provisions for software and content.

H. Video Support

Telecommunications products or systems which have the capacity to transmit video, text and voice communications shall support internet protocol text and voice communications in X format and have sufficient transmission bandwidth capacity to support video communication such as video relay and point to point video communications.

6. Electronic Content Provisions

{for products, training, or E&IT services}

[6.1] If Web Content and Applications

{Web content and application requirements}

(NOTE: On June 7, 2007, the heading was updated from Web and Application Content as was agreed to in the May plenary meeting)

A. Non-text Content:

Non-text Content: Except for the situations listed below, a text alternative that presents equivalent information shall be provided for all non-text content.

  1. Controls-Input: If non-text content is a control or accepts user input, then it has a name that describes its purpose. (See also <reference the new provision on interface components>)
  2. Media-Test-Sensory: If non-text content is multimedia , live audio-only or live video-only content, a test or exercise that must be presented in non-text format, or primarily intended to create a specific sensory experience , then text alternatives at least identify the non-text content with a descriptive text label. (For multimedia, see also 1194.22(b) - 7.c.A)
  3. CAPTCHA*: If the purpose of non-text content is to confirm that content is being accessed by a person rather than a computer, then a descriptive text label describing its purpose is provided and different forms are provided to accommodate different disabilities.
  4. Decoration-Formatting-Invisible: If non-text content is pure decoration, or used only for visual formatting, or if it is not presented to users, then it is implemented such that it can be ignored by assistive technology.

B. Forms

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.

C. Scripts

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.


D. Repeated Blocks

A mechanism shall be available to bypass blocks of content that are repeated on multiple Web pages.

E. Keyboard

Keyboard operability provision TBD from Web and Software Subcommittee.

F. Link Purpose

The purpose of each link shall be capable of being determined from the link text and its programmatically determinable link context.

G. Information and Relationships

Information and relationships conveyed through presentation shall be programmatically determinable, and notification of changes to these is available to user agents, including assistive technologies. For example:

  1. row and column headers are identified for data tables
  2. markup is used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.
  3. markup is used to identify section headings

H. Focus Cursor (Web)

A focus cursor shall be provided that visually indicates which user interface element currently has the keyboard input focus, as well as the focus location within that element when one exists. The focus cursor shall be programmatically determinable so that assistive technology can track focus and focus changes.

I. User Interface Components

For all user interface components, the name and role shall be programmatically determinable, states, properties, and values that can be set by the user shall be programmatically determinable and can be programmatically set, and notification of changes to these items is available to user agents, including assistive technologies. For example:

  1. Frames shall be titled with text that facilitates frame identification and navigation.

J. Consistent Identification

Components that have the same functionality within a set of Web units shall be identified consistently.

K. Timing (Web)

For each time limit that is set by the content, at least one of the following is true:

  1. Deactivate: the user shall be allowed to deactivate the time limit; or
  2. Adjust: the user shall be allowed to adjust the time limit over a wide range that is at least ten times the length of the default setting; or
  3. Extend: the user shall be warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "hit any key"), and the user is allowed to extend the time limit at least ten times; or
  4. Real-time Exception: the time limit is an important part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or
  5. Essential Exception: the time limit is part of an activity where timing is essential (for example, competitive gaming or time-based testing) and time limits can not be extended further without invalidating the activity.

L. Pausing

Content shall be capable of being paused by the user unless the timing or movement is part of an activity where timing or movement is essential.

M. Contrast (Web)

Text, images of text, or diagrams, and their respective backgrounds, shall have a luminosity contrast ratio of at least n:1.

[6.2] If a Content Format

{Requirements for content formats}

A. Non-text Objects

When a content format supports non-text objects, an encoding mechanism shall be provided to associate non-text objects with textual descriptions displayable by a user-agent.

B. Multimedia (Format)

When a content format supports multimedia, an encoding mechanism shall be provided to include synchronized text of verbal content, and audio descriptions of critical nonverbal activity displayable by a user-agent.

C. Reading Order

When a content format supports 2 dimensional display of information, an encoding mechanism shall be provided to identify the logical linear reading order of the content displayable by a user-agent.


D. Table Headers

When a content format supports row and column headers in data tables, an encoding mechanism shall be provided to identify row and column headers for data tables displayable by a user-agent.

E. Complex Table Headers

When a content format supports data tables that have two or more logical levels of row or column headers, an encoding mechanism shall be provided to associate row and column headers with data cells, displayable by a user-agent.

F. Interactive Elements

When a content format supports interactive elements, an encoding mechanism shall be provided to identify name, operation, and state, of any interactive elements displayable by a user-agent.

G. Links

When a content format supports links, an encoding mechanism shall be provided to identify link text displayable by a user-agent.

H. Embedded Comments

When a content format supports embedded comments, an encoding mechanism shall be provided to identify embedded comments and associate those comment locations within the document.

I. Images of Text

When a content format supports scanned images of text, an encoding mechanism shall be provided to identify text of scanned images of text, displayable by a user-agent. Note, this means allowing for inclusion of the text of a scanned image of text.

J. Dynamic Information

When a content format supports dynamic presentations, graphs, or other extracted information, an encoding mechanism shall be provided to include data used for any dynamic presentations, graphs, or other extracted information displayable by a user-agent.

[6.3] If Audio and/or Video content

{Requirements for AV content: captioning, audio description, and synchronized alternatives for audio and video with interaction.}

A. Synchronized Alternatives

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

B. Captions and Transcripts

All materials containing video and/or audio, regardless of format, that contain speech or other audio information necessary for the comprehension of the content, must comply with the following:

  1. Materials containing prerecorded audio and no additional time-based content must provide either a transcript or synchronized captions.
  2. Materials containing prerecorded video with concurrent audio must provide synchronized captions and may offer a transcript in addition to, but not in place of, the captions.
  3. Materials containing real-time audio, with or without video, must provide synchronized real-time captions.

C. Audio Description and Full Text Equivalents

All materials containing video and/or audio, regardless of format, that contain visual information necessary for the comprehension of the content, must comply with the following:

  1. materials containing prerecorded video and no audio or other additional time-based content must provide either a separate text description of the video or provide an additional audio track to convey the informational content of the video.
  2. materials containing prerecorded video with concurrent audio must provide synchronized audio descriptions, or a separate text description of the video, to convey the informational content of the video.
  3. materials containing live video must provide synchronized audio descriptions in real time to convey the informational content of the video.

D. Open or Closed Captions/Descriptions:

At the time of playback, captions and/or video descriptions must be either (a) capable of being turned on and off ("closed"), or (b) visible or audible to all users ("open").

E. Interactive Elements

All materials containing interactive elements that are part of the content must comply with 1194.21 [a-z] as well as 1194.24 a-e.

[6.4] Additional requirements for Web Content Authoring Tools

{Additional Requirements for software tools specifically designed to author web content }

7. Information, Documentation and Support

[7.1] Product Documentation and help

{Requirements for access to and content of documentation and help}

A. Accessible Documentation

To provide documentation to users on the installation, configuration and use of the product, Federal agencies shall require that all documentation supporting the product, including but not limited to reports, system documentation and user training or technical support materials conform the relevant accessibility provisions in 1194 Subparts B and C.

B. Access Features

Product documentation shall provide users with a description of the accessibility and compatibility features of the product, including how to install and activate them. This information shall be provided in alternate formats or alternate methods upon request.

C. Keyboard Shortcuts

Information about keyboard shortcuts shall be made available in documentation.

  1. All shortcuts for keyboard operation shall be enumerated in one place for easy reference.
  2. When the documentation lists specific mouse based actions, the keyboard commands shall also be listed.

D. Advisory Notes

Best practices for providing documentation to people with disabilities include:

  1. Context-sensitive help, which offers documentation or support for the features and functions of the current page, screen or window should be offered, using a consistent set of accessible commands to access it.
  2. Documentation and training materials should include text descriptions of the interface. These descriptions should stand on their own and be understandable without relying on graphic images in the materials.
  3. Descriptions of a user interface should refer to elements by name or function, in addition to their location in the visual interface.

[7.2] Support and E&IT related services

{Requirements for access and availability of support and training}

A. Support Services

Support services for products shall accommodate the communication needs of end-users with disabilities.

B. Advisory Notes

Best practices for providing support to people with disabilities include:

  1. Remote assistance programs allow someone to access a computer system remotely to provide support or instruction. This ability to demonstrate features of the computer software or hardware is helpful to people with cognitive disabilities. Applications should either make such a feature available or not disrupt tools that provide it.

8. Product Development Process (255 only)

{Process guidance, including PWD, access in design, development & fabrication, no decrease in access}

Deleted Provisions:

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.

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

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

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

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

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

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

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

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

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.

WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University