Web and Software: Harmonization impact 2

NOTE 1 Common attributes for a visual interface could include, but are not limited to, font type, font size, and font colour. For an auditory interface they could include, but are not limited to, aural cue type, rate, volume, pitch, position in 3D audio space, etc. For a tactile interface they could include, but are not limited to, haptic object size, texture, xy- or xyz-position, pressure sensitivity, solidity, etc.

NOTE 2 Platform software often supports these options for standard user interface elements it provides. To enhance user experience, applications can use the settings defined at the platform level.

EXAMPLE Software retains user preference for window size and location between sessions.

• Controls-Input: If a non-text object is a control or accepts user input, then it must have a name that describes its purpose. (See also User Interface Components provisions)
• Media: If a non-text object is multimedia, live audio-only or live video-only content, then text alternatives at least identify the non-text object with a descriptive text label. (For multimedia, see also Audio and/or Video provisions)
• Test: If a non-text object is a test or exercise that must be presented in non-text format, then text alternatives at least identify the non-text object with a descriptive text label. (For multimedia, see also Audio and/or Video provisions)
• Sensory: If a non-text object is primarily intended to create a specific sensory experience, then text alternatives at least identify the non-text object with a descriptive text label. (For multimedia, see also Audio and/or Video provisions)
• CAPTCHA: If the purpose of a non-text object is to confirm that content is being accessed by a person rather than a computer then text alternatives that identify and describe the purpose of the non-text object must be provided and alternative forms in different modalities must be provided to accommodate different disabilities.
• Decoration, Formatting, Invisible Objects: If a non-text object 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.

• Note: Object information provided per the "Information and Relationships", "User Interface Components", or "AT interoperability" provision that describes the necessary visual cues or relationships is sufficient.

NOTE If software generates audio output, it is preferable for it to provide its own control that adjusts the volume of its own audio output relative to other software and any system-wide volume setting. Software shall enable users to control the volume of audio output. NOTE If software generates audio output, it is preferable for it to provide its own control that adjusts the volume of its own audio output relative to other software and any system-wide volume setting.

If the background and other sound layers are separate audio tracks/channels, software should provide a mechanism to enable users to control the volume of and/or turn on/off each audio track.

NOTE For users who are visually impaired or blind, the order and grouping in which keyboard navigation occurs may be the only order in which they can use controls

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
4. markup is used to identify form element labels

• the name and role must be programmatically determined
• states, properties, and values that can be set by the user must be programmatically determined and can be programmatically set, and
• notification of changes to these items is available to user agents, including assistive technologies.

For example:

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

• 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 labeled 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

• User interface element information includes, but is not limited to: general states (such as existence, selection, focus, and position), attributes (such as size, color, role, and name), values (such as the text in a static or editable text field), states specific to particular classes of user interface elements (such as on/off, depressed/released), and relationships between user interface elements (such as when one user interface element contains, names, describes, or affects another).
• See 8.2, "Names and Labels for User Interface Elements" for more information on the name property and the relationship between an element and its visual label.

• provide assistive technology with object information including but not limited to:
  • role, state(s), boundary, name, and description
  • 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 labeled by another
  • parent or containing element, and any children objects
  • text contents, text attributes, and the boundary of text rendered to the screen

• allow assistive technology to track and modify focus, text insertion point, and selection attributes of user interface objects;

• provide assistive technology with object information including but not limited to:
  • role, state(s), boundary, name, and description

• provide assistive technology with object information including but not limited to:
  • any table row & column, and row & column headers (if the object is in a table)

• In some cases the name will be displayed visibly, but in other cases it will only be provided programmatically for use by assistive technology as described in section 8.6.

8.2.4 : Each name of a user interface element and its association shall be made available by the software system to assistive technology in a documented and stable fashion.

• provide assistive technology with object information including but not limited to:
  • role, state(s), boundary, name, and description

• the user is allowed to deactivate the time-out, or;
• the user is allowed to adjust the time-out over a wide range which is at least ten times the length of the default setting, or;
• the user is warned before time expires, allowed to extend the time-out with a simple action (for example, "hit any key") and given at least 20 seconds to respond.

• Turn off: the user is allowed to turn off the time limit before encountering it; or
• Adjust: the user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or
• Extend: the user is 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
• Real-time Exception: the time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or
• Essential Exception: the time limit is part of an activity where timing is essential and time limits can not be extended further without invalidating the activity.

• Note: If the object is a text entry field, a visual indication of the text insertion point is sufficient as a focus cursor.

• Note: A focus cursor that is visually locatable by people with unimpaired vision at 2.5 meters when software is displayed on a 38 cm (15 inch) diagonal screen at 1024 x 768 pixels resolution, without moving the cursor is sufficient.

1. expose the underlying platform's color, contrast, and other individual display settings to applications running within its platform, so that these applications can meet the User Preferences provision.
2. define, expose, and translate accessibility service information between applications running within its platform and the underlying platform - so that those applications can meet the AT Interoperability provision.
3. provide mechanisms for:
   • moving the keyboard focus into and out of an application, and
   • addressing central conflicts between keyboard mnemonics in the application and the host platform.

• For each accessible content format supported, authoring tools must allow the author to produce content, including content derived from programmatic sources, that meets applicable Section 508 provisions.
• Authoring tools must preserve accessibility information necessary to meet applicable Section 508 provisions, unless the user explicitly indicates otherwise.
• For authoring tools with a user interface, authoring tools must provide a mode which prompts authors to create accessible content.
• For authoring tools with a user interface, authoring tools must either provide a mode which assists authors in checking for accessibility problems, or compatability with evaluation tools that provide that function.
• Authoring tools which provide pre-authored content, or templates to facilitate production of content, must provide at least one version that meets applicable Section 508 provisions.