| Home |
 |
Additional detail on what the law requires, techniques specific to the chapter's technologies, and further discussion addressing each standard can be found in the Section 508 Technical Reference Guide.
Software is a program that runs on electronic equipment. For a program to be considered accessible, assistive technology should be able to work with it to allow its features and functions to be understood.
Software developers are responsible for helping the screen reader understand the screen. Blind users, for instance, do not use mice. A program that required the use of a mouse would not comply with Section 508. Blind users need an alternative method to understand the functions of a toolbar, radio buttons, push buttons, drop-down menus, or pop-up messages explaining the function of an icon.
The technical steward for software and operating systems is the Manager, Business Solutions Services, IT.
Accessibility is accomplished by designing software that accommodates the widest range of users, including those with disabilities. Listed below are some general requirements that will help the Postal Service ensure continued accessibility of software applications and operating systems:
• The Postal Service will develop and procure software applications that take advantage of hardware and operating system built-in accessibility features when those features are available to both end users and software developers.
• The Postal Service will maintain standards for the following categories of assistive technologies that people with disabilities use to access software applications and operating systems:
• Screen magnifiers: Help visually impaired people by allowing them to enlarge any part of the screen (i.e., as with a magnifying glass).
• Screen readers: Help people who are blind by making on-screen information available as synthesized speech or for display as refreshable Braille.
• Voice input aids: Help mobility- or dexterity-impaired people by allowing them to control the computer with their voice instead of with a mouse or keyboard.
• On-screen keyboards: Help people who are unable to use a standard keyboard by providing an on-screen keyboard that can be used with a pointing device.
• Keyboard filters: Help people who have trouble typing by compensating for erratic motion, tremors, or slow response time.
• Alternative input devices: Help people who would prefer to control their computer with a device other than a keyboard or mouse.
• The Postal Service will develop software applications that maximize the capabilities of the accessibility features installed and activated by a user (e.g., native hardware and operating system features, as well as installed accessibility aids). Software developers should do the following:
• Support the native operating system and activate the accessibility features for the major operating systems that are integrated with input and output devices (e.g., keyboard, sound, display, or mouse).
• Use standard controls for the particular operating systems where possible (e.g., menus, buttons, lists, or windows). These standard controls often already support the native operating system accessibility features. Using them will often eliminate the need for software to provide explicit accessibility support, unless the behavior of the standard controls has been enhanced.
• Be careful when using custom controls or enhancing standard controls, because accessibility aids may have difficulty identifying them (i.e., accessibility aids require specific information to work successfully with screen elements). When custom or enhanced standard controls are used, developers must use appropriate accessibility interfaces or application programming interfaces (APIs) (e.g., Sun's Java Access Bridge, Microsoft Active Accessibility, window messaging, off-screen model, etc.) to provide object information to accessibility aids. The information that must be provided by objects includes name, location, type, associated values, parent control, logical order for navigation, and event notifications, such as focus gain or loss.
• Provide flexibility in using a variety of input methods (e.g., keyboard or mouse) and output methods (e.g., color, sound, images, or text).
• Detect if accessibility aids are in use and configure the software applications automatically. For example, determine when a screen reader is in use so that the software can be reconfigured.
Web-based information and applications are based on access guidelines developed by the Web Accessibility Initiative of the World Wide Web Consortium (http://www.w3c.org). The standards aim to ensure that such information is also available in an accessible format. This means use of text labels or descriptors for graphics and certain format elements. HTML code already provides an alternative text attribute (or "alt" tag) for graphics which can serve as a verbal descriptor for graphics. Web-based information and application accessibility standards also address the usability of multimedia presentations, image maps, style sheets, scripting languages, applets and plug-ins, and electronic forms.
The standards apply to federal Web sites but not to private sector Web sites - unless a site is provided under contract to a federal agency; in that case, only that Web site (or portion) covered by the contract would have to comply. Accessible sites offer significant advantages that go beyond access. For example, those with "text-only" options provide a faster downloading alternative and can facilitate transmission of Web-based data to cell phones and personal digital assistants.
The Technical Steward for Web-based information and applications is the Manager, Corporate Business Systems Solutions, IT.
Accessibility is accomplished by designing software that accommodates the widest range of users, including those with disabilities. Listed below are some general requirements that will help the Postal Service ensure that Web-based applications and information remain accessible:
• The Postal Service will take advantage of operating system and Web client built-in accessibility features when those features are available to both end users and software developers.
• The Postal Service will maintain standards for the following accessibility aids or assistive technologies that are used by people with disabilities to access Web-based applications and information:
• Screen magnifiers: Help visually impaired people by allowing them to enlarge any part of the screen (i.e., as with a magnifying glass).
• Screen readers: Help blind people by making on-screen information available as synthesized speech or for display as refreshable Braille.
• Voice input aids: Help mobility- or dexterity-impaired people by allowing them to control the computer with their voice instead of with a mouse or keyboard.
• On-screen keyboards: Help people who are unable to use a standard keyboard by providing an on-screen keyboard that can be used with a pointing device.
• Keyboard filters: Help people who have trouble typing by compensating for erratic motion, tremors, or slow response time.
• Alternative input devices: Help people who would prefer to control their computer with a device other than a keyboard or mouse.
• The Postal Service will develop Web-based applications that are based on interoperable specifications and do not interfere with accessibility features installed and activated by a user (e.g., operating system features and Web client capabilities, as well as installed accessibility aids). Web-based developers should do the following:
• Support native operating system and activated accessibility features for major operating systems that are integrated with input and output devices (e.g., keyboard, sound, display, or mouse). These features are supported by most Web clients and Web browsers. Developers should be aware of how these features will be used in combination with Web-based technologies. Standards for each operating system related to each specific requirement are shown in the "References" area under each specific requirement in Chapter 5 of Handbook AS-508-A, Section 508 Technical Reference Guide, Software Applications and Operating Systems.
• Use standard markup tags in creating Web content where possible (i.e., use the W3C recommendations). Standardized markup is often already supported by Web clients and operating system accessibility features. Using these tags will often eliminate the need for software to provide explicit accessibility support.
• Use caution when using plug-ins or enhancing Web content, because accessibility aids may have difficulty identifying them (i.e., accessibility aids require specific information to work successfully with screen elements). When custom or enhanced Web content is used, developers must use appropriate methods to allow Web content and information (e.g., providing alternate or equivalent content) to function with accessibility aids. The nonproprietary information that is created using standard HTML, XHTML, XML, or SGML allows for access using multiple clients (tools), reduces development costs, and permits the interoperability of technologies unknown by the author or creator of the information. Provide flexibility by allowing for a variety of input (e.g., keyboard, mouse) and output (e.g., color, sound, images, text) methods.
• Allow accessibility aids and nonstandard clients to use and configure the Web applications and information automatically. For example, detecting a specific browser and providing additional modification of Web content should not prevent unknown clients and accessibility aids from accessing the content.
Handbook AS-885, usps.com Development Process and Standards, provides processes and standards for building and maintaining an information presence or application on usps.com and defines the design and development standards and best practices for use on that site. It may be accessed online at http://blue.usps.gov/cpim/ftp/hand/as885.pdf.
Telecommunication products are any products whose primary function is to provide telephone functions (i.e., two-way voice communications), regardless of type.
The convergence of telephony and information technology is blurring the line between different product types as a variety of new and innovative products are created (e.g., softphones, voice over IP, etc.). For products with multiple functions, these requirements apply only to the telephone functions of those products.
The Technical Steward for telecommunications products is the Manager, Telecommunications Services, IT.
Accessibility is accomplished by purchasing or developing telecommunications products that accommodate the widest range of users, including those with disabilities. Listed below are some general requirements that will help the Postal Service ensure that its telecommunications products continue to be accessible:
• The Postal Service will develop and procure telecommunications products that take advantage of built-in accessibility features when those features are available to both end users and product developers.
• The Postal Service will procure or develop telecommunications products that maximize the capabilities of the accessibility features installed and activated by a user (e.g., native hardware, as well as installed assistive technology). Postal Service telecommunications products procurement personnel and developers should do the following:
• Buy or build products that support industry and regulatory telecommunications standards. Accessibility features are often integrated with these standards to ensure accessibility in telecommunications usage (including input, compression, transmission, storage, and output).
• Use standard hardware and software controls instead of custom controls. Standard controls often already support product accessibility features. Using them may eliminate the need for additional configuration or programming to provide explicit accessibility support, unless the behavior of the standard control has been enhanced.
• Buy or build products that support a variety of input and output methods.
• Buy or build products that can detect the assistive technology in use and configure the telecommunication products automatically. For example, IVR (Interactive Voice Recognition) systems might detect the presence of TTY signals and automatically route calls to the appropriate system or subsystem.
The purpose of this standard is:
• To ensure that video receivers and displays are capable of displaying closed captioning in a variety of contexts.
• To ensure that all associated data, information, training material, and documents related to those mission-critical video and multimedia productions must be open or closed-captioned.
• Require audio descriptions for all training and informational video and multimedia productions which are related to the mission of the organization (i.e., considered mission-critical) and that contain visual information necessary for the comprehension of the content.
In considering the many different technologies involved, note that video in combination with other media, regardless of format, is considered multimedia. Whether broadcast to a television or streamed over the Internet, it must comply with the video and multimedia standard.
The Technical Steward for video and multimedia products is the Enabler Business Systems Portfolio, IT.
Accessibility is accomplished by designing video and multimedia that accommodates the widest range of users, including those with disabilities. Listed below are some general requirements that will help the Postal Service ensure that video and multimedia products remain accessible:
• Implementation of specific requirements may require research on the current accessibility features of the target platform, operating system, or transmission/broadcast method.
• All video and multimedia productions should be designed with the evolving open standards for accessibility that support cross-platform use (i.e., use of SMIL standards that are supported by most digital media players, etc.).
In many cases, raw videotaped footage does not have to be captioned or audio described. For example, raw videotaped footage used to document a safety violation could be considered a video "in support of the Postal Service's mission." If the footage is used in a production, however, such as a Web-based presentation or training video, it does have to be captioned or audio described.
The term "self-contained" is used to define a class of information technology. Unlike personal computers, which can have assistive technology installed, closed products can be accessible only if they have been designed to be accessible by people with limited vision, mobility, or hearing.
This standard covers any products or systems that do not permit end-user-installed assistive technologies. Such products often involve input and output interactions that present accessibility challenges (e.g., touch screens, physical layout/positioning). Unlike personal, customizable devices, many products in this class of technology (e.g., kiosks and shared printers) are used by the general public.
Since they cannot be customized, such closed products must be designed with the needed accessibility features for all users.
The Technical Steward for self-contained, closed products is the Manager, Technology Support, IT.
Accessibility is accomplished by purchasing or developing self-contained, closed products that accommodate the widest range of users, including those with disabilities. Listed below are some general requirements that will help the Postal Service ensure continued accessibility of self-contained, closed products:
• The Postal Service will develop and procure self-contained, closed products that take advantage of built-in accessibility features when those features are available to both end users and product developers.
• The Postal Service will procure or develop self-contained, closed products that recognize and maximize the capabilities of the accessibility features installed and activated by a user via an attached personal computer (e.g., operating system features and assistive technologies that enable control of dialog boxes to activate device controls). Postal Service self-contained, closed products procurement personnel and developers should do the following:
• Buy or build products that support self-contained, closed products standards. Accessibility features are often integrated with these standards in order to ensure accessibility in self-contained, closed products. Standard kiosk shapes have been developed to meet appropriate reach specifications.
• Where possible, use standard hardware and software controls instead of custom controls. These standard controls often already support product accessibility features. Using them will often eliminate the need for additional configuration or programming to provide explicit accessibility support, unless the behavior of the standard controls has been enhanced. Full-screen keyboards are well understood. Many self-contained, closed products support the attachment of such input devices. Telephone-style key clusters are another de facto standard.
• Provide flexibility in using a variety of input and output methods. Many self-contained, closed products support only one mode of operation. When such devices can be added to a network, people with disabilities may be able to access these products from a personal computer that has assistive technology.
• Consult with accessibility experts and representatives of the disability community when developing unique devices. Assistive technology products for personal computers represent standard solutions to open products. Accessibility experts and representatives of the disability community are a resource that can vastly enhance the designs of engineers and solution architects.
This standard covers any hardware computer product, regardless of type (e.g., desktop, mobile or portable), onto which operating systems and software applications can be installed.
For products with multiple functions, these requirements apply only to the hardware components of those products.
The Technical Steward for desktop and portable computers is the Manager, Distributed Computing Environment, IT.
Desktop and portable computer products that have mechanically operated controls and keys shall comply with the following requirements:
• Controls and keys shall be tactilely discernible without activating the controls or keys.
• Controls and keys shall be operable with one hand and shall not require tight grasping, pinching, or twisting of the wrist. The force required to activate controls and keys shall be 5 lbs. (22.2 N) maximum.
• 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.
• The status of all locking or toggle controls or keys shall be visually discernible, and discernible either through touch or sound.
• For touch screens, provide an appropriate alternate access method that supports the first four requirements listed above.
Biometric User Identification and Controls.
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.
Industry-Standard Expansion Slots, Ports, and Connectors.
Where provided, at least one of each type of expansion slots, ports and connectors shall comply with publicly available industry standards.
This standard covers all information about EIT products and their support services, regardless of technology type. Persons with disabilities need this information to support their effective use of the EIT products covered by Section 508. It includes any documentation provided by the Postal Service or its EIT suppliers to its technology users must be available upon request in appropriate alternate formats. The Postal Service functional units are required to supply end users with information about accessibility or compatibility features that are built into a product, upon request. This information is vital in knowing how to use certain products such as self-contained, closed products. It is also essential for the installation of assistive technology in IT devices that are open to software which provides functions such as speech output, speech recognition, screen enlargement, or keyboard alternatives.
Help desks and other technology support services serving the Postal Service's employees and customers must be able to accommodate the communications needs of persons with disabilities. For example, a Postal Service help desk may need to communicate through a TTY. The help desk or support service must also be familiar with such features as keyboard-only access and other options important to people with disabilities. Electronic methods of interaction - e.g., Web forms, IVR systems, and online help systems - must also work properly for the employees and customers of the Postal Service.
Accessibility is accomplished not only by purchasing or developing compliant products that accommodate the widest range of users but also by ensuring that the information, documentation, and support services for the products are compliant as well. Listed below are some general requirements that will help the Postal Service ensure continued accessibility of both purchased and developed EIT information, documentation, and support:
• The Postal Service will procure products and systems with documentation and support that are accessible to the users of the system. These users may be Postal Service employees who access the system or customers who will interact with the system or its developed outputs.
• The Postal Service will develop products and systems that have accessible information, documentation, and support.