Web and Software: Reorganized Web and Software provisions
Contents |
Software and Electronic Content Provisions
- GV Comment: This name looks like software applications and content. Needs to sound like it covers UI behavior of hardware as well.
- WhitneyQ comment: We need to normalize the wording of these provisions to use the 508 style (using "must" not "shall", and not the checklist style).
These provisions apply to all software user interfaces and electronic content.
Software user interfaces and content that includes interactive elements, other than links, that require programming logic, must also apply the Interactive Electronic Content or Software provisions.
Color
- Current 508 Software: Color coding must not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
- Current 508 Web: Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.
- Current WCAG 2.0: Any information that is conveyed by color differences is also simultaneously visually evident without the color differences.
- GV Comment: I thought color was the only one still up in General Performance Requirements. I'm ok with it here though - maybe we should duplicate.
- GV Comment: WCAG is currently tuning their language.
Contrast
Text (and images of text) have a contrast ratio of at least 5:1, except if the text is pure decoration. Larger-scale text or images of text can have a contrast ratio of 3:1.
- AS Comment: This seems to be in conflict with the User Preferences requirement. Is this one that only applies to content and not to software user interfaces?
- GV Suggestion: Text (and images of text) have a DEFAULT contrast ratio of at least 5:1, except if the text is pure decoration. Larger-scale text or images of text can have a contrast ratio of 3:1. Then there would be no conflict with other provision which just says 'honor the user settings'.
Flash
Content and applications do not contain anything that flashes more than 3 times in any one second period or the flashing is below the general flash and red flash thresholds.
Non-text content
Non-text Content: All non-text content has a text alternative that presents equivalent information, except for the situations listed below.
- Controls-Input: If non-text content is a control or accepts user input, then it has a name that describes its purpose. (See also User Interface Components provisions)
- 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 Audio and/or Video provisions)
- CAPTCHA: If the purpose of non-text content 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 content are provided and alternative forms in different modalities are provided to accommodate different disabilities.
- 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.
Link purpose
The purpose of each link can be determined from the link text or the link text together with it's programmatically determined link context.
- AS Comment: Need to think about how this one applies to non-HTML content.
- GV Comment: People get confused. i think we should add "by users" after "determined".
Information and relationships
Information and relationships conveyed through presentation can be programmatically determined or are available in text, and notification of changes to these is available to user agents, including assistive technologies. For example:
- row and column headers are identified for data tables
- 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.
- markup is used to identify section headings
- AS Comment: Frame titles would need to be included as an example here I think.
Reading order
When the sequence in which content is presented affects its meaning, a correct reading sequence is programmatically determinable.
Consistent use of images/components
Components that have the same functionality must be identified consistently. When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned to those images must be consistent throughout an application's performance.
- GV Comment: should add a note somewhere as to why we are focusing on bitmaps
Pausing
Moving, blinking, scrolling, or auto-updating information can be paused by the user unless it is part of an activity where timing or movement is essential. Moving content that is pure decoration can be stopped by the user.
- AS Comment: I wasn't sure if this is necessary for content that does not require programming logic. That is, can an author create moving, blinking, scrolling, or auto-updating information without using programming logic that the user would not be able to stop using the rendering software or user agent? If it stays here, need to harmonize with the Animation provision below and delete the Animation provision.
- GV Comment: Author should not use 'non-programmatic' content that will move/blink/scroll if the user agents dont provide a way to stop.
If Web Pages, bypass blocks
A mechanism must be available to bypass blocks of content that are repeated on multiple Web pages.
- AS Note: This one seemed particular only to Web pages and not other kinds of content.
- GV Comment: Are you considering an HTML page that is not on the Web to be a Web page? If you have a manual in HTML this should still apply - no?
Software and Interactive Electronic Content
- GV Comment: OOPs - this one has components for behavior of hardware caused by software or firmware too. I don't see any way for a person to figure out which provisions apply to products that do not have an OS. "Software" is not a good term for behaviors that are parts of products like simple phones, copiers, fax machines, etc. People dont think of those things as running software or having to meet software provisions. hmmmmm. Sorry - not quick suggestion.
Software includes but is not limited to:
- traditional applications coded in a programming language such as C++ or Java
- application specific forms such as dialog boxes or database application forms
Interactive electronic content is any content that is implemented with programming logic.
Examples of interactive electronic content include but are not limited to:
- DHTML, Script, and AJAX implementations where markup languages are used but elements are repurposed to produce interactive functions.
- Forms in HTML, PDF, or Word
- HTML+CSS? (is the application of CSS considered programming logic? Some have suggested that if you override the user agent styles, you are responsible for things like supporting the user's system settings, focus cursor appearance, etc.)
- Flash presentations that include GUI-like controls
- Multimedia that includes GUI-like controls such as the interactive elements used to select different content on a DVD.
Note that software must also meet the applicable General Requirements.
- AS comment: This is where the current organization gives us a problem. We're trying to make the static content provisions self-contained so that authors who are not programmers don't have to look at the general provisions so there is duplication. But if the interactive content and software developers have to look at general in addition to content and software, then they will see some requirements twice.
Color adjustment
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 7:1 must be provided.
User Preferences
Applications must 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.
Timing
For each time limit that is set by the software, at least one of the following is true:
- 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.
Keyboard Operation
All functionality of the product operable through the user interface is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.
- Note: This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path dependent input but the underlying function (text input) does not.
- Note: This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.
- GV Comment: add to note 2?: "...such as mouse or gesture."
Disruption of access features
Applications must not, except by specific user request, disrupt the features of the platform that have an accessibility usage in the platform developer documentation.
Focus Cursor
Software must 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 must be provided, and is sufficient.
Animation
When an informational animation is displayed that will last for more than three seconds, software must 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 must give the user a means to stop the animation.
AS Note: This provision is currently slightly different than the "Pausing" provision above due to harmonization with ISO/HFES. The ISO/HFES wording is now the same as the "Pausing provision" above so we can delete this requirement.
If running on a platform that supports AT Interoperability
If interactive electronic content
For all user interface components, including form elements and those generated by scripts, the name and role must be programmatically determinable, states, properties, and values that can be set by the user must be programmatically determinable and can be programmatically set, and notification of changes to these items is available to user agents, including assistive technologies.
If software
Software that provides user interface objects must 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 must:
- 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
Note: This provision applies to forms in the software.
Both platform and app
Software that is both a 'platform', and an 'application' running on another platform must:
- 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.
- 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.
- 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.
Software that is an authoring tool
- TBD authoring tool provisons
- Content format provisions
