Proposed EITAAC Report 2/28/99 Kitchen Sink Draft #1 Everything I could find, patched into a single document. What's missing: 5.3.4 Web based information 5.3.8 PDAs/Thin clients Please note that I am not a Word wizard, so there are lots of funky formatting issues from cutting and pasting. I don't think it will take long to figure out that this document contains tons of redundant text. I think we should look to Jim Thatcher's basic plan in the software guidelines for a verbosity standard. Just as in the TAAC, there's a lot of useful stuff that won't begin to fit in a rule, but will be useful as appendices. Jim Fruchterman, Arkenstone 1. Executive Summary Draft after we're closer on the rest of the report. I believe Larry volunteered to do this, unless the Preamble is separate. 2. Legislative Authority/Background 2.1. Section 508 language Pull in from email or the web: Section 508 of the Rehabilitation Act 29 U.S.C. 798 SECTION 508 - ELECTRONIC AND INFORMATION TECHNOLOGY (a) Requirements for Federal Departments and Agencies: (1) Accessibility: (A) Development, procurement, maintenance, or use of electronic and information technology: When developing, procuring, maintaining, or using electronic and information technology, each Federal department or agency, including the United States Postal Service, shall ensure, unless an undue burden would be imposed on the department or agency, that the electronic and information technology allows, regardless of the type of medium of the technology- (i) individuals with disabilities who are Federal employees to have access to and use of information and data that is comparable to the access to and use of the information and data by Federal employees who are not individuals with disabilities; and (ii) individuals with disabilities who are members of the public seeking information or services from a Federal department or agency to have access to and use of information and data that is comparable to the access to and use of the information and data by such members of the public who are not individuals with disabilities. (B) Alternative means efforts: When development, procurement, maintenance, or use of electronic and information technology that meets the standards published by the Access Board under paragraph (2) would impose an undue burden, the Federal department or agency shall provide individuals with disabilities covered by paragraph (1) with the information and data involved by an alternative means of access that allows the individual to use the information and data. (2) Electronic and information technology standards: (A) In general: Not later than 18 months after the date of enactment of the Rehabilitation Act Amendments of 1998, the Architectural and Transportation Barriers Compliance Board (referred to in this section as the `Access Board'), after consultation with the Secretary of Education, the Administrator of General Services, the Secretary of Commerce, the Chairman of the Federal Communications Commission, the Secretary of Defense, and the head of any other Federal department or agency that the Access Board determines to be appropriate, including consultation on relevant research findings, and after consultation with the electronic and information technology industry and appropriate public or nonprofit agencies or organizations, including organizations representing individuals with disabilities, shall issue and publish standards setting forth- (i) for purposes of this section, a definition of electronic and information technology that is consistent with the definition of information technology specified in section 5002(3) of the Clinger-Cohen Act of 1996 (40 U.S.C. 1401(3)); and (ii) the technical and functional performance criteria necessary to implement the requirements set forth in paragraph (1). (B) Review and amendment: The Access Board shall periodically review and, as appropriate, amend the standards required under subparagraph (A) to reflect technological advances or changes in electronic and information technology. (3) Incorporation of standards: Not later than 6 months after the Access Board publishes the standards required under paragraph (2), the Federal Acquisition Regulatory Council shall revise the Federal Acquisition Regulation and each Federal department or agency shall revise the Federal procurement policies and directives under the control of the department or agency to incorporate those standards. Not later than 6 months after the Access Board revises any standards required under paragraph (2), the Council shall revise the Federal Acquisition Regulation and each appropriate Federal department or agency shall revise the procurement policies and directives, as necessary, to incorporate the revisions. (4) Acquisition planning: In the event that a Federal department or agency determines that compliance with the standards issued by the Access Board under paragraph (2) relating to procurement imposes an undue burden, the documentation by the department or agency supporting the procurement shall explain why compliance creates an undue burden. (5) Exemption for national security systems: This section shall not apply to national security systems, as that term is defined in section 5142 of the Clinger-Cohen Act of 1996 (40 U.S.C. 1452). (6) Construction: (A) Equipment: In a case in which the Federal Government provides access to the public to information or data through electronic and information technology, nothing in this section shall be construed to require a Federal department or agency- (i) to make equipment owned by the Federal Government available for access and use by individuals with disabilities covered by paragraph (1) at a location other than that where the electronic and information technology is provided to the public; or (ii) to purchase equipment for access and use by individuals with disabilities covered by paragraph (1) at a location other than that where the electronic and information technology is provided to the public. (B) Software and peripheral devices: Except as required to comply with standards issued by the Access Board under paragraph (2), nothing in paragraph (1) requires the installation of specific accessibility-related software or the attachment of a specific accessibility- related peripheral device at a workstation of a Federal employee who is not an individual with a disability. (b) Technical Assistance: The Administrator of General Services and the Access Board shall provide technical assistance to individuals and Federal departments and agencies concerning the requirements of this section. (c) Agency Evaluations: Not later than 6 months after the date of enactment of the Rehabilitation Act Amendments of 1998, the head of each Federal department or agency shall evaluate the extent to which the electronic and information technology of the department or agency is accessible to and usable by individuals with disabilities described in subsection (a)(1), compared to the access to and use of the technology by individuals described in such subsection who are not individuals with disabilities, and submit a report containing the evaluation to the Attorney General. (d) Reports: (1) Interim report: Not later than 18 months after the date of enactment of the Rehabilitation Act Amendments of 1998, the Attorney General shall prepare and submit to the President a report containing information on and recommendations regarding the extent to which the electronic and information technology of the Federal Government is accessible to and usable by individuals with disabilities described in subsection (a)(1). (2) Biennial reports: Not later than 3 years after the date of enactment of the Rehabilitation Act Amendments of 1998, and every 2 years thereafter, the Attorney General shall prepare and submit to the President and Congress a report containing information on and recommendations regarding the state of Federal department and agency compliance with the requirements of this section, including actions regarding individual complaints under subsection (f). (e) Cooperation: Each head of a Federal department or agency (including the Access Board, the Equal Employment Opportunity Commission, and the General Services Administration) shall provide to the Attorney General such information as the Attorney General determines is necessary to conduct the evaluations under subsection (c) and prepare the reports under subsection (d). (f) Enforcement: (1) General: (A) Complaints: Effective 2 years after the date of enactment of the Rehabilitation Act Amendments of 1998, any individual with a disability may file a complaint alleging that a Federal department or agency fails to comply with subsection (a)(1) in providing electronic and information technology. (B) Application: This subsection shall apply only to electronic and information technology that is procured by a Federal department or agency not less than 2 years after the date of enactment of the Rehabilitation Act Amendments of 1998. (2) Administrative complaints: Complaints filed under paragraph (1) shall be filed with the Federal department or agency alleged to be in noncompliance. The Federal department or agency receiving the complaint shall apply the complaint procedures established to implement section 504 for resolving allegations of discrimination in a federally conducted program or activity. (3) Civil actions: The remedies, procedures, and rights set forth in sections 505(a)(2) and 505(b) shall be the remedies, procedures, and rights available to any individual with a disability filing a complaint under paragraph (1). (g) Application to Other Federal Laws: This section shall not be construed to limit any right, remedy, or procedure otherwise available under any provision of Federal law (including sections 501 through 505) that provides greater or equal protection for the rights of individuals with disabilities than this section. 2.2. Related legislation & rules (ADA, 255, Part 1193, old 508, ADAAG) Need some discussion of the relationship of these different pieces of law and regulations. 3. Definitions 3.1. Electronic and Information Technology 3.1.1 Preamble: It is understood that Electronics and Information Technology addresses a broader spectrum than Information Technology alone, and includes the full breadth of the information environment of the future. It is understood that the intent of Section 508 was to ensure that government employees and the public have access to the government's information environment as it evolves. It is understood that the information environment that is evolving is something that we only imperfectly understand today but that it will include (but not be restricted to) the acquisition, creation, translation, duplication, manipulation, storage, management, movement, control, display, switching, interchange, transmission, or reception of information in a broad range of forms including voice, graphics, text, and data structures of all types both on a real time basis (e.g., conversation, communication, interaction) and delayed presentation basis (e.g. information serving, publishing etc.). It is understood that the definition of "Electronic and Information Technology" in Section 508 was meant to address the future and be broader than but consistent with (completely includes) the definition of "Information Technology" put forth by Clinger Cohen Act of 1996 including the exclusion for national security equipment. 3.1.2 Definition: The term "Electronic and Information Technology" shall mean electronic technology that is used in carrying out information activities, involving any form of information, where: a) "Electronic Technology" includes but is not limited to equipment, hardware, computers, software, firmware and similar procedures, systems, ancillary technologies, technologies which cause content to be active in any way, documentation, services (including support services) and related resources. It includes subsystems, interconnections, and interconnected systems. b) "Information Activities" include, but are not limited to, the creation, translation, duplication, serving, acquisition, manipulation, storage, management, movement, control, display, switching, interchange, transmission, or reception of data or information. Information activities include delayed presentation activities such as information servers and messaging systems as well as synchronous, real-time communication activities. c) "Any Form of Information" includes, but is not limited to, voice, graphics, text, dynamic content, and data structures of all types whether they are in electronic, visual, auditory, optical or any other form. [Pulled from January meeting minutes, as written up by Gregg] 3.2. Accessible Need a good definition of accessible. Check out the ADAAG & TAAC definitions. The Part 1193 and other definitions are often self- referencing (accessible for Part 1193 means equipment that complies with 1193). 3.2.1. TAAC definition (edited for EITAAC use): EIT is accessible if a person with a disability can use the EIT to perform the same tasks, access the same information, with the same ease, in the same time and at the same cost as a person using the EIT without a disability. The TAAC definition goes further and states that to be considered accessible the disabled person can use the EIT in its standard manufactured form without having to modify the product or purchase special technologies. 3.2.2. ADAAG definition: complies with the ADAAG requirements, and that the facility can be approached, entered and used by physically handicapped persons. 3.3. Disability. Use the ADA definition? Section 3(2)(A) of the ADA (42 USC 12101(2)(A)). 3.4. Undue burden. What authority should we reference? ADA implementation regulations from the DoJ. 36.104: Undue burden means significant difficulty or expense. In determining whether an action would result in an undue burden, factors to be considered include -- (1) The nature and cost of the action needed under this part; (2) The overall financial resources of the site or sites involved in the action; the number of persons employed at the site; the effect on expenses and resources; legitimate safety requirements that are necessary for safe operation, including crime prevention measures; or the impact otherwise of the action upon the operation of the site; (3) The geographic separateness, and the administrative or fiscal relationship of the site or sites in question to any parent corporation or entity... and more stuff based on the parent corporation (which isn't applicable to the federal government, I think). 3.5. Comparable Access/Ready Access (Pat Beattie's issue) The statute calls for access comparable to that experienced by nondisabled federal employees and members of the public. We need to explain what comparable access is. This could be based on the concept of ready access that Pat Beattie worked on a few years ago. Ready access is when a person with a disability has access to the same or equivalent information (as the nondisabled person), with a similar amount of effort and time. This needs some examples (may be relocated to an appendix): 3.5.1. Access is not comparable if the disabled person depends on human intervention to access the information while the nondisabled person does not require human intervention to access the same information 3.5.2. Access is not comparable if the disabled person is required to buy a product or pay money for access that the nondisabled person does not have to buy an equivalent product or pay money for access. For example, a sighted employee receives a manual for free but the blind employee has to pay for a Braille version. Exception: assistive technology may be required to be purchased by the government to make a piece of EIT accessible 3.5.3. Access is not comparable if there is a significant time delay for the person with a disability. 3.6. Any other terms important enough to define in this section of the main report as opposed to placing it in the glossary? 4. Issues that the committee wants to comment on. This is just a list of issues that have come up that would seem to need to addresses in the report somewhere. 4.1. Standards Refresh Does the Committee want to make some more detailed suggestions to the Access Board on the topic of refreshing the standards, beyond what's in the statute? 4.2. Procurement process There are several points here. The first is explanatory material about our interpretation of the burden in 508, which is on the government directly to require accessibility in procurement and in its provision of information to the public. The second is to make more specific recommendations on how these issues show up in federal procurement. For example, should these be part of the representations and certifications for vendors (I believe this was the section K discussed in the meeting)? Is accessibility supposed to be part of the evaluation criteria for major federal EIT bids (Section M)? My personal opinion is that a short rep and certification clause for Section K will be recommended for all procurements. We should recommend that major EIT procurements make it an explicit part of the evaluation process, as well as explicitly in the specifications (I forget which section this is). There was a discussion on the listserv about using access as either a binary certification (yes/no) or an evaluation criteria in awards. 4.3. Technical guidance Does the Committee want to make more specific recommendations in this area? 4.4. Proportionality This is the issue that Steve Berger has brought up. Does the Committee want to expand on this issue, by discussing how to achieve accessibility at the most reasonable cost? 4.5. Flexibility/least restrictive environment This issue is a bit of a counterweight to proportionality. Several people have brought up the need for more than one solution to access problems. For example, forcing a visually impaired person to use voice output screen access may make them five times less productive. Telling a non-Braille reader that Braille is the only accessibility accommodation for a person with a vision impairment is not a reasonable position. 4.6. Alternative Means 508(a)(1)(B) This is the backup strategy embodied in 508. How does this come into play in real situations for federal employees and the public? 4.7. International issues We've discussed harmonization with international standards bodies, ISO, the European Union. Are we going to get specific here? 4.8. Compliance with standards Do we have recommendations on compliance with standards? The EITAAC had a presentation on this from ANSI. Do we want to recommend a body be established to ensure or measure compliance? Do we have recommendations on what an agency should do if it decides that accessibility is an undue burden? DoJ can't help much on this, according to MaryLou. See Steve Berger's group on an accessibility compliance form, attached as Appendix Z. 4.9. Alternatives to standards mandated requirements What if an agency has something better than what a standard mandates? Can they try out the better thing? How can this sort of thing be drafted to prevent abuse? 4.10. Etc. What other items bear comment? 5. Proposed Standards 5.1. The seven or eight generic standards (mainly just the list of people with disabilities that need to be considered and made accessible for). 5.2. The function based performance guidelines [Jim F] Based on the Section 255 final rule from the Access Board: 1193.41 Input, control, and mechanical functions. Input, control, and mechanical functions shall be locatable, identifiable, and operable in accordance with each of the following, assessed independently: (a) Operable without vision. Provide at least one mode that does not require user vision. (b) Operable with low vision and limited or no hearing. Provide at least one mode that permits operation by users with visual acuity between 20/70 and 20/200, without relying on audio output. (c) Operable with little or no color perception. Provide at least one mode that does not require user color perception. (d) Operable without hearing. Provide at least one mode that does not require user auditory perception. (e) Operable with limited manual dexterity. Provide at least one mode that does not require user fine motor control or simultaneous actions. (f) Operable with limited reach and strength. Provide at least one mode that is operable with user limited reach and strength. (g) Operable without time-dependent controls. Provide at least one mode that does not require a response time. Alternatively, a response time may be required if it can be by-passed or adjusted by the user over a wide range. (h) Operable without speech. Provide at least one mode that does not require user speech. (i) Operable with limited cognitive skills. Provide at least one mode that minimizes the cognitive, memory, language, and learning skills required of the user. 1193.43 Output, display, and control functions. All information necessary to operate and use the product, including but not limited to, text, static or dynamic images, icons, labels, sounds, or incidental operating cues, shall comply with each of the following, assessed independently: (a) Availability of visual information. Provide visual information through at least one mode in auditory form. (b) Availability of visual information for low vision users. Provide visual information through at least one mode to users with visual acuity between 20/70 and 20/200 without relying on audio. (c) Access to moving text. Provide moving text in at least one static presentation mode at the option of the user. (d) Availability of auditory information. Provide auditory information through at least one mode in visual form and, where appropriate, in tactile form. (e) Availability of auditory information for people who are hard of hearing. Provide audio or acoustic information, including any auditory feedback tones that are important for the use of the product, through at least one mode in enhanced auditory fashion (i.e., increased amplification, increased signal-to-noise ratio, or combination). For transmitted voice signals, provide a gain adjustable up to a minimum of 20 dB. For incremental volume control, provide at least one intermediate step of 12 dB of gain. (f) Prevention of visually-induced seizures. Visual displays and indicators shall minimize visual flicker that might induce seizures in people with photosensitive epilepsy. (g) Availability of audio cutoff. Where a product delivers audio output through an external speaker, provide an industry standard connector for headphones or personal listening devices (e.g., phone-like handset or earcup) which cuts off the speaker(s) when used. (h) Non-interference with hearing technologies. Reduce interference to hearing technologies (including hearing aids, cochlear implants, and assistive listening devices) to the lowest possible level that allows a user to utilize the product. (i) Hearing aid coupling. Where a product delivers output by an audio transducer which is normally held up to the ear, provide a means for effective wireless coupling to hearing aids. 5.3. Proposed Family Standards: Information Presentation 5.3.1. Common IP Standards Many of the IP standards have similar requirements. Can we just list these in one place and say they apply to all EIT doing IP? Are there similar standards that belong on top of all the family efforts? 5.3.2. Desktop Software [Jim Thatcher] 5.3.2 Desktop Software Standards 5.3.2.1 Keyboard Access 5.3.2.1.1. All actions required or available by the program must be available from the keyboard. (i.e., keyboard equivalents for all mouse actions.) Mouse actions that are fundamentally two dimensional, like drawing an arc, encircling an area, or attaching graphical objects are excluded from this requirement. 5.3.2.1.2. The software must provide logical interaction with interface objects (logical tab order between buttons, lists etc.). Fast path keys must be provided for commonly used objects when 7 or more objects are in displayed (Ctrl+P for print or alt+c for cancel). [This says that if there are no commonly used objects, they do not need to have accelerator keys.] 5.3.2.1.3. Clear and precise instructions for the use of all keyboard functions shall be provided as part of the user documentation. 5.3.2.1.4. The software shall not interfere with existing accessibility features built into the operating system (such as Sticky Keys, Slow Keys, Repeat Keys in Microsoft Windows). 5.3.2.1.5. If timed responses are required by the software then it shall allow user adjustment of timing. 5.3.2.2. Object Information 5.3.2.2.1. There must be a well defined visual focus indicator that moves among interactive objects as the input focus changes. The focus indication must be programmatically exposed to assistive technology. 5.3.2.2.2. Assistive technology must be able to determine enough information about user interface objects to be able to understand their use (e.g., object is a text box with label "enter password," or a check box which is checked). 5.3.2.3. Icons 5.3.2.3.1. Either icons must have text attached (as in the desktop icons in Windows 95) or meaningful text must be available to assistive technology, as a text pop-ups or bubble help, for example. 5.3.2.3.2. The use of icons shall be consistent throughout the application. 5.3.2.3.3. Provide menu equivalents or hot keys (Ctrl+P for Print) for all tool bar functions. [Tool bar functions are assumed to be very common functions. We probably should require hot keys for all of them.] 5.3.2.3.4. Use system text drawing tools or provide text through an application programming interface supporting interaction with assistive technology. (Painted text may not be accessible to screen readers. ) 5.3.2.4. Sounds 5.3.2.4.1. Provide a visual cue for all audio alerts. 5.3.2.4.2. Support the Sounds feature where built into the operating system. (Such as Microsoft Windows 95 show sounds feature.) 5.3.2.4.3. Allow the user to disable sound and adjust the volume. 5.3.2.4.4. Wherever and whenever information is presented in audio format, it shall be capable of being displayed by the user in text format, wither as closed captioning, a pop-up window, or other means, in parallel with the audio information. 5.3.2.5. Display 5.3.2.5.1. Do not use color coding as the only means of conveying information or indicating an action. Always provide an alternative or parallel method that can be used by individuals who do not possess the ability to identify colors. 5.3.2.5.2. Provide a wide variety of color and font settings. Respect operating system color and font settings. 5.3.2.5.3. If patterned backgrounds behind text or graphics are part of your product, allow users to turn that feature off. 5.3.3. Web based information [Judy, Wayne] 5.3.4. Office equipment and other hardware [Charles Abernathy] FAMILY: 5.3 Information Presentation: Office Equipment and Other Hardware (including displays) to both create and control information and data. Should be capable of supporting Software and Web-based information presentation. PRESENTATION OF INFORMATION [from "First Rough Draft: Function Based Performance Guidelines, 12/1/98, www.trace.wisc.edu/eitaac/functionalperf.gtm?functional+perf ormance [1]] DESIGN GOAL: "(All) technologies that present information to the user for any purpose (directly or indirectly) should be able to present the information in visual, visually enhanced, audible, audibly enhanced, and tactile form [except where it would present an undue burden]." [1]. FUNCTIONAL REQUIREMENT: "Technologies that present information to the user for any purpose (directly or indirectly) will do so in a fashion that can be perceived by a person [except where it would present an undue burden]" [1]: * without vision * with low vision and no hearing * without hearing * who is hard of hearing and without vision * who cannot see or hear * cannot read * have limited skills in the language(s) used" [1]. Following clauses presented by SENSORY/MOTOR/COGNITIVE headings: SENSORY: * No Vision * Low Vision * Color Blind * Color Weak * Monocular * Visually Seizure Sensitive * Deaf * Hard of hearing * Speech in noise * Monaural * Acoustically Seizure Sensitive * No Tactile * Loa Tactile Sensitivity MOTOR: * Mobility * Dexterity * Articulation NEUROLOGICAL: * Cognitive impairment * Learning disabilities * Speech and language impairment * Attention deficits * Sequencing deficits COMBINATIONS: * Thereof --------------------------- FUNCTIONAL REQUIREMENT: "Technologies which present information in a time sequenced manner should allow the user to control the pace of delivery over a very wide range, be able to freeze presentation at any time and allow the information to be re-presented in whole or in part [except where it would present an undue burden]." [1]. EXAMPLE DESIGN SCENARIO: "a very wide range (5 x normal)" [1]. FUNTIONAL REQUIREMENT: "Technologies which provide a presentation function should avoid triggering seizures in users who are sensitive to presentational stimulation (for example, people with photosensitive epilepsy who can experience a seizure when exposed to flashing light in certain frequency ranges and above certain brightness [except where it would present an undue burden]." [1]. FUNCTIONAL REQUIREMENT: "Technologies that provide presentation functions that cannot meet the above for all users should provide a mechanism for connecting an alternate display [except where it would present an undue burden]." [1]. EXAMPLE DESIGN SCENARIO: "wirelessly connecting" [1]. "(remote console)" [1]. FUNCTIONAL REQUIREMENT: "Technologies that are meant to be interacted with via voice should also support TTY interaction [except where it would present an undue burden]." [1]. ---------------- * Without Vision FUNCTIONAL REQUIREMENT: "Access to visually displayed information. The capability to access the screen is necessary to support the speech or Braille output requirement of many blind users." [2]. EXAMPLE DESIGN SCENARIOS: "Currently, blind users are able to select and review the spoken or Braille equivalent of text from any portion of the screen while using standard applications software. Third-party vendors should have access to the screen contents in a manner that can be translated and directed to any internal speech chip, a speech synthesizer on a serial or parallel port, or a Braille display device [except where it would present an undue burden]." [2]. DESIGN GOAL: "Information presented pictorially also needs to be available in such a manner that, as software sophistication improves, it may eventually be translated using alternative display systems [except where it would present an undue burden]." [2]. FUNCTIONAL REQUIREMENT: "Auditory output. The auditory output capability on current microcomputers is sufficient to beep and play music. However, some users with disabilities may require speech capability [except where it would present an undue burden]." [2]. EXAMPLE DESIGN SCENARIO: "A speech synthesizer is required to generate speech on today's computers [except where it would present an undue burden]. The capability to support a speech synthesizer should continue to be available in future generations of computers, or this capability may be internalized through an upgrade of the computer's internal speaker [except where it would present an undue burden]." [2] DETAILED DESIGN REQUIREMENT: "The speech capability should include user-adjustable volume control and a headset jack [except where it would present an undue burden]." [2] * Without Vision, Low Vision, Cannot Handle Complex Tasks FUNCTIONAL REQUIREMENT: "Sequentialisation. The presentation of data on a Braille display, or using a speech synthesizer, or magnifying the data on the screen, has to put the components in a sequence. The order in which these components are presented is important for the understanding of the global meaning [except where it would present an undue burden]." [6.4 of 3] EXAMPLE DESIGN SCENARIO: "As the number of components present in a screen is generally limited, two basic keys (up and down arrows) constitute a simple mechanism to explore the screen [except where it would present an undue burden]." [6.4 of 3]. FUNCTIONAL REQUIREMENT: "Specific Guidance. Since a visually impaired user can not apprehend the screen globally, a part of its meaning and clarity is lost. Some extra guidance is therefore useful to compensate this handicap [except where it would present an undue burden]." [6.4 of 3] EXAMPLE DESIGN SCENARIO: "This guidance can be given using textual comments just before an interaction component or just after [except where it would present an undue burden]." [6.4 of 3]. DETAILED DESIGN REQUIREMENT: "Messages should be informative but concise, and should be presented in small amounts which are easy to retain [except where it would present an undue burden]. This is also useful for dyslexic and older users." [6.4 of 3]. FUNCTIONAL REQUIREMENT: "Non verbal feedback. Non verbal feedback is extremely useful in non-visual interfaces in order to convey feedback rapidly. It can concern feedback on events that the user[] is expecting and wants confirmation about - like going to the next or previous line or element - or to give low level warning like "no more element after this one" [except where it would present an undue burden]." [6.4 of 3]. EXAMPLE DESIGN SCENARIO: "Using beeps is a simple and low cost method to achieve this. Beeps are also compatible with the different types of adaptation based either on Braille, speech or data magnification [except where it would present an undue burden]." [6.4 of 3]. EXAMPLE DESIGN SCENARIO: "Non-speech sounds should be used for all messages/feedback which are ubiquitous throughout the system. In particular they should be used to indicate: * The end of a list * Page down * New input field * A key which has no function at that particular time [except where it would present an undue burden]." [6.4 of 3]. DETAILED DESIGN REQUIREMENT: "A speech explanation which can be turned off once the user is familiar with the beeps may also be useful [except where it would present an undue burden]." [6.4 of 3]. * No Vision. All. FUNCTIONAL REQUIREMENT: "There should be a way for the user to return the appliance to a state where all mode settings are known [except where it would present an undue burden]." [7]. EXAMPLE DESIGN SCENARIO: "This [state where all mode settings are known] is different from the "reset" function that many appliances have to restore factory settings. The intent here is to enable the operator to predict what will happen when specific procedures are executed. If the operator makes a mistake in executing the procedure, he or she should be able to return to a known starting point to try again. In addition, the operator should be able to perform any desired function from this known state with a minimum number of keystrokes [except where it would present an undue burden]." [7]. EXAMPLE DESIGN SCENARIO: "Speech should be responsive and interruptible [except where it would present an undue burden]." [7]. DETAILED DESIGN SCENARIO: "This means that it [speech] can be stopped and started almost instantly, simply by pressing a key which causes new speech to be generated [except where it would present an undue burden]." [7]. EXAMPLE DESIGN SCENARIO: "A button should be provided which causes the speech to speak the entire display, if it is one line, or the entire list of menu choices, if the display consists of multiple lines. If a choice is to be selected from a list, a method should be provided to speak each choice individually so that the operator will know what is being selected [except where it would present an undue burden]." [7]. * No Vision. Low Vision. EXAMPLE DESIGN SCENARIO: "Modification of services. Not all service characteristics can be dealt with at the terminal level. This implies the need to adapt services modifying directly the way in which a service is provided. The service provider would have to be directly involved in the adaptation activity. "Some service characteristics that can be dealt with only at the service level are the following: * Graphical banners * Menus presented by graphical means (e.g., icon lists) * Textual description of images * Frame based presentation of information * Short timeouts * Status line * No information when in input mode" [except where it would present an undue burden]." [5.2.2 of 3]. * No Vision. Low Vision. FUNCTIONAL REQUIREMENT: "Provide a visual cue for all audio alerts [except where it would present an undue burden]." [Page 2 of 3, 4]. EXAMPLE DESIGN SCENARIO: "Support the Sounds feature where built into the operating system (such as Microsoft Windows 95 "show sounds" feature.) [except where it would present an undue burden]." [Page 2 of 3, 4]. FUNCTIONAL REQUIREMENT: "Allow the user to disable or adjust sound volume [except where it would present an undue burden]." [Page 2 of 3, 4]. ----------------------- * With Low Vision EXAMPLE DESIGN SCENARIO: "Large print display. There should be a means for enlarging a portion of the screen for a low- vision user. This process uses a window or similar mechanism allowing magnification to be controlled by a user. A user can invoke the large-print display capability from the keyboard or control pad for use in conjunction with any work-related applications software [except where it would present an undue burden]. If applications software includes graphics, enlargement of graphic displays should also be available [except where it would present an undue burden]."[2]. FUNCTIONAL REQUIREMENT: "Color presentation. When colors must be distinguished in order to understand information on the display, color-blind end users should be provided with a means of selecting colors to be displayed [except where it would present an undue burden]." [2]. * With Low Vision. DETAILED DESIGN REQUIREMENTS: "* Good contrast with the background should be provided for text and graphics. Display should give a minimum contrast ratio of 3:1 for positive displays, and a maximum of 1 to 20 for negative displays." BASED NOT ON DISABLED * Provide for adequate, adjustable illumination of [passive] LCD displays whenever possible. * Use back illumination of LCD screens whenever possible (a simple regulation of contrast or brightness is not sufficient) * Anti-glare provision to avoid reflections whenever possible * Possibility to tilt the display * Any anti-glare reduction measure should not decrease the quality of sharpness of characters nor darken too much the background, blue has been found to be a good background color * Combination of blue, green, and violet should be avoided * Color alone should not carry information * If a dot matrix display is used a cell of 9x7 is the preferred minimum, with the addition of four rows to accommodate line spacing, lower case ascenders and descenders and accents BASED NOT ON DISABLED * Large fonts should be used whenever possible (10, 12 points minimum, better 16), a minimum of 3 mm high for 500 mm viewing distance BASED NOT ON DISABLED * Light weight, extra bold and condensed typefaces should be avoided, especially when used in reverse mode * The possibility to choose and enlarge typeface should be provided * Serif fonts (e.g. Times) are less readable than sans serif (e.g. Tiresias Screenfont) * Avoid typeface with numerals with tails curling up * Distance among lines should be at least 20% of typeface dimension BASED NOT ON DISABLED * Upper and lower case type is easier to read than upper case only BASED NOT ON DISABLED * Do not use more than 3 luminance levels in the screen [except where it would present an undue burden]." [6.1 of 3]. * Low Vision. EXAMPLE DESIGN SCENARIO: "Highlighting should also be viewable with inverted colors [except where it would present an undue burden]." [Page 2 of 3, 4]. FUNCTIONAL REQUIREMENT: "Do not use patterned backgrounds behind [except where it would present an undue burden]" [Page 2 of 3, 4]. EXAMPLE DESIGN SCENARIO: "text or important graphics [except where it would present an undue burden]." [Page 2 of 3, 4]. EXAMPLE DESIGN SCENARIO: "Individual user override of application default fonts for printing and text displays are required [except where it would present an undue burden]." [Page 2 of 3, 4]. EXAMPLE DESIGN SCENARIO: "Allow user adjustment of, or allow user to disable flashing, rotating or moving displays to the extent that this does not interfere with the purpose of the application [except where it would present an undue burden]." [Page 2 of 3, 4]. * Low Vision. EXAMPLE DESIGN SCENARIO: "Characters. Characters displayed on the screen shall be in a sans serif font. Characters shall be 3/16 inch (4.8 mm) minimum in height based upon the uppercase letter "I". Characters shall contrast with their background with either light characters on a dark background or dark characters on a light background [except where it would present an undue burden]." QUESTIONABLE BASIS/BASED NOT ON DISABLED? [707.5.4.2, 5]. * Low Vision. No vision. Hard of hearing. Deaf. EXAMPLE DESIGN SCENARIO: "Receipts and Verification. Where a receipt is available and is requested, the following options shall be provided: a printed receipt, audible presentation of the transaction information provided on the receipt, or both [except where it would present an undue burden]." [707.5.6, 5]. ------------------- * Color weak. Color blind. FUNCTIONAL REQUIREMENT: "Do not use color-coding as the only means of conveying information or indicating an action. Always provide an alternative or parallel method that can be used by individuals who do not possess the ability to identify colors [except where it would present an undue burden]." [page 2 of 3, 4]. EXAMPLE DESIGN SCENARIO: "The application must support user- defined color settings system-wide [except where it would present an undue burden]." [Page 2 of 3, 4]. * Color weak. EXAMPLE DESIGN SCENARIO: For color weak (or bad lighting), make any color coding from the following list: red, orange, yellow, blue, purple, gray, buff, white, black [except where it would present an undue burden]. [Federal Specification TT-C-595]. ---------------------- * No hearing. Hard of Hearing. FUNCTIONAL REQUIREMENT: "Wherever and whenever information is presented in audio format, it shall be capable of being displayed by the user in text format, [except where it would present an undue burden]." [Page 2 of 3, 4]. EXAMPLE DESIGN SCENARIOS: "either as closed-captioning, a pop-up window, or other means, in parallel with the audio information." [except where it would present an undue burden]. [Page 2 of 3, 4]. * Without Hearing or Hard of Hearing FUNCTIONAL REQUIREMENT: "Information redundancy. Currently, several programs activate a speaker in the microcomputer to provide information to the user. Some programs do not have the capability to present this information visually to the hearing-impaired user. An information redundancy feature presents a visual equivalent of the auditory information provided [except where it would present an undue burden]." [2]. ------------------- * Low Mobility. EXAMPLE DESIGN SCENARIO: "The screen shall be visible from a point located 40 inches (1015 mm) above the center of the clear floor space in front of the machine [except where it would present an undue burden]. EXCEPTION: This requirement shall not apply to drive-up only automatic teller machines." [707.5.4.1, 5]. -------------- * All. GOAL: " Privacy. The opportunity for the same degree of privacy of output shall be available to all individuals utilizing the equipment [except where it would present an undue burden]." [707.5.1, 5]. EXAMPLE DESIGN SCENARIO: "A headphone jack should be provided for private listening. This will enable the blind person to hear confidential information as in the case of an automatic teller machine [except where it would present an undue burden]." [7]. -------------- * Adaptation FUNCTIONAL REQUIREMENT: "Open software architecture. ... support an adaptation strategy based on a general architecture [except where it would present an undue burden]". [6.5 of 3]. EXAMPLE DESIGN SCENARIO: "The Communication Module has three main functions: * To transfer the information displayed on the screen to the adaptation software as soon as this information appears. * To inform the adaptation software when a full screen has been completed * To emulate any of the actions usually performed ... to control the dialogue ... [except where it would present an undue burden]." [6.5 of 3]. EXAMPLE DESIGN SCENARIO: "The Adaptation Software has to optimize the presentation of data, which often implies reconstructing the initial data on the screen (different order, additional comments, rephrasing, etc)." [6.5 of 3]. EXAMPLE DESIGN SCENARIO: "The Non Visual Interface handles interactions on the specific peripherals (Braille terminal / speech synthesizer / adapted screen / keyboard) [except where it would present an undue burden]." [6.5 of 3]. EXAMPLE DESIGN SCENARIO: "This architecture can lead to different hardware solutions. For instance, the adaptation software and the non-visual interface can be run by an external device or run internally by the ... [except where it would present an undue burden]." [6.5 of 3]. FUNCTIONAL REQUIREMENT: "Terminal Adaptation. Usually the terminal needs to be adapted [except where it would present an undue burden]" [4.0 of 3]. EXAMPLE DESIGN SCENARIOS: "[by] developing and integrating special software modules: * An event/interrupt Interceptor intercepting data displayed on the screen and any key pressed * A translation module to crate a textual representation of the data on the screen * A system for enlarging text on the screen, with the ability to scroll if necessary * A screen reader that manages user commands and allows navigation on the screen. This would have a "screen reading" mode to allow the user to move around the screen without moving the cursor or performing an operation. * Drivers allowing output through larger screen, speech synthesizers and Braille displays * A communication module in case other software components are installed on different devices [except where it would present an undue burden]." [4.0 of 3]. ---------------------- REFERENCES: [1.] "First Rough Draft: Function Based Performance Guidelines, 12/1/98, www.trace.wisc.edu/eitaac/functionalperf.gtm?functional+perf ormance. [2.] "Managing Information Resources for Accessibility", GSA, December, 1991, H-7. [3.] "Guidelines for the Design of Screen and Web Phones to be Accessible by Visually Disabled Persons", Royal National Institute for the Blind, J. Gill (Ed.), December 1998, www.rnib.org.uk/wedo/research/sru/phones/htm. [4.] "Requirements for Accessible Software Design", Version 1.1, Software Accessibility Guidelines - Microsoft Internet Explorer, March 6, 1997. [5.] "Current ADAAG Requirements", http://www.access-board.gov/eitaac/adaag.requirements.html. [6.] "Resource Guide for Accessible Design of Consumer Electronics: Linking Product Design to the Needs of People with Functional Limitations", A Joint Venture of the Electronic Industries Alliance and the Electronic Industries Foundation. November 1996. http://www.tiaonline.org/access/guide.html. [7.] "Commercial Technology for the Blind", Curtis Chong, Monitor?, undated. --------------- CATEGORIES of Clauses: GOAL FUNCTIONAL REQUIREMENT EXAMPLE (or CONDITIONAL) DESIGN SCENARIO DETAILED DESIGN REQUIREMENT CATAGORIES of research support: BASED NOT ON DISABLED QUESTIONABLE BASIS NO RESEACH IDENTIFIED E*N*D OF 5.3.4 5.3.5. Telecommunications [Jim F] Telecommunications Family Standard Introduction Telecommunications equipment is covered by Section 508 under the definition of Electronic Information Technology. The following recommended standards are based on the Access Board's PART 1193 - TELECOMMUNICATIONS ACT ACCESSIBILITY GUIDELINES. However, since the Section 508 standard is higher than that in Part 1193 (undue burden vs. readily achievable), the guidelines have been modified into standards. Functional Specifications Access to information All information necessary to operate and use the product, including but not limited to, text, static or dynamic images, icons, labels, sounds, or incidental operating cues, shall comply with each of the following, assessed independently: 1. Availability of visual information. Provide visual information through at least one mode in auditory form. 2. Availability of visual information for low vision users. Provide visual information through at least one mode to users with visual acuity between 20/70 and 20/200 without relying on audio. 3. Access to moving text. Provide moving text in at least one static presentation mode at the option of the user. 4. Availability of auditory information. Provide auditory information through at least one mode in visual form and, where appropriate, in tactile form. 5. Availability of auditory information for people who are hard of hearing. Provide audio or acoustic information, including any auditory feedback tones that are important for the use of the product, through at least one mode in enhanced auditory fashion (i.e., increased amplification, increased signal-to-noise ratio, or combination). For transmitted voice signals, provide a gain adjustable up to a minimum of 20 dB. For incremental volume control, provide at least one intermediate step of 12 dB of gain. 6. Prevention of visually-induced seizures. Visual displays and indicators shall minimize visual flicker that might induce seizures in people with photosensitive epilepsy. 7. Availability of audio cutoff. Where a product delivers audio output through an external speaker, provide an industry standard connector for headphones or personal listening devices (e.g., phone-like handset or earcup) which cuts off the speaker(s) when used. 8. Non-interference with hearing technologies. Reduce interference to hearing technologies (including hearing aids, cochlear implants, and assistive listening devices) to the lowest possible level that allows a user to utilize the product. 9. Hearing aid coupling. Where a product delivers output by an audio transducer which is normally held up to the ear, provide a means for effective wireless coupling to hearing aids. Compatibility Telecommunications equipment and customer premises equipment shall be compatible with peripheral devices and specialized customer premises equipment commonly used by individuals with disabilities to achieve accessibility, and shall comply with the following provisions, as applicable: 1. External electronic access to all information and control mechanisms. Information needed for the operation of products (including output, alerts, icons, on-line help, and documentation) shall be available in a standard electronic text format on a cross-industry standard port and all input to and control of a product shall allow for real time operation by electronic text input into a cross-industry standard external port and in cross-industry standard format. The cross-industry standard port shall not require manipulation of a connector by the user. 2. Connection point for external audio processing devices. Products providing auditory output shall provide the auditory signal at a standard signal level through an industry standard connector. 3. Compatibility of controls with prosthetics. Touchscreen and touch-operated controls shall be operable without requiring body contact or close body proximity. 4. TTY connectability. Products which provide a function allowing voice communication and which do not themselves provide a TTY functionality shall provide a standard non-acoustic connection point for TTYs. It shall also be possible for the user to easily turn any microphone on and off to allow the user to intermix speech with TTY use. 5. TTY signal compatibility. Products, including those providing voice communication functionality, shall support use of all cross-manufacturer non-proprietary standard signals used by TTYs. Information Pass Through Telecommunications equipment and customer premises equipment shall pass through cross-manufacturer, non-proprietary, industry-standard codes, translation protocols, formats or other information necessary to provide telecommunications in an accessible format. In particular, signal compression technologies shall not remove information needed for access or shall restore it upon decompression. 5.3.6. Multimedia Information [courtesy of Larry G.] Information Presentation Subcommittee Draft requirements for MULTIMEDIA ACCESS [based, loosely, on DoEd/Thatcher document format] In addressing presentation issues for multimedia, the following document adopts a broad definition: video, audio, animation, graphics and text combined in numerous ways and delivered via a variety of platforms: video and audiotape, CD- and DVD-ROM, Internet-based, broadcast, narrowcast, and satellite-delivered. This document is also focused as narrowly as possible on CONTENT issues and not command and control of the delivery device, which are covered in other subcommittee reports. A section will address those issues which are specific to the types of controls that are common and/or needed for multimedia use. A. Alternate presentation of audio 1) When a piece of media contains audio information essential to understanding its content, the media must also be capable of creating a user-selectable visual display in text format of that audio. The types of audio that must have an alternate text presentation include narration, dialog, speech and vocal music and essential non-speech sounds such as sound effects needed for comprehension of content and identification of speakers and sound sources. Examples of audio NOT requiring alternate text presentation include incidental non-vocal background music and ambient sounds unimportant to understanding of the content. 2) Particular media formats may have one or more solutions for achieving alternate text presentation. In the case of analog (NTSC) and digital (ATSC) video, use of accepted technical specifications will assure comprehensive and common access through closed captions. That is, o Analog video must use the "EIA-608 specification" for line-21 closed caption data which will assure that alternate text presentation will be decoded on all television receivers, 13" or larger, manufactured for sale in the United States after July 1993. Adherence to this standard also assumes that television receivers purchased or used under this requirement be equipped with built-in closed caption decoder circuitry (although most TV receivers by now have such circuitry as standard equipment, stand-alone monitors and video projectors, as well as personal computers with TV reception capability, may not be so equipped). o Digital video formats, as defined by the Advanced Television Systems Committee or ATSC, must use the "EIA-708- A" specification for closed captioning. Though digital television receivers and set-top boxes used for reception of digital television signals are not yet in wide distribution, the 708 standard has been designated by the television industry and will be ruled upon by the Federal Communications Commission in the first half of 1999. 3) In the case of audio tracks provided as part of software- based multimedia, interactive or otherwise, alternate text presentation may be achieved through the use of various multimedia authoring tools (such as Adobe premiere or Macromedia Director) or may employ such formats as the W3C's Synchronized Media Interchange Language (SMIL) or Microsoft's Synchronized Accessible Multimedia Interchange format (SAMI). Regardless of authoring technology, the following guidelines will enhance comprehension via alternate text presentation: o text should be user-selectable o text should be displayed on the screen or other display device in a manner so as not to obscure other essential on- screen information o text should be clearly legible and distinguishable from background visuals o text should be fully synchronized with the audio it is reflecting o if the media is being presented in a computer operating system that offers a "ShowSounds" preference (such as Microsoft's Windows), the alternate text presentation should automatically be displayed if the user selects this preference. o triggering display of alternate text presentation should not automatically mute the audio portion of the program o the user should be able to disable or adjust sound volume B. Alternate presentation of visuals 1) When a piece of media contains visual information essential to understanding its content, the media must also be available with narrative descriptions of visual displays (user-selectable, if possible, as in software-based multimedia). Such narrative descriptions may either be voiced by a narrator in pauses between program dialog or other audio (as is common with linear video description) or rendered in text to be synthesized by a host computer and triggered at appropriate timings. Since linear video (such as the commonly available 1/2" VHS video format) cannot support user-selectable narrative descriptions, alternate copies of such videotapes with narrative description may be provided, or videotapes which include both narrated and unnarrated versions of the material may be provided. Since people with visual impairments have varying degrees of residual sight, provision of audio-only tape versions of videotapes are not acceptable. The types of multimedia-based visual information that must have available narrative descriptions include on-screen text, graphics, charts, tables, speaker identifications, settings, action and other visuals that are essential to the comprehension of the media. Examples of visuals NOT requiring narrative descriptions include incidental "decorations," non-meaningful transition effects, and other visual information unimportant to understanding of the content. 2) Particular media formats may have one or more solutions for achieving alternatives to visual presentation. In the case of analog (NTSC) and digital (ATSC) video, use of accepted technical specifications will assure comprehensive and common access through narrative descriptions. That is, o When provided via broadcast cable or satellite, analog video must use the Secondary Audio Program for delivery of narrative descriptions. Adherence to this standard also assumes that television receivers and VCRs purchased or used under this requirement be equipped with SAP or MTS decoding circuitry (although many TV receivers by now have such circuitry as standard equipment, stand-alone monitors and video projectors, as well as personal computers with TV reception capability, may not be so equipped). o Digital video formats, including digital broadcast formats defined by the Advanced Television Systems Committee must use the ancillary audio channels as defined in ATSC ancillary audio technical specifications. 3) In the case of visuals provided as part of software- based multimedia, interactive or otherwise, narrative descriptions may be achieved through the use of various multimedia authoring tools (such as Adobe premiere or Macromedia Director) or may employ such formats as the W3C's Synchronized Media Interchange Language (SMIL) or Microsoft's Synchronized Accessible Multimedia Interchange format (SAMI). Regardless of authoring technology, the following guidelines will enhance comprehension via narrative descriptions: o narrative descriptions should be user-selectable o narrative descriptions should be available to the user in a manner so as not to obscure other essential audio information, either by enabling playback in-between main program audio or by enabling pausing of dynamic multimedia content while narrative descriptions are played to the user o narrative descriptions should be clearly authored and distinguishable from other audio sources o if narrative descriptions are presented as text, they should be fully available to a user's screen reading software or should be played to the user via a device's text- to-speech engine o if the media is being presented in a computer operating system that offers a narrative description preference, the narrative descriptions should automatically be played if the user selects this preference o triggering playback of narrative descriptions should not effect the video portion of the program in any way, other than to allow the user to pause the program if extended narrative descriptions are available and desired o the user should be able to disable or adjust sound volume C. Controls Display or presentation of alternate text presentation or narrative descriptions should be user-selectable. 1) If accessed via desk-top computer equipment and software, control of these access features should either be through clearly indicated and accessible application interfaces or operating system preferences. 2) If media content is delivered via other hardware devices such as television receivers or kiosks or similar devices, access to controls should be in top-level (opening screen) menus or initial on-screen displays. D. Hardware/Equipment 1) Analog television displays must be equipped with caption decoder circuitry which receives and properly decodes and displays closed captions according to Federal Communications Commission Part 15 Rules which govern the specifications for television receivers. TV equipment not governed by these rules (i.e., monitors not equipped with built-in tuners and therefore not considered receivers and projection televisions with separate tuners) must be equipped with external closed caption decoders built to the above-named FCC Rules. 2) Digital television displays must be equipped with caption decoder circuitry which receives and properly decodes and displays closed captions according to Federal Communications Commission Rules to be established in 1999. 3) Analog television displays must be equipped with Secondary Audio Program playback circuitry as defined by the Multichannel Television Sound specification. 4) Digital television displays must be equipped with ancillary audio playback capabilities as defined by the Advanced television Systems Committee. 5) Other media delivery hardware and devices (such as integrated or standalone CD-ROMs and DVDs) must be capable of generating the audio of narrative descriptions via integrated or attached speakers or headphones. 6) Alternate text displays require displays with a minimum level of resolution necessary for clarity and legibility. E. Conversion between formats 1) Embedded or encoded alternate text presentations (closed captions) and narrative descriptions must be preserved intact when a piece of media is copied, transmitted, reformatted (edited), or transformed for display on subsequent platforms (particularly when digitized from an original analog format). 2) "Preserved intact" includes maintaining all styles and exact timing and synchronization commands and zero introduction of errors or garbling of data. 5.3.7. ATMs/ITMs [Earl J's 2/27/99 draft, with numbering linked to the software standard ] Targeted ITM Standards & Externally Based ITM Interactions * The ITM must be useable without the need of physically attaching a device to it or copying an assistive technology from a user's disk onto it. * The software must support secure interaction with an external personal device connected to the ITM through wireless means. - The protocol enabling secure interactions must be based on industry accepted and community developed standards. - The ease of establishing a person's identity and UI display and interaction preferences must be the same for people with and without disabilities. Examples of identification methods include biometrics and smart cards. Examples of UI display preferences include magnified content and remote access. * The ITM must provide a way to receive and transmit information to an external device. The protocol, or combined protocols, used to convey a UIs content and support interaction with an ITM by an external device must be based on industry accepted and community developed standards. For example, a handset may be used to transmit UI information and short range RF or directional IR could be used to transmit UI information to and support interaction by an external device. 5.3.2.1 If a Physical Keyboard is present 5.3.2.1.1. All actions required or available by the program must <<>> <5.3.2.1.2.a Software must provide a logical navigation sequencing when the keyboard is used to navigate between associated interactive interface objects. For example, many applications targeted for English speaking locales adopt a left to right, top to bottom> <> <5.3.2.1.2.b Provide <> for all frequently used application functions in applications that contain many functions. Ctrl+P for Print is an example of a> <>. 5.3.2.1.3. instructions for the use of all keyboard functions. << >> 5.3.2.1.4. not interfere with existing accessibility features built into <> include Sticky Keys, Slow Keys, and Repeat Keys>. 5.3.2.1.5. If timed responses are required by the software then it shall allow user adjustment of timing. 5.3.2.2. Object Information 5.3.2.2.1. a well defined visual focus indicator that moves among interactive objects as the input focus changes. focus indication must be programmatically <> 5.3.2.2.2. <> must be able to be able enough information about user interface objects to be able to <> their use >. For example, exposing one object is a text field that is named by (related to) a label object named "enter password" or <> 5.3.2.3. <> 5.3.2.3.1. << >> Icons and <> must have <> 5.3.2.3.2. <> * Graphical figures such as charts and maps meant to convey information must always provide a description of what they are meant to convey. 5.3.2.3.3. The use of icons shall be consistent throughout the <>. 5.3.2.3.4. <> interaction with an external device>>. > is text content, text input carat location, <<>> and selected text.> * Painted text <> 5.3.2.4. Sounds 5.3.2.4.1 > 5.3.2.4.2 < > 5.3.2.4.3. allow the user to disable sound and adjust the volume. 5.3.2.4.4. <<>> 5.3.2.5. Display 5.3.2.5.1. Do not use color coding as the only means of conveying information or indicating an action. provide an alternative or parallel method that can be used by individuals who do not possess the ability to identify colors. 5.3.2.5.2. Provide a wide variety of color and font settings. respect color and font settings . 5.3.2.5.3. If patterned backgrounds behind text or graphics are part of your product, allow users to turn that feature off through a GUI that utilizes high contrast design methods. * The UI must provide pre-determined and easily accessed alternate UI presentation modalities for users who are not able to view information presented in the default modality (i.e. visually based). This means it must allow the user to choose from the following presentation options: - Present text, interactive object, and key graphic based information in an audio format - Allow the ability to change the size and contrast of text, interactive objects, and graphics meant to convey information (e.g. a car rental add) - Present the content of synchronized and streaming audio in a text based visual and audio manner (e.g. closed captioning) - Support programmatic UI access, display, and interaction of the ITM UI onto externally "connected" devices by use of industry accepted and community developed standards. * Provide a visual, tactile, and programmatic based way that allows a user to change the way information is displayed. Examples include GUI and physical buttons fronted with the international symbol for disability access. 5.3.8. PDAs/Thin Clients 5.4. Proposed Family Standards: Input and Controls 5.4.1 Limited reach and strength IST ONE - GENERAL FACTORS FOR CREATING MORE ACCESSIBLE PRODUCTS NOTE: - SINCE THERE ARE OFTEN MULTIPLE WAYS TO ACHIEVE A FUNCTION, NOT ALL CONTROLS NEED TO BE ACCESSIBLE. JUST ENOUGH TO ALLOW THE PERSON TO BE ABLE TO OPERATE THE FULL FUNCTIONS OF THE PRODUCT. Operable with limited reach and strength. - Provide at least one mode that is operable with user limited reach and strength. TAAG 1193.41 (f)] Providing Basic Access - See also: Operable with limited manual dexterity TAAG 1193.41(e)] - minimizing the amount of force needed to operate or adjust controls. - ensure controls are reachable. - facilitate connection or insertion of objects (connectors, media, plugs, jacks, cards, etc.) - Use wireless connection strategies that eliminate the need to orient or insert connectors, plugs, jacks, cards, etc.; (i.e. Infrared). Overcoming Major Usability Issues - help support the weight of the hand and arm or any components of the device. - prevent the loss of loose components of a product. Other Increase Ease of Use - help ensure that the product is accessible "out of the box." (that the user does not have to have someone else set-up, start-up, adjust timing parameters, etc. to make it usable) ------------------------------------- LIST TWO - POSSIBLE IDEAS AND STRATEGIES FOR INCREASING ACCESSIBILITY + Operable with limited reach and strength. [Provide at least one mode that is operable with user limited reach and strength. TAAG 1193.41 (f)] + Strategies for Providing Basic Access - See also: Operable with limited manual dexterity [TAAG 1193.41(e)] + Strategies for minimizing the amount of force needed to operate or adjust controls. - Provide power assisted control (electric pushbutton, software or auto ejection, remote control, etc). - Provide adjustable activation force for controls. - Provide controls with activation forces less than (100 grams????) - Provide bearings or rollers for heavy objects that need to be moved. - Provide user interface components which require minimum force for position adjustment + Strategies to ensure controls are reachable. + Optimize location of controls, components, displays, and output for reach and sight from various approach conditions and heights (standing/walker, wheelchair, etc) with minimum changes in body position. ( 36-48" from floor) - Avoid placing controls where the user has to lean or look in the back in order to see or use them. - Location, height, and slant of keyboard should be adjustable. - The most frequently used controls should be placed in the most accessible positions. + Strategies to facilitate connection or insertion of objects (connectors, media, plugs, jacks, cards, etc.) - Provide wrist or arm support for users while using controls or inserting objects. - Locate frequently used controls, slots, etc where users have direct visual access and where they can be easily reached with minimal change in body position. (at the front) - Allow receptacles to be repositioned for better accessibility. - Use wireless connection strategies that eliminate the need to orient or insert connectors, plugs, jacks, cards, etc.; (i.e. Infrared). - Provide power assisted control (electric pushbutton, software or auto ejection, remote control, etc). + Strategies for Overcoming Major Usability Issues + Strategies to help support the weight of the hand and arm or any components of the device. - Provide physical key-guards for keyboards or keypads. - Provide wrist or arm support for users while using controls or inserting objects. - Locate controls, which must be operated frequently, in positions closest to the individual and where they have best support. - Lift and hold handsets may present difficulty for mobility impaired users. Headset phones, speakerphones, special switches, and phone cradles are options for some users. - Ensure that devices have stable, non-slip bases, or the ability to be attached to a stable surface. + Strategies to prevent the loss of loose components of a product. - Covers, lids, doors and other loose components should be hinged, tethered, or otherwise connected to the product + Other Strategies to Increase Ease of Use + Strategies to help ensure that the product is accessible "out of the box." (that the user does not have to have someone else set-up, start-up, adjust timing parameters, etc... to make it usable) - Minimize and simplify mechanical assembly and set-up -------------------------------------------------- 5.4.2 Operable without speech LIST ONE - GENERAL FACTORS FOR CREATING MORE ACCESSIBLE PRODUCTS NOTE: - SINCE THERE ARE OFTEN MULTIPLE WAYS TO ACHIEVE A FUNCTION, NOT ALL CONTROLS NEED TO BE ACCESSIBLE. JUST ENOUGH TO ALLOW THE PERSON TO BE ABLE TO OPERATE THE FULL FUNCTIONS OF THE PRODUCT. Operable without speech. - Provide at least one mode that does not require user speech. TAAG 1193.41 (h)] Providing Basic Access - providing alternatives to speech controlled functions. Overcoming Major Usability Issues - Consider adjusting the detection mechanism, or requiring a keypress from the user to terminate recording. (Slow or breathy speech may result in the system detecting silence and thus prematurely shutting off recording mechanism.) ------------------------------------- LIST TWO - POSSIBLE IDEAS AND STRATEGIES FOR INCREASING ACCESSIBILITY + Operable without speech. [Provide at least one mode that does not require user speech. TAAG 1193.41 (h)] + Strategies for Providing Basic Access + Strategies for providing alternatives to speech controlled functions. + Make the product entirely usable and adjustable from the keyboard - Follow GUI guidelines for keyboard equivalents of standard functions - Enable the system to accept and play back text messages, by playing the text through a speech synthesis system. - Ensure that entry from TTYs is accepted in lieu of touchtone pad and speech (Must be accompanied by TTY output instead of speech) + Strategies for Overcoming Major Usability Issues - Consider adjusting the detection mechanism, or requiring a keypress from the user to terminate recording. (Slow or breathy speech may result in the system detecting silence and thus prematurely shutting off recording mechanism.) 5.4.3 Operable with limited manual dexterity LIST ONE - GENERAL FACTORS FOR CREATING MORE ACCESSIBLE PRODUCTS NOTE: - SINCE THERE ARE OFTEN MULTIPLE WAYS TO ACHIEVE A FUNCTION, NOT ALL CONTROLS NEED TO BE ACCESSIBLE. JUST ENOUGH TO ALLOW THE PERSON TO BE ABLE TO OPERATE THE FULL FUNCTIONS OF THE PRODUCT. Operable with limited manual dexterity. - Provide at least one mode that does not require user fine motor control or simultaneous actions. TAAG 1193.41 (e)] Providing Basic Access - See also: Operable with limited reach and strength TAAG 1193.41(f)] - reduce accidental activation of controls and help to ensure that the desired control is activated instead. - avoiding functions that require simultaneous actions to activate or operate. (e.g. requires two hands to open, or multiple finger operations). - providing alternatives for functions and controls that require sustained motion such as pointing, tracking, and scrolling features. - designing controls that can be activated with a stick, the side of the hand, elbow, pencil or other implement - avoiding controls and mechanisms or knobs that require twist motions, i.e. rotation of the wrist or pinch and twist or grasp and twist. - avoiding hazardous situations - See also: reduce accidental activation of controls and help ensure that the desired control is activated instead. Overcoming Major Usability Issues - facilitate connection or insertion of objects (connectors, media, plugs, jacks, cards, etc.) - Use wireless connection strategies that eliminate the need to orient or insert connectors, plugs, jacks, cards, etc.; (i.e. Infrared). - help stabilize hand and arm or eliminate the need for stabilization while using the device. - providing indication of control activation and operation - prevent the loss of loose components of a product. Other Increase Ease of Use - Design controls which can be manipulated easily with either left or right hand. - Provide redundant modes of operation utilizing the next larger set of motor movements (finger-hand-arm-foot) - Location, height, and slant of keyboard should be adjustable. - Make controls adequate size or provide an alternate means for small controls - Gain should be adjustable for both coarse and fine movement of pointing devices. - reduce the number of controls. - Provide programmable macros or shortcuts for frequently used sequences of actions . (i.e. speed dial) - help ensure that the product is accessible "out of the box." (that the user does not have to have someone else set-up, start-up, adjust timing parameters, etc_ to make it usable) ------------------------------------- LIST TWO - POSSIBLE IDEAS AND STRATEGIES FOR INCREASING ACCESSIBILITY + Operable with limited manual dexterity. [Provide at least one mode that does not require user fine motor control or simultaneous actions. TAAG 1193.41 (e)] + Strategies for Providing Basic Access - See also: Operable with limited reach and strength [TAAG 1193.41(f)] + Strategies to reduce accidental activation of controls and help to ensure that the desired control is activated instead. - Provide a function that ignores multiple rapid activations of the same key as could be caused by tremor or palsy (a.k.a. BounceKeys). - Allow key repeat functions to be adjusted over a wide range and / or to be turned off (a.k.a. RepeatKeys). - Provide an option where buttons must be depressed for an adjustable period of time before they are accepted as input (a.k.a. SlowKeys). - Use a two step "select and confirm" to reduce accidental selections (esp. for critical or non reversible functions). + Provide physical guards to make accidental activation more difficult. - Provide switch guards, especially for critical switches. - Provide physical key-guards for keyboards or keypads. - Recess or provide guard bars between buttons. - Increase the force needed to activate critical or dangerous controls - Provide a lockout for critical or dangerous controls - Provide the ability to cancel an input, undo an operation or otherwise "back up." - Leave adequate space around and between keys and controls for adaptive levers, special labels (e.g. Braille), for grasping, and accidental activation avoidance - Avoid gang mounted controls (unless alternate mode of activation is provided). - Provide a mode where keys are announced when pressed but only activated if they are held down for a (user adjustable) period of time. + Strategies for avoiding functions that require simultaneous actions to activate or operate. (e.g. requires two hands to open, or multiple finger operations). - Do not require simultaneous operation of keys or chordic keystrokes (SHIFT + mouse click or CTRL + F5) unless providing an alternate mode where keys can be pressed sequentially (e.g. StickyKeys). - Do not require simultaneous manipulations such as requiring the user to hold the mouse button down while moving the mouse (i.e. drag & drop, menu selection). Allow click-click as an alternative to click-and-drag or allow click-lock to hold the button down. - Do not require triple-clicking or the use of SHIFT and ALT to modify mouse clicks (Use only if alternative is available). + Avoid complex manipulations (such as pushing & rotating, grasping & pulling, grasping & twisting, pinching & twisting, etc) or provide alternatives. - Design rotary controls so that they can be operated without grasping and twisting (e.g., a thin pie slice shape or edge control). - Avoid (or provide an alternate means for) pull switches which require grasp and pull. - Avoid dual latches/handles that require simultaneous activation. + Strategies for providing alternatives for functions and controls that require sustained motion such as pointing, tracking, and scrolling features. + Make the product entirely usable and adjustable from the keyboard - Allow the keyboard to be used to move the mouse pointer around the screen (a.k.a. MouseKeys). - Follow GUI guidelines for keyboard equivalents of standard functions - Use TAB or arrow keys to move between options on the screen - Support speech input/voice recognition to activate functions and as alternatives to typing, dialing, and using keyboards or mouse. + Strategies for designing controls that can be activated with a stick, the side of the hand, elbow, pencil or other implement - Use a textured non-slip surface for controls (and other objects.) - Use buttons which are slightly dished, recessed or contained within a raised boundary. If using a flat touch panel, provide a raised ridge around the edge of control areas. - Provide power assisted control (electric pushbutton, software or auto ejection, remote control, etc). - Use concave keys rather than convex or flat membrane keys when designing key pads and other button style controls. + Strategies for avoiding controls and mechanisms or knobs that require twist motions - i.e. rotation of the wrist or pinch and twist or grasp and twist. - Use pushbuttons, rocker switches, or sliding switches. - Use latches or handles that can be opened with a closed fist - Shape products and handles to minimize wrist bending or body repositioning. - Use automatic or easy-to-handle doors (e.g. magnetic clasps, push buttons, push-to-spring opening, lever, or remote control) + Strategies for avoiding hazardous situations - Provide automatic timed shut-off for devices that might cause a hazard if left on. - Make all connectors and surfaces safe to explore by touch (electrically safe and free of sharp edges or hot surfaces) even if contact with body part is not normally expected. - See also: Strategies to reduce accidental activation of controls and help ensure that the desired control is activated instead. + Strategies for Overcoming Major Usability Issues + Strategies to facilitate connection or insertion of objects (connectors, media, plugs, jacks, cards, etc.) - Removable media and parts should be rugged and "hard- cased" to accept light clamping. + Facilitate reaching and grasping with clenched fists or special mobility aids (e.g., artificial limbs or hands, mouth-sticks, etc.) - Use a textured non-slip surface for controls (and other objects.) - Objects should eject 1" and preferably 2" to facilitate grasping with fists or tools. - Provide power assisted control (electric pushbutton, software or auto ejection, remote control, etc). + Provide simple self-guiding/orienting features for insertion of objects. - Bevel (or funnel) opening to facilitate insertion of objects. - Use orientation independent objects, connectors and media receptacles. - Ensure that an object cannot be inserted improperly. - Use wireless connection strategies that eliminate the need to orient or insert connectors, plugs, jacks, cards, etc.; (i.e. Infrared). - Provide wrist or arm support for users while using controls or inserting objects. + Strategies to help stabilize hand and arm or eliminate the need for stabilization while using the device. - Provide physical key-guards for keyboards or keypads. - Provide wrist or arm support for users while using controls or inserting objects. - Locate controls, which must be operated frequently, in positions closest to the individual and where they have best support. - Ensure that devices have stable, non-slip bases, or the ability to be attached to a stable surface. - Lift and hold handsets may present difficulty for mobility impaired users. Headset phones, speakerphones, special switches, and phone cradles are options for some users. + Strategies for providing indication of control activation and operation - Provide an indicator light or message on display to indicate activation/confirmation. - Provide audible click or tone to indicate activation + Provide graphical feedback to indicate activation. - Display touched area in reverse video or with thick outline to indicate activation + Use a positive movement that can be felt to indicate activation. - Keys should comply with minimum travel distance so that it is obvious when they have been activated. - On pushbuttons, toggle switches, and rotary controls there should be variable resistance that gradually builds up and then drops suddenly on activation. + Strategies to prevent the loss of loose components of a product. - Covers, lids, doors and other loose components should be hinged, tethered, or otherwise connected to the product + Other Strategies to Increase Ease of Use - Design controls which can be manipulated easily with either left or right hand. - Provide redundant modes of operation utilizing the next larger set of motor movements (finger-hand-arm-foot) - Location, height, and slant of keyboard should be adjustable. + Make controls adequate size or provide an alternate means for small controls - For touch screens or panels, use large areas - Gain should be adjustable for both coarse and fine movement of pointing devices. + Strategies to reduce the number of controls. - Minimize the number of steps needed for operations, if possible, to a single non-time-dependent step. - Layer controls and menus by frequency of use (priority). Hide/shield infrequently used controls, although it must be easy to "unhide" them when needed. - Provide programmable macros or shortcuts for frequently used sequences of actions . (i.e. speed dial) + Strategies to help ensure that the product is accessible "out of the box." (that the user does not have to have someone else set-up, start-up, adjust timing parameters, etc... to make it usable) - Minimize and simplify mechanical assembly and set-up 5.4.4 Operable for people who are hard of hearing IST ONE - GENERAL FACTORS FOR CREATING MORE ACCESSIBLE PRODUCTS NOTE: - SINCE THERE ARE OFTEN MULTIPLE WAYS TO ACHIEVE A FUNCTION, NOT ALL CONTROLS NEED TO BE ACCESSIBLE. JUST ENOUGH TO ALLOW THE PERSON TO BE ABLE TO OPERATE THE FULL FUNCTIONS OF THE PRODUCT. Availability of auditory information for people who are hard of hearing. - Provide audio or acoustic information, including any auditory feedback tones that are important for the use of the product, through at least one mode in enhanced auditory fashion (I.e., increased amplification, increased signal-to-noise ratio, or combination). For transmitted voice signals, provide a gain adjustable up to a minimum of 20 dB. For incremental volume control, provide at least one intermediate step of 12 dB of gain. TAAG 1193.43 (e)] Providing Basic Access - ensuring that auditory information is perceivable. - Provide private or secure monitoring of audio display of private information by the user Overcoming Major Usability Issues - making spoken information easier to understand. - ensure that messages important to operation are not missed - especially if not understood the first time. Additional Strategies - presenting visual information in auditory and/or tactile forms. ----- Non-interference with hearing technologies. - Reduce interference to hearing technologies (including hearing aids, cochlear implants, and assistive listening devices) to the lowest possible level that allows a user to utilize the product. TAAG 11931.43 (h)] Providing Basic Access - Design product so that it does not create interference for hearing aids. ----- Hearing aid coupling. - Where a product delivers output by an audio transducer which is normally held up to the ear, provide a means for effective wireless coupling to hearing aids. TAAG 11931.43 (I)] Providing Basic Access - Provide inductive loop for direct coupling with hearing aids. - For product which are held up to the ear, provide enough electromagnetic leakage so that hearing aid T-coils can pick up the signal. ------------------------------------- LIST TWO - POSSIBLE IDEAS AND STRATEGIES FOR INCREASING ACCESSIBILITY + Availability of auditory information for people who are hard of hearing. [Provide audio or acoustic information, including any auditory feedback tones that are important for the use of the product, through at least one mode in enhanced auditory fashion (I.e., increased amplification, increased signal-to-noise ratio, or combination). For transmitted voice signals, provide a gain adjustable up to a minimum of 20 dB. For incremental volume control, provide at least one intermediate step of 12 dB of gain. TAAG 1193.43 (e)] + Strategies for Providing Basic Access + Strategies for ensuring that auditory information is perceivable. - Use sounds with strong mid-low frequency components, 500- 1500 Hz. (for alarms use at least 2 strong mid-frequency components). + Provide adjustable volume control, preferably with easy to see (visual) indication of volume. - Permit amplification boost by 20-30 dB. Target signal to noise ratio of at least 20 dB. - Provide user-selectable way for volume to automatically return to unamplified levels - or to remain at most recent volume setting. - Use incremental indicators for volume measurement - Use loud default volume settings (77dB) - Provide loudest possible undistorted volume capacity + Reduce background noise - Locate speakers and headphones in the front of the device and away from other noise sources - Allow warning signals to exceed normal sound level by 15 dB, or any maximum sound level with a duration of 30 seconds by 5dB (with an upper limit of 120 dB) + A variety of complex tones, sounds, and speech should be used for displaying different types of information. - The set of sounds should be small and individual sounds should be easily discernable. [Use sounds that are distinct contrast to the environment] + Provide private or secure monitoring of audio display of private information by the user - Allow user to turn off the public audio presentation when private audio presentation is used. - Turn off speakers when headphone jack is inserted or handset is lifted from hook. + Strategies for Overcoming Major Usability Issues + Strategies for making spoken information easier to understand. - Use recorded speech or synthetic speech which is very clear and easy to understand.; - Provide methods for pausing, rewinding and repeating speech information (output) - Allow user to adjust speed and volume of speech. - Keep audible presentations short and simple - Begin any unexpected auditory presentation with an attention getting sound. + Strategies to ensure that messages important to operation are not missed - especially if not understood the first time. - Repeat messages periodically if no response is received from user (where response is prompted). For important auditory information, request acknowledgment from user. + Non-interference with hearing technologies. [Reduce interference to hearing technologies (including hearing aids, cochlear implants, and assistive listening devices) to the lowest possible level that allows a user to utilize the product. TAAG 11931.43 (h)] + Strategies for Providing Basic Access - Design product so that it does not create interference for hearing aids. + Hearing aid coupling. [Where a product delivers output by an audio transducer which is normally held up to the ear, provide a means for effective wireless coupling to hearing aids. TAAG 11931.43 (I)] + Strategies for Providing Basic Access - Provide inductive loop for direct coupling with hearing aids. - For product which are held up to the ear, provide enough electromagnetic leakage so that hearing aid T-coils can pick up the signal. 5.4.5 Operable with no hearing -------------------------------------------------- LIST ONE - GENERAL FACTORS FOR CREATING MORE ACCESSIBLE PRODUCTS NOTE: - SINCE THERE ARE OFTEN MULTIPLE WAYS TO ACHIEVE A FUNCTION, NOT ALL CONTROLS NEED TO BE ACCESSIBLE. JUST ENOUGH TO ALLOW THE PERSON TO BE ABLE TO OPERATE THE FULL FUNCTIONS OF THE PRODUCT. Operable without hearing. - Provide at least one mode that does not require user auditory perception. TAAG 1193.41 (d)] Providing Basic Access - providing non-aural notification of events, warnings, etc that usually occur auditorily - providing indication of control activation and operation - Incorporate text telephone functionality into device (public phones, etc) - See also: Operable without speech TAAG 1193.41(h)] Overcoming Major Usability Issues - keeping language demands low for non-native speakers when creating menus, labels, and documentation. Note: Many people who mainly communicate using sign language have difficulty with written text (English is a second language for American Sign language users). ----- Availability of auditory information. - Provide auditory information through at least one mode in visual form and, where appropriate, in tactile form. TAAG 1193.43 (d)] Providing Basic Access - presenting auditory information in visual and/or tactile forms. Overcoming Major Usability Issues - If speech accompanies video, (e.g. in multi-media telecommunications such as video phone), a channel and method could be provided for typing messages back and forth to accompany the visual image. - Incorporate text telephone functionality into device (public phones, etc) - Provide TTY users with appropriate visual prompt or messages for distinctive or unusual dial tones (i.e. stutter). Ensure that stutter is of sufficient length so that it can be detected even after the user picks up the handset, couples it to the TTY.] ------------------------------------- LIST TWO - POSSIBLE IDEAS AND STRATEGIES FOR INCREASING ACCESSIBILITY + Operable without hearing. [Provide at least one mode that does not require user auditory perception. TAAG 1193.41 (d)] + Strategies for Providing Basic Access + Strategies for providing non-aural notification of events, warnings, etc that usually occur auditorily + Use visual cues (flashing menus, highlights, status lights) or vibration (of a part of the product in contact with the user; i.e. pagers) in addition to audible tones to indicate events. + Provide visual or tactile information to inform the user of the status of a process (if progress is normal or not) that is usually determined through auditory means (e.g., line status on a phone call, disk drive being busy, etc.) - Provide visual feedback of the status of inserted objects - Provide portable remote visual or tactile indicator to alert the user when the appliance gives an auditory alert. (e.g. an oven or washer/dryer) - For warnings, provide a prominent visual indication in the field of vision. + All speech prods, confirmations, tones, etc., could be presented simultaneously in text form either as standard operating mode or at the option of the user - Provide a switch or setting that a user can turn on which will cause the product to provide visual indications of audible events including captions for spoken text (e.g., ShowSounds and SoundSentry). [Example] + Strategies for providing indication of control activation and operation + Provide graphical feedback to indicate activation. - Display touched area in reverse video or with thick outline to indicate activation - Provide an indicator light or message on display to indicate activation/confirmation. + Use a positive movement that can be felt to indicate activation. - Keys should comply with minimum travel distance so that it is obvious when they have been activated. - Use control position detents - On pushbuttons, toggle switches, and rotary controls there should be variable resistance that gradually builds up and then drops suddenly on activation. - Incorporate text telephone functionality into device (public phones, etc) - See also: Operable without speech [TAAG 1193.41(h)] + Strategies for Overcoming Major Usability Issues + Strategies for keeping language demands low for non-native speakers when creating menus, labels, and documentation. Note: Many people who mainly communicate using sign language have difficulty with written text (English is a second language for American Sign language users). - Keep language as simple as possible. - Restrict number of items in a menu, keeping prompts short and simple - Use goal/action structure for menu prompts - Use visual examples (diagrams, icons, drawings) in addition to text descriptions. ------ + Availability of auditory information. [Provide auditory information through at least one mode in visual form and, where appropriate, in tactile form. TAAG 1193.43 (d)] + Strategies for Providing Basic Access + Strategies for presenting auditory information in visual and/or tactile forms. + Use visual cues (flashing menus, highlights, status lights) or vibration (of a part of the product in contact with the user; i.e. pagers) in addition to audible tones to indicate events. - Provide portable remote visual or tactile indicator to alert the user when the appliance gives an auditory alert. (e.g. an oven or washer/dryer) - Provide visual or tactile information to inform the user of the status of a process (if progress is normal or not) that is usually determined through auditory means (e.g., line status on a phone call, disk drive being busy, etc.) + All speech prods, confirmations, tones, etc., could be presented simultaneously in text form either as standard operating mode or at the option of the user - Provide a switch or setting that a user can turn on which will cause the product to provide visual indications of audible events including captions for spoken text (e.g., ShowSounds and SoundSentry). [Example] + Provide captioning (closed and open) for all audiovisual components. - Pace captions to match reading speed. (Text should be displayed long enough to be read.) - Verbatim captioning is desirable + Strategies for Overcoming Major Usability Issues - If speech accompanies video, (e.g. in multi-media telecommunications such as video phone), a channel and method could be provided for typing messages back and forth to accompany the visual image. - Incorporate text telephone functionality into device (public phones, etc) - Provide TTY users with appropriate visual prompt or messages for distinctive or unusual dial tones (i.e. stutter). [Ensure that stutter is of sufficient length so that it can be detected even after the user picks up the handset, couples it to the TTY.] 5.4.6 Operable with low vision and limited or no hearing -------------------------------------------------- LIST ONE - GENERAL FACTORS FOR CREATING MORE ACCESSIBLE PRODUCTS NOTE: - SINCE THERE ARE OFTEN MULTIPLE WAYS TO ACHIEVE A FUNCTION, NOT ALL CONTROLS NEED TO BE ACCESSIBLE. JUST ENOUGH TO ALLOW THE PERSON TO BE ABLE TO OPERATE THE FULL FUNCTIONS OF THE PRODUCT. Operable with low vision and limited or no hearing. - Provide at least one mode that permits operation by users with visual acuity between 20/70 and 20/200, without relying on audio output. TAAG 1193.41 (b)] Providing Basic Access - ensuring that controls can be located (i.e. they are distinguishable from their surroundings) - ensuring that the surface of controls can be easily differentiated tactually from the main surface of a product. - ensuring that controls are visually locatable (i.e. distinguishable from their surroundings) - ensuring that controls can be identified - providing indication of settings or status of controls - providing indication of control activation and operation - See also: Operable without time-dependent controls. TAAG 1193.41(g)] Overcoming Major Usability Issues - assist in locating controls from memory or to simplify a search for a function - help differentiate controls - breaking up large groups of keys with landmarks. - narrowing or quickening the search for a function - facilitate connection or insertion of objects (connectors, media, plugs, jacks, cards, etc.) - ensure that messages important to operation are not missed - especially if not understood the first time. - Make all connectors and surfaces safe to explore by touch (electrically safe and free of sharp edges or hot surfaces) even if contact with body part is not normally expected. Other Increase Ease of Use - making control operation easier to understand. Operable with little or no color perception. - Provide at least one mode that does not require user color perception. TAAG 1193.41 (c)] Providing Basic Access - Provide stick-on labels, overlays, or recappable keys with large raised lettering, Braille, color, and/or customizable labels/keycaps as options. - ensure that information presented via color is perceivable ------- Availability of visual information for low vision users. - Provide visual information through at least one mode to users with visual acuity between 20/70 and 20/200 without relying on audio. TAAG 1193.43 (b)] Providing Basic Access - formatting visual information for maximum readability. - designing display hardware to enhance readability of information. - See also: Access to Moving Text. TAAG 1193.43(c)] Other Increase Ease of Use - Alternative forms of material include printed, large print, electronic format, audio tape, on-line, Braille, raised large print, captioned video, speech output (Note for computer systems: audio tape may be more useful than electronic documents if installation requires rebooting the computer) ------------------------------------- LIST TWO - POSSIBLE IDEAS AND STRATEGIES FOR INCREASING ACCESSIBILITY + Operable with low vision and limited or no hearing. [Provide at least one mode that permits operation by users with visual acuity between 20/70 and 20/200, without relying on audio output. TAAG 1193.41 (b)] + Strategies for Providing Basic Access + Strategies for ensuring that controls can be located (i.e. they are distinguishable from their surroundings) + Strategies for ensuring that the surface of controls can be easily differentiated tactually from the main surface of a product. - Make sure the tactile cues and differences are sufficient to detect. Diameter changes of at least 3/8 inch and thickness changes of at least 1/32 inch are most readily detectable by people who are blind. - Use buttons that are raised or have a raised feature such as an embossed dot or icon. - Use buttons which are slightly dished, recessed or contained within a raised boundary. If using a flat touch panel, provide a raised ridge around the edge of control areas. + Strategies for ensuring that controls are visually locatable (i.e. distinguishable from their surroundings) - Contrast keys with their background; either light controls on dark background or dark controls on light background. Light controls on dark background are preferred with contrast ratio of 6:1 or greater. + Use color coding or other visual demarcation of edges of keys - Avoid colors with low luminance. - Avoid using the blues, greens and violets for color coding information - Use large and/or blinking cursors (enable user to adjust size and blink rate) - Use graphic trail for cursor/pointer + Optimize location of controls, components, displays, and output for reach and sight from various approach conditions and heights (standing/walker, wheelchair, etc) with minimum changes in body position. ( 36-48" from floor) - Avoid placing controls where the user has to lean or look in the back in order to see or use them. + Strategies for ensuring that controls can be identified + Format visual labels to enhance readability. - Increase the size of labels -- Make labels as large as possible to enhance readability - Make characters as large as possible. - Use simple typeface (sans serif). - Provide adequate spacing between letters, words, and lines - Avoid airbrushed effects - Use upper and lower case letters for maximum readability. - Use Arabic instead of Roman Numerals + Use high-contrast between text or graphics and background. - For maximum contrast provide option for white or light yellow symbols or letters over black background (e.g. High Contrast Setting) + Provide large, raised lettering &/or Braille labels. (NOTE: Braille alone is not sufficient for a majority of people who are blind) - Make sure the tactile cues and differences are sufficient to detect. Diameter changes of at least 3/8 inch and thickness changes of at least 1/32 inch are most readily detectable by people who are blind. - Use universally recognizable tactile shapes for controls or labels - Follow stereotypes and common conventions for color codes and symbols. + Provide stick-on labels, overlays, or recappable keys with large raised lettering, Braille, color, and/or customizable labels/keycaps as options. - Leave adequate space around and between keys and controls for adaptive levers, special labels (e.g. Braille), for grasping, and accidental activation avoidance + Label the product and its controls clearly so that the user can tell what is being controlled - Locate labels on or close to controls with clear markings to indicate correspondence - Provide adequate illumination + Use color coding (Always in combination with other cues such as size, shape, or texture.) - Avoid colors with low luminance. - Avoid using the blues, greens and violets for color coding information - Allow the user to adjust colors. + Strategies for providing indication of settings or status of controls + Provide tactile indication of control status or settings through position or orientation of the control - Provide tactile markings, which allow determination of the setting. - Use switches which have tactilely discernable states (e.g., toggle or rocker switch versus push-on/push-off or a push-on/push-off switch which has distinctly different heights in the on and off state). + Use absolute reference controls (e.g. knobs with pointers) rather than relative controls (e.g. increase/decrease buttons; round or unmarked knobs) - Shape a control so that its setting can be tactilely read (e.g., a twist knob shaped like a pie wedge) - Use moving pointers and stationary scales for adjustments and settings + Provide concrete rather than abstract indicators (e.g. a visual, graphic indicator rather than a numeric one) - Provide simple progress indicator [e.g. half full, full, busy, wrong choice] + Strategies for providing indication of control activation and operation + Use a positive movement that can be felt to indicate activation. - Keys should comply with minimum travel distance so that it is obvious when they have been activated. - Use control position detents - On pushbuttons, toggle switches, and rotary controls there should be variable resistance that gradually builds up and then drops suddenly on activation. + Provide graphical feedback to indicate activation. - Display touched area in reverse video or with thick outline to indicate activation - See also: Operable without time-dependent controls. [TAAG 1193.41(g)] + Strategies for Overcoming Major Usability Issues + Strategies to assist in locating controls from memory or to simplify a search for a function + Strategies to help differentiate controls - Use texture on buttons that have important or unusual functions. - Use varying sizes, shapes, and textures for controls. - Use BOTH color and shape coding to distinguish similar parts or controls + Use color coding (Always in combination with other cues such as size, shape, or texture.) - Avoid colors with low luminance. - Avoid using the blues, greens and violets for color coding information + Strategies for breaking up large groups of keys with landmarks. + Provide tactile markings or reference points on keyboards/pads - Use nibs on the F and J keys of standard QWERTY keyboards - Use nibs on the 5 key of a number pad. - No key or control should be more than 1 away from a tactile landmark (corner, uniquely shaped control, nibbed key, home key) - Group or delineate associated controls, displays, labels, etc. with raised lines, boxes, colors, spacing, texture, shape and/or similar means. + Strategies for narrowing or quickening the search for a function - Layer controls and menus by frequency of use (priority). Hide/shield infrequently used controls, although it must be easy to "unhide" them when needed. - Arrange controls in order of sequence of operation - Cluster controls of similar functions + Strategies to facilitate connection or insertion of objects (connectors, media, plugs, jacks, cards, etc.) - Locate frequently used controls, slots, etc where users have direct visual access and where they can be easily reached with minimal change in body position. (at the front) + Ensure that an object cannot be inserted improperly. + Provide unique connector/jack combinations - Use BOTH color and shape coding to distinguish similar parts or controls - Tactually mark identity and orientation (if not self- orienting nor orientation independent) of object (connectors, media, etc). There should be obvious tactile target for insertion. - Visually mark identity and orientation (if not self- orienting nor orientation independent) of object (connectors, media, etc). There should be visual contrast to emphasize where an object can be inserted. + Strategies to ensure that messages important to operation are not missed - especially if not understood the first time. - Emphasize priority information, key words or phrases, and special warnings with underlines, bold, boxes, graphics or icons, different type fonts, colors etc. - For warnings, provide a prominent visual indication in the field of vision. - Make all connectors and surfaces safe to explore by touch (electrically safe and free of sharp edges or hot surfaces) even if contact with body part is not normally expected. + Other Strategies to Increase Ease of Use + Strategies for making control operation easier to understand. - Use simple screen layouts or one thing at a time presentations - Use sequential numbers for numbered menus/lists - Tab in a logical and consistent manner among objects - Put most important information at the beginning of text - [especially if short spoken information such as lists] + Operable with little or no color perception. [Provide at least one mode that does not require user color perception. TAAG 1193.41 (c)] + Strategies for Providing Basic Access - Provide stick-on labels, overlays, or recappable keys with large raised lettering, Braille, color, and/or customizable labels/keycaps as options. + Strategies to ensure that information presented via color is perceivable + Use different hues and intensities of color so that "colors" can be easily differentiated from each other even on a black and white screen, display, or photograph. - Use high-contrast between text or graphics and background. + Avoid color combinations which cause color confusion.; - Avoid using the blues, greens and violets for color coding information - Use BOTH color and shape coding to distinguish similar parts or controls - Allow the user to adjust colors. ------ + Availability of visual information for low vision users. [Provide visual information through at least one mode to users with visual acuity between 20/70 and 20/200 without relying on audio. TAAG 1193.43 (b)] + Strategies for Providing Basic Access + Strategies for formatting visual information for maximum readability. + Use high-contrast between text or graphics and background. - For maximum contrast provide option for white or light yellow symbols or letters over black background (e.g. High Contrast Setting) - Avoid colors with low luminance. - Allow the user to adjust colors. - Avoid using the blues, greens and violets for color coding information - Make characters as large as possible. - Use simple typeface (sans serif). - Use upper and lower case letters for maximum readability. - Use Arabic instead of Roman Numerals - Provide adequate spacing between letters, words, and lines - Use sequential numbers for numbered menus/lists - Supplement graphic information with non visual forms or modes - Use simple screen layouts or one thing at a time presentations - Follow stereotypes and common conventions for color codes and symbols. - When combining text with titles (or labels), use sans serif or bold type to clearly distinguish labels/titles from common text. Only one or two different typefaces should be used for emphasis. + Highlight key information. Only one or two different typefaces should be used for emphasis. - Put most important information at the beginning of text - [especially if short spoken information such as lists] - Emphasize priority information, key words or phrases, and special warnings with underlines, bold, boxes, graphics or icons, different type fonts, colors etc. + Strategies for designing display hardware to enhance readability of information. - Use LED displays when possible for maximum contrast - Allow the user to adjust colors. + Provide brightness and contrast adjustment - Provide means for adjusting viewing angle of LCD displays + Minimize glare on display screens or other display or warning surfaces - Provide easy adjustment to visual displays including height, tilt, swivel. (angle) - Provide means for adjusting viewing angle of LCD displays - Use filtering devices - Use non-reflective surfaces - Provide zoom or other means for enlarging image/text on the display - Provide adequate illumination - Leave important visual messages or warnings on display until confirmed by user. - See also: Access to Moving Text. [TAAG 1193.43(c)] + Other Strategies to Increase Ease of Use + Alternative forms of material include printed, large print, electronic format, audio tape, on-line, Braille, raised large print, captioned video, speech output (Note for computer systems: audio tape may be more useful than electronic documents if installation requires rebooting the computer) - Design printed documentation to be "scanner/OCR friendly" 5.4.7 Operable without vision -------------------------------------------------- LIST ONE - GENERAL FACTORS FOR CREATING MORE ACCESSIBLE PRODUCTS NOTE: - SINCE THERE ARE OFTEN MULTIPLE WAYS TO ACHIEVE A FUNCTION, NOT ALL CONTROLS NEED TO BE ACCESSIBLE. JUST ENOUGH TO ALLOW THE PERSON TO BE ABLE TO OPERATE THE FULL FUNCTIONS OF THE PRODUCT. Operable without vision. - Provide at least one mode that does not require user vision. TAAG 1193.41(a)] Providing Basic Access - ensuring that controls can be located (i.e. they are distinguishable from their surroundings) - ensuring that the surface of controls can be easily differentiated tactually from the main surface of a product. - ensuring that controls can be identified - providing indication of settings or status of controls - providing indication of control activation and operation - providing alternatives for functions and controls that require eye-hand coordination (e.g. mouse, ). - avoiding hazardous situations See also: reduce accidental activation of controls and help ensure that the desired control is activated instead. Overcoming Major Usability Issues - assist in locating controls from memory or to simplify a search for a function - breaking up large groups of keys with landmarks. - help differentiate controls - narrowing or quickening the search for a function - reduce accidental activation of controls and help to ensure that the desired control is activated instead. - facilitate connection or insertion of objects (connectors, media, plugs, jacks, cards, etc.) - Use wireless connection strategies that eliminate the need to orient or insert connectors, plugs, jacks, cards, etc.; (i.e. Infrared). - ensure that messages important to operation are not missed - especially if not understood the first time. - keep materials usable over time Other Increase Ease of Use - making spoken information easier to understand. - making control operation easier to understand. - help ensure that the product is accessible "out of the box." (that the user does not have to have someone else set- up, start-up, adjust timing parameters, etc to make it usable) - prevent the loss of loose components of a product. ------ Availability of visual information. - Provide visual information through at least one mode in auditory form. TAAG 1193.43 (a)] Providing Basic Access - presenting visual information in auditory and/or tactile forms. Overcoming Major Usability Issues - ensure that messages important to operation are not missed - especially if not understood the first time. - Put most important information at the beginning of text - especially if short spoken information such as lists] - making spoken information easier to understand. - Provide private or secure monitoring of audio display of private information by the user Other Increase Ease of Use - making it easier to hear auditory output ------------------------------------- LIST TWO - POSSIBLE IDEAS AND STRATEGIES FOR INCREASING ACCESSIBILITY + Operable without vision. [Provide at least one mode that does not require user vision. TAAG 1193.41(a)] + Strategies for Providing Basic Access + Strategies for ensuring that controls can be located (i.e. they are distinguishable from their surroundings) + Strategies for ensuring that the surface of controls can be easily differentiated tactually from the main surface of a product. - Use buttons which are slightly dished, recessed or contained within a raised boundary. If using a flat touch panel, provide a raised ridge around the edge of control areas. - Use buttons that are raised or have a raised feature such as an embossed dot or icon. - Make sure the tactile cues and differences are sufficient to detect. Diameter changes of at least 3/8 inch and thickness changes of at least 1/32 inch are most readily detectable by people who are blind. - Make controls on touchscreens auditorally differentiable (or keyboard operable). + Make the product entirely usable and adjustable from the keyboard - Follow GUI guidelines for keyboard equivalents of standard functions - Use TAB or arrow keys to move between options on the screen + Strategies for ensuring that controls can be identified + Provide large, raised lettering &/or Braille labels. (NOTE: Braille alone is not sufficient for a majority of people who are blind) - Make sure the tactile cues and differences are sufficient to detect. Diameter changes of at least 3/8 inch and thickness changes of at least 1/32 inch are most readily detectable by people who are blind. + Provide stick-on labels, overlays, or recappable keys with large raised lettering, Braille, color, and/or customizable labels/keycaps as options. - Leave adequate space around and between keys and controls for adaptive levers, special labels (e.g. Braille), for grasping, and accidental activation avoidance - Use universally recognizable tactile shapes for controls or labels + Use voice output to identify controls - Provide an optional mode which announces keys when pressed but does not activate them. [Example] - Provide a mode where keys are announced when pressed but only activated if they are held down for a (user adjustable) period of time. - Provide audio directions to the locations of controls. - Provide Braille directions to the locations of controls. + Strategies for providing indication of settings or status of controls + Provide audible cues to announce or confirm settings or status of controls - Provide tones to indicate status (e.g. ToggleKeys), - Provide clicks in conjunction with a hard stop (e.g. go to zero and forward 3 clicks) - Provide Speech output to announce settings + Provide tactile indication of control status or settings through position or orientation of the control + Use switches which have tactilely discernable states (e.g., toggle or rocker switch versus push-on/push-off or a push-on/push-off switch which has distinctly different heights in the on and off state). - A button that is not depressed should indicate an off condition while a depressed pushbutton should indicate an on condition + Use absolute reference controls (e.g. knobs with pointers) rather than relative controls (e.g. increase/decrease buttons; round or unmarked knobs) - Shape a control so that its setting can be tactilely read (e.g., a twist knob shaped like a pie wedge) - Provide tactile markings, which allow determination of the setting. - Use moving pointers and stationary scales for adjustments and settings + Strategies for providing indication of control activation and operation - Provide audible click or tone to indicate activation + Use a positive movement that can be felt to indicate activation. - On pushbuttons, toggle switches, and rotary controls there should be variable resistance that gradually builds up and then drops suddenly on activation. - Keys should comply with minimum travel distance so that it is obvious when they have been activated. - Use control position detents + Strategies for providing alternatives for functions and controls that require eye-hand coordination (e.g. mouse, ). + Make the product entirely usable and adjustable from the keyboard - Follow GUI guidelines for keyboard equivalents of standard functions - Use TAB or arrow keys to move between options on the screen - Support speech input/voice recognition to activate functions and as alternatives to typing, dialing, and using keyboards or mouse. + Strategies for avoiding hazardous situations - Eliminate or audibly warn of visually obvious hazards - Provide automatic timed shut-off for devices that might cause a hazard if left on. - Make all connectors and surfaces safe to explore by touch (electrically safe and free of sharp edges or hot surfaces) even if contact with body part is not normally expected. - See also: Strategies to reduce accidental activation of controls and help ensure that the desired control is activated instead. + Strategies for Overcoming Major Usability Issues + Strategies to assist in locating controls from memory or to simplify a search for a function + Strategies for breaking up large groups of keys with landmarks. - Group or delineate associated controls, displays, labels, etc. with raised lines, boxes, colors, spacing, texture, shape and/or similar means. + Provide tactile markings or reference points on keyboards/pads - Use nibs on the F and J keys of standard QWERTY keyboards - Use nibs on the 5 key of a number pad. - No key or control should be more than 1 away from a tactile landmark (corner, uniquely shaped control, nibbed key, home key) + Strategies to help differentiate controls - Use varying sizes, shapes, and textures for controls. - Use texture on buttons that have important or unusual functions. - Use BOTH color and shape coding to distinguish similar parts or controls + Strategies for narrowing or quickening the search for a function - Locate controls adjacent to what they control, in logical or corresponding layout. - Cluster controls of similar functions - Arrange controls in order of sequence of operation - Layer controls and menus by frequency of use (priority). Hide/shield infrequently used controls, although it must be easy to "unhide" them when needed. + Strategies to reduce accidental activation of controls and help to ensure that the desired control is activated instead. - Use a two step "select and confirm" to reduce accidental selections (esp. for critical or non reversible functions). + Provide physical guards to make accidental activation more difficult. - Provide physical key-guards for keyboards or keypads. - Recess or provide guard bars between buttons. - Provide switch guards, especially for critical switches. - Avoid buttons or controls that are activated as soon as they are touched (unless there is a touch and confirm option) - Leave adequate space around and between keys and controls for adaptive levers, special labels (e.g. Braille), for grasping, and accidental activation avoidance - Allow key repeat functions to be adjusted over a wide range and / or to be turned off (a.k.a. RepeatKeys). - Increase the force needed to activate critical or dangerous controls - Provide a lockout for critical or dangerous controls - Provide the ability to cancel an input, undo an operation or otherwise "back up." - Provide a mode where keys are announced when pressed but only activated if they are held down for a (user adjustable) period of time. + Strategies to facilitate connection or insertion of objects (connectors, media, plugs, jacks, cards, etc.) - Use orientation independent objects, connectors and media receptacles. + Provide simple self-guiding/orienting features for insertion of objects. - Bevel (or funnel) opening to facilitate insertion of objects. + Ensure that an object cannot be inserted improperly. + Provide unique connector/jack combinations - Use BOTH color and shape coding to distinguish similar parts or controls - Tactually mark identity and orientation (if not self- orienting nor orientation independent) of object (connectors, media, etc). There should be obvious tactile target for insertion. - Use wireless connection strategies that eliminate the need to orient or insert connectors, plugs, jacks, cards, etc.; (i.e. Infrared). + Strategies to ensure that messages important to operation are not missed - especially if not understood the first time. - Repeat messages periodically if no response is received from user (where response is prompted). For important auditory information, request acknowledgment from user. + Strategies to keep materials usable over time - Choose Materials that resist aging, wear, and vandalism. Example: The bubbling and expanding of non-heat resistive surfaces can destroy the tactile nature of the Braille labels, making them unintelligible to the blind user. + Other Strategies to Increase Ease of Use + Strategies for making spoken information easier to understand. - Allow user to adjust speed and volume of speech. - Keep audible presentations short and simple - Begin any unexpected auditory presentation with an attention getting sound. - Use sequential numbers for numbered menus/lists - Maximize signal to noise ratio of speech in environment. + Strategies for making control operation easier to understand. - Tab in a logical and consistent manner among objects - Use standard, simple layouts for controls. - Match the direction of movement of the control in a logical way with the function of the control and/or use standard conventions for controlled direction (e.g., clockwise increases). i.e. Follow movement stereotypes; - Put most important information at the beginning of text - [especially if short spoken information such as lists] - Use sequential numbers for numbered menus/lists + Strategies to help ensure that the product is accessible "out of the box." (that the user does not have to have someone else set-up, start-up, adjust timing parameters, etc... to make it usable) - Minimize and simplify mechanical assembly and set-up - Mark identity and orientation of objects needing assembly + Strategies to prevent the loss of loose components of a product. - Covers, lids, doors and other loose components should be hinged, tethered, or otherwise connected to the product ----- + Availability of visual information. [Provide visual information through at least one mode in auditory form. TAAG 1193.43 (a)] + Strategies for Providing Basic Access + Strategies for presenting visual information in auditory and/or tactile forms. - Provide speech output of information. [Example] - Supplement graphic information with non visual forms or modes - Provide audio descriptions (e.g. descriptive video) for video. [Example] - Provide verbal descriptions of the appearance, functionality and purpose of more complex displays where this information is available to sighted viewers by the graphic layout and visual techniques used on the visual displays. - Use Auditory Icons for auditory redundancy in graphic user interfaces (e.g. Sonic Finder, Finder Sounds) + Strategies for Overcoming Major Usability Issues + Strategies to ensure that messages important to operation are not missed - especially if not understood the first time. - Repeat messages periodically if no response is received from user (where response is prompted). For important auditory information, request acknowledgment from user. - Put most important information at the beginning of text - [especially if short spoken information such as lists] + Strategies for making spoken information easier to understand. - Provide methods for pausing, rewinding and repeating speech information (output) - Allow user to adjust speed and volume of speech. - Keep audible presentations short and simple - Begin any unexpected auditory presentation with an attention getting sound. - Use sequential numbers for numbered menus/lists - Maximize signal to noise ratio of speech in environment. + Provide private or secure monitoring of audio display of private information by the user - Allow user to turn off the public audio presentation when private audio presentation is used. - Turn off speakers when headphone jack is inserted or handset is lifted from hook. + Other Strategies to Increase Ease of Use + Strategies for making it easier to hear auditory output - See also: Availability of auditory information for people who are hard of hearing [TAAG 1193.43(e)] 5.4.8 Operable with limited cognitive skills -------------------------------------------------- LIST ONE - GENERAL FACTORS FOR CREATING MORE ACCESSIBLE PRODUCTS NOTE: - SINCE THERE ARE OFTEN MULTIPLE WAYS TO ACHIEVE A FUNCTION, NOT ALL CONTROLS NEED TO BE ACCESSIBLE. JUST ENOUGH TO ALLOW THE PERSON TO BE ABLE TO OPERATE THE FULL FUNCTIONS OF THE PRODUCT. Operable with limited cognitive skills. - Provide at least one mode that minimizes the cognitive, memory, language, and learning skills required of the user. TAAG 1193.41 (I)] Providing Basic Access - reduce reliance on memory. - eliminating difficulties associated with remembering the correct sequence of operation. - avoiding functions that require simultaneous actions to activate or operate. (e.g. requires two hands to open, or multiple finger operations). - facilitate entry of information or commands. - ensuring that information is understood - making text (either visual or auditory) information easier to understand. - making spoken information easier to understand. - making visual information easier to understand - ensuring that controls can be identified - making control operation easier to understand. - avoiding hazardous situations - See also: Operable without time-dependent controls. TAAG 1193.41(g)] Overcoming Major Usability Issues - reduce accidental activation of controls and help to ensure that the desired control is activated instead. - assist in locating controls from memory or to simplify a search for a function - breaking up large groups of keys with landmarks. - narrowing or quickening the search for a function - reduce the number of controls. - providing indication of control activation and operation - making settings or status of controls easier to understand - ensure that messages important to operation are not missed - especially if not understood the first time. - facilitate connection or insertion of objects (connectors, media, plugs, jacks, cards, etc.) - Use wireless connection strategies that eliminate the need to orient or insert connectors, plugs, jacks, cards, etc.; (i.e. Infrared). Other Increase Ease of Use - Reduce system lag or response time - Provide defaults, and an easy way to re-establish defaults. - Avoid color combinations which cause color confusion.; - Use color coding or other visual demarcation of edges of keys - Contrast keys with their background; either light controls on dark background or dark controls on light background. Light controls on dark background are preferred with contrast ratio of 6:1 or greater. - Gain should be adjustable for both coarse and fine movement of pointing devices. - help ensure that the product is accessible "out of the box." (that the user does not have to have someone else set- up, start-up, adjust timing parameters, etc_ to make it usable) ------------------------------------- LIST TWO - POSSIBLE IDEAS AND STRATEGIES FOR INCREASING ACCESSIBILITY + Operable with limited cognitive skills. [Provide at least one mode that minimizes the cognitive, memory, language, and learning skills required of the user. TAAG 1193.41 (I)] + Strategies for Providing Basic Access + Strategies to reduce reliance on memory. + Strategies for eliminating difficulties associated with remembering the correct sequence of operation. + Eliminate Sequences - Use smart cards to reduce need to memorize access sequences and/or provide customization automatically - Provide programmable macros or shortcuts for frequently used sequences of actions . (i.e. speed dial) + Reduce the length of sequences. - Minimize the number of steps needed for operations, if possible, to a single non-time-dependent step. + Provide cues for sequences - Provide simple step-by-step operating instructions. - Arrange controls in order of sequence of operation - Provide instructions and information using numbered, bulleted or checklist steps - Provide short prompts (and instructions) for required sequences and for error resolution. - Tab in a logical and consistent manner among objects - Provide important instructions on the device as well as in documentation. - Provide quick reference cards for essential features - Provide an easy and clear exit to return to the starting point from any point in the system + Strategies for avoiding functions that require simultaneous actions to activate or operate. (e.g. requires two hands to open, or multiple finger operations). - Do not require triple-clicking or the use of SHIFT and ALT to modify mouse clicks (Use only if alternative is available). - Avoid complex manipulations (such as pushing & rotating, grasping & pulling, grasping & twisting, pinching & twisting, etc) or provide alternatives. - Avoid dual latches/handles that require simultaneous activation. + Strategies to facilitate entry of information or commands. - Utilize choose from list feature. + Reduce the number of choices. - Restrict number of items in a menu, keeping prompts short and simple - Provide examples and cues for length and format when entering data into fields. - Automate procedures. - Provide ability to get help + Strategies for ensuring that information is understood - Provide speech output of information. [Example] + Strategies for making text (either visual or auditory) information easier to understand. + Keep language as simple as possible. - Avoid abbreviations, acronyms, and hyphenations in labels, instructions, or information presentation. If acronyms or abbreviations are necessary, use only ones that are well- known to the user population. - Highlight key information. Only one or two different typefaces should be used for emphasis. - Allow users to proceed at their own pace. - Allow user to back up and repeat earlier information. + Strategies for making spoken information easier to understand. - Provide methods for pausing, rewinding and repeating speech information (output) - Keep audible presentations short and simple - Begin any unexpected auditory presentation with an attention getting sound. - Allow user to adjust speed and volume of speech. - Use sequential numbers for numbered menus/lists - Maximize signal to noise ratio of speech in environment. + Strategies for making visual information easier to understand - Use digits for numerical info, and graphics for qualitative values (e.g. half full, full) - Use simple screen layouts or one thing at a time presentations - Use visual examples (diagrams, icons, drawings) in addition to text descriptions. - Pace captions to match reading speed. (Text should be displayed long enough to be read.) - See also: Access to Moving Text. [TAAG 1193.43(c)] + Strategies for ensuring that controls can be identified + Use multiple methods to allow user to identify and locate a control. - Use varying sizes, shapes, and textures for controls. - Use universally recognizable tactile shapes for controls or labels - Use color coding (Always in combination with other cues such as size, shape, or texture.) - Follow stereotypes and common conventions for color codes and symbols. - Provide audio directions to the locations of controls. + Use voice output to identify controls - Provide a mode where keys are announced when pressed but only activated if they are held down for a (user adjustable) period of time. - Provide an optional mode which announces keys when pressed but does not activate them. [Example] + Label the product and its controls clearly so that the user can tell what is being controlled - Locate labels on or close to controls with clear markings to indicate correspondence + Format visual labels to enhance readability. - Use Arabic instead of Roman Numerals - Use high-contrast between text or graphics and background. - Use upper and lower case letters for maximum readability. + Provide stick-on labels, overlays, or recappable keys with large raised lettering, Braille, color, and/or customizable labels/keycaps as options. - Leave adequate space around and between keys and controls for adaptive levers, special labels (e.g. Braille), for grasping, and accidental activation avoidance + Strategies for making control operation easier to understand. - Match the direction of movement of the control in a logical way with the function of the control and/or use standard conventions for controlled direction (e.g., clockwise increases). i.e. Follow movement stereotypes; - Use standard, simple layouts for controls. - Use simple screen layouts or one thing at a time presentations - Tab in a logical and consistent manner among objects - Use goal/action structure for menu prompts - Use sequential numbers for numbered menus/lists - If an icon appears with text beneath it, clicking on the text should cause the same effect as clicking on the icon. This is particularly true when the icon is a single-click activated button. [An exception to this is when the icon is already selected and a second single-click causes the text below it to be editable while clicking on the icon itself may do nothing.] - Simplify operations; avoiding dual purpose or ambiguous controls - Avoid gang mounted controls (unless alternate mode of activation is provided). + Strategies for avoiding hazardous situations - Provide automatic timed shut-off for devices that might cause a hazard if left on. - See also: Operable without time-dependent controls. [TAAG 1193.41(g)] + Strategies for Overcoming Major Usability Issues + Strategies to reduce accidental activation of controls and help to ensure that the desired control is activated instead. - Avoid gang mounted controls (unless alternate mode of activation is provided). - Use a two step "select and confirm" to reduce accidental selections (esp. for critical or non reversible functions). - Provide ability to playback, erase, and rerecord voice messages, or edit speech input before activating speech operated control (i.e. dialing) - Provide the ability to cancel an input, undo an operation or otherwise "back up." - Provide a mode where keys are announced when pressed but only activated if they are held down for a (user adjustable) period of time. - Leave adequate space around and between keys and controls for adaptive levers, special labels (e.g. Braille), for grasping, and accidental activation avoidance + Strategies to assist in locating controls from memory or to simplify a search for a function + Strategies for breaking up large groups of keys with landmarks. - Group or delineate associated controls, displays, labels, etc. with raised lines, boxes, colors, spacing, texture, shape and/or similar means. + Strategies for narrowing or quickening the search for a function - Layer controls and menus by frequency of use (priority). Hide/shield infrequently used controls, although it must be easy to "unhide" them when needed. - Locate controls adjacent to what they control, in logical or corresponding layout. - Arrange controls in order of sequence of operation - Cluster controls of similar functions + Strategies to reduce the number of controls. - Layer controls and menus by frequency of use (priority). Hide/shield infrequently used controls, although it must be easy to "unhide" them when needed. - Minimize the number of steps needed for operations, if possible, to a single non-time-dependent step. - Make the product self adjusting + Strategies for providing indication of control activation and operation - Provide definite feedback cues + Provide graphical feedback to indicate activation. - Display touched area in reverse video or with thick outline to indicate activation + Use a positive movement that can be felt to indicate activation. - Keys should comply with minimum travel distance so that it is obvious when they have been activated. - On pushbuttons, toggle switches, and rotary controls there should be variable resistance that gradually builds up and then drops suddenly on activation. - Provide an indicator light or message on display to indicate activation/confirmation. + Strategies for making settings or status of controls easier to understand - Use visual/audio cues to indicate the completion of operation - Provide visual feedback of the status of inserted objects + Provide concrete rather than abstract indicators (e.g. a visual, graphic indicator rather than a numeric one) - Provide simple progress indicator [e.g. half full, full, busy, wrong choice] - Use absolute reference controls (e.g. knobs with pointers) rather than relative controls (e.g. increase/decrease buttons; round or unmarked knobs) - Use moving pointers and stationary scales for adjustments and settings - A button that is not depressed should indicate an off condition while a depressed pushbutton should indicate an on condition + Strategies to ensure that messages important to operation are not missed - especially if not understood the first time. - Repeat messages periodically if no response is received from user (where response is prompted). For important auditory information, request acknowledgment from user. - Emphasize priority information, key words or phrases, and special warnings with underlines, bold, boxes, graphics or icons, different type fonts, colors etc. + Strategies to facilitate connection or insertion of objects (connectors, media, plugs, jacks, cards, etc.) - Specify whether object should be fully inserted or dipped briefly. - Use orientation independent objects, connectors and media receptacles. - Use wireless connection strategies that eliminate the need to orient or insert connectors, plugs, jacks, cards, etc.; (i.e. Infrared). - Tactually mark identity and orientation (if not self- orienting nor orientation independent) of object (connectors, media, etc). There should be obvious tactile target for insertion. - Visually mark identity and orientation (if not self- orienting nor orientation independent) of object (connectors, media, etc). There should be visual contrast to emphasize where an object can be inserted. + Ensure that an object cannot be inserted improperly. + Provide unique connector/jack combinations - Use BOTH color and shape coding to distinguish similar parts or controls + Provide simple self-guiding/orienting features for insertion of objects. - Bevel (or funnel) opening to facilitate insertion of objects. - Locate frequently used controls, slots, etc where users have direct visual access and where they can be easily reached with minimal change in body position. (at the front) + Other Strategies to Increase Ease of Use - Reduce system lag or response time - Provide defaults, and an easy way to re-establish defaults. - Avoid color combinations which cause color confusion.; - Use color coding or other visual demarcation of edges of keys - Contrast keys with their background; either light controls on dark background or dark controls on light background. Light controls on dark background are preferred with contrast ratio of 6:1 or greater. - Gain should be adjustable for both coarse and fine movement of pointing devices. + Strategies to help ensure that the product is accessible "out of the box." (that the user does not have to have someone else set-up, start-up, adjust timing parameters, etc... to make it usable) - Minimize and simplify mechanical assembly and set-up - Mark identity and orientation of objects needing assembly 5.4.9 Operable without time-dependent controls -------------------------------------------------- LIST ONE - GENERAL FACTORS FOR CREATING MORE ACCESSIBLE PRODUCTS NOTE: - SINCE THERE ARE OFTEN MULTIPLE WAYS TO ACHIEVE A FUNCTION, NOT ALL CONTROLS NEED TO BE ACCESSIBLE. JUST ENOUGH TO ALLOW THE PERSON TO BE ABLE TO OPERATE THE FULL FUNCTIONS OF THE PRODUCT. Operable without time-dependent controls. - Provide at least one mode that does not require a response time. Alternatively, a response time may be required if it can be by-passed or adjusted by the user over a wide range. TAAG 1193.41 (g)] Providing Basic Access - minimizing difficulties arising from timed responses and time limited actions. - dealing with information which is only temporally presented Access to moving text. - Provide moving text in at least one static presentation mode at the option of the user. TAAG 1193.43 (c)] Providing Basic Access - reducing difficulties associated with moving or dynamic text ------------------------------------- LIST TWO - POSSIBLE IDEAS AND STRATEGIES FOR INCREASING ACCESSIBILITY + Operable without time-dependent controls. [Provide at least one mode that does not require a response time. Alternatively, a response time may be required if it can be by-passed or adjusted by the user over a wide range. TAAG 1193.41 (g)] + Strategies for Providing Basic Access + Strategies for minimizing difficulties arising from timed responses and time limited actions. - Allow users to proceed at their own pace. - If product requires a quick response (a reaction time of < 5 seconds or the release of a key in < 2 seconds) allow the user to adjust the time interval or provide a non time dependent alternative. + Ensure that time-outs are long enough to accommodate users who may need extra time. - Set all time limitations to very high values. - Warn the user when time is running out and allow them to secure extended time. - Provide the ability to cancel an input, undo an operation or otherwise "back up." + Strategies for dealing with information which is only temporally presented - Leave important visual messages or warnings on display until confirmed by user. - Provide an alternative to animated icons or animated menus that require users to respond as they change. - Avoid or provide alternative to animations that present information (e.g. scrolling or marquee text ) - Provide means for adjusting speed on dynamic displays and animations or allow the user to control the motion. ----- + Access to moving text. [Provide moving text in at least one static presentation mode at the option of the user. TAAG 1193.43 (c)] + Strategies for Providing Basic Access + Strategies for reducing difficulties associated with moving or dynamic text - Avoid or provide alternative to animations that present information (e.g. scrolling or marquee text ) - Provide an alternative to animated icons or animated menus that require users to respond as they change. - Provide means for adjusting speed on dynamic displays and animations or allow the user to control the motion. - Pace captions to match reading speed. (Text should be displayed long enough to be read.) 5.5. Proposed Family Standards: Setup & Installation 5.5.1. Draft standard, including maintenance & operation [Bill Sahlberg] Setup and Installation Standards Group As of 1/31/99 Narrative: The setup and installation standards group has been charged with drafting setup and installation standards of accessibility for use with computer and information technology as defined by the EITAAC committee. Questions, comments can be directed to group members: Bill Sahlberg, Curtis Chong, Gus Estrella, Joe Roeder, Janina Sajka, Susan Stillwell. General:1. Packaging: External and internal packaging should be removable with one hand. 2. Cables: Cables should be tactilely labeled or keyed for corresponding connections (which are also tactilely labeled). 3. Equipment port/cable connection labeling: Port, cable connection will be labeled with icons containing a clear area and size as described in 1193.51 Appendix 4.30.4 . 4. Documentation: (a) Manufacturers shall ensure access to information and documentation it provides to its customers. Such information and documentation includes user guides, installation guides for end-user installable devices, and product support communications, regarding both the product in general and the accessibility features of the products. Manufacturers shall take such other steps as necessary including: (1) Providing a description of the accessibility and compatibility features of the product upon request, including, as needed, in alternate formats or alternate modes at not additional charge (2) Providing end-user product documentation in alternate formats or alternate modes upon request at no additional charge (3) Ensuring usable customer support and technical support in the call centers and service centers which support their products at no additional charge. (b) Manufacturers shall include in general product information the contact method for obtaining the information required by paragraph (a) of this section. (c) Where manufacturers provide employee training, they shall ensure it is appropriate to an employee's function. In developing, or incorporating existing training programs, consideration shall be given to the following factors: (1) Accessibility requirements of individuals with disabilities (2) Means of communicating with individuals with disabilities (3) Commonly used adaptive technology used with the manufacturer's products (4) Designing for accessibility (5) Solutions for accessibility and compatibility (d) Readouts (LCDs): Information displayed on readouts should be available audibly and tactilely. (e) Serial Numbers: Serial numbers will be available in alternate formats for both hardware devices and software. (f) Registration: Registration of products should be achievable without requirement for visual identification of serial numbers. (Pre installation and setup documentation should be available in alternative media. Such as a technical support telephone number, audio, or Internet connection.) 5. Paper/Ribbon/Toner installation: Loading the device will allow loading from the front of the unit with one hand. 6. Error recovery: Physical - (e.g. paper jam) will allow for correction of the error to be done from a seated position, with one hand. (Invalid Media Error Messages: Error messages should be displayed in both tactile and audible formats. Logical - (e.g. LED errors) general and specific errors will notify the user with both audible and visual notification (beeps and flashing lights). 7. Installation software: Installation software will offer a textual version of the installation process to accommodate screen readers. 8. Status of buttons and switches: Status of buttons and switches will be easily determined through both tactile and visual inspection. 9. Operation of buttons and switches: All buttons and switches will be operational with one hand, and clearance away from other limiting design features as to not obstruct the users access to the button or switch. (REF: Part 1193 - Telecommunications Act Accessibility Guidelines PBX Button Layout: Numeric key pads should be consistent with audio identifiers and tactile landmarks on the five (5) and the one (1) keys. Intercom and other key layouts should provide audio and tactile identifiers) 10. Battery installation/removal: Should be capable of being performed with one hand. 11. Specific devices: Printers: Require that toner cartridges become operational with the use of one hand. Ribbons and ink cartridges will use both tactile and visual accommodation to identify the product (e.g. different colors for ink cartridges) Faxes: Require both audible and tactile procedures for setup (e.g. speed dial settings) TELEPHONES: This part provides requirements for accessibility, usability, and compatibility of telecommunications equipment and customer premises equipment covered by the Telecommunications Act of 1996 (47 U.S.C. 255). TTY Compatibility: [1193.51(d)]. Products which provide a function allowing voice communication and which do not themselves provide a TTY functionality shall provide a standard non-acoustic connection point for TTYs. It shall also be possible for the user to easily turn any microphone on and off to allow the user to inter-mix speech with TTY use. PERIPHERAL DEVICES: Identifying labeling of media: Media should carry tactile and visual definition of top/bottom and front and back. SOFTWARE: 1. Written instructions for the installation and set up of software shall include certain mandatory content and shall be provided in digital form. The mandatory content of instructions for the installation and set up of software is as follows: 1. all references to mouse controls or actions shall be accompanied by the keyboard equivalent control or action. 2. all images depicting control icons shall be accompanied by the textual name that identifies the icon. 3. When direct technical support is provided, phone numbers, e-mail addresses or other contact information shall be provided in all forms of the written instructions. 2. At least one copy of written instructions for the installation and set up of software in digital form shall be a plain ASCII text file with text line lengths less than 76 characters including spaces for margins and indentation and shall be provided regardless of any other digital form provided. 3. If a digital form of the written instructions for the installation and set up of software is provided as a hypertext files, it shall be written in conformance to section XXX(this reference is to the section for web page design) of these standards. ADVISORY GUIDANCE: (a) Plain ASCII text is the most universally accessible mode that does not require proprietary programs to view and which and be easily transferred to portable Notetakers to make the information available during the process of installing or setting up software. (b) Hypertext, while unsuitable for Notetakers and requiring proprietary programs to view, may be more easily rendered into some more accessible forms such as magnified print or Braille and, with appropriate links, be more conveniently navigated; thus, hypertext files should conform to accessibility standards. 2. Utilities provided for the installation and set up of operating systems and other software shall provide equivalent facilitation. Utilities shall be furnished by computer hardware providers for the set up of hardware CMOS ROM and shall provide equivalent facilitation. Equivalent facilitation is required for all functions including, but not limited to, menu choices and selections, text input, error messages, progress gauges and status alerts. 1. utilities provided for the installation and set up of operating systems shall provide, without the aid of third party assistive technology, equivalent facilitation that make it operable in accordance with the following: 1. Operable without vision. Provide at least one mode that does not require user vision. 2. Operable with low vision. Provide at least one mode that can be read by users with visual acuity between 20/70 and 20/200. 3. Operable with little or no color perception. Provide 4. At least one mode that does not require user color perception. 5. Operable without hearing. Provide at least one mode that does not require user auditory perception. 6. Operable with one hand. Provide at least one mode that does not require user fine motor control or simultaneous actions. 7. Operable without time-dependent controls. Provide at least one mode that does not require a response time. Alternatively, a response time may be required if it can be by-passed or adjusted by the user over a wide range. Advisory Guidance - assistive technology usually requires the presence of an operating system and, hence, is not necessarily available during installation and set up of operating systems. 3. Utilities provided for the installation and set up of software other than operating systems shall provide equivalent facilitation with or without the aid of third party assistive technology that make it operable in accordance with the following: 1. Operable without vision. Provide at least one mode that does not require user vision. 2. Operable with low vision. Provide at least one mode that can be read by users with visual acuity between 20/70 and 20/200. 3. Operable with little or no color perception. Provide at least one mode that does not require user color perception. 4. Operable without hearing. Provide at least one mode that does not require user auditory perception. 5. Operable with limited manual dexterity. Provide at least one mode that does not require user fine motor control or simultaneous actions. 6. Operable without time-dependent controls. Provide at least one mode that does not require a response time. Alternatively, a response time may be required if it can be by-passed or adjusted by the user over a wide range. 7. Utilities shall be furnished by computer hardware providers for the set up of hardware ROM or CMOS and shall provide, with or without the aid of third party assistive technology, equivalent facilitation that make it operable in accordance with the following: [NOTE that "with third party assistive technology implies that such utilities run under the operating system] 8. Operable without vision. Provide at least one mode that does not require user vision. 9. Operable with low vision. Provide at least one mode that can be read by users with visual acuity between 20/70 and 20/200. 10. Operable with little or no color perception. Provide at least one mode that does not require user color perception. 11. Operable without hearing. Provide at least one mode that does not require user auditory perception. 12. Operable with limited manual dexterity. Provide at least one mode that does not require user fine motor control or simultaneous actions. 13. Operable without time-dependent controls. Provide at least one mode that does not require a response time. Alternatively, a response time may be required if it can be by-passed or adjusted by the user over a wide range. 14. TECHNICAL SUPPORT- When direct technical support for software installation and set up is provided by telephone, e- mail, fax or other direct contact methods, persons providing the technical support shall have knowledge of, or ready access to, the keyboard equivalents for all mouse controls and actions. Computer Hardware: General Setup: 1. Connection of appropriate cables, mounting and attaching elements of the device both internally inside the device, and externally to other devices such as mounting a hard drive in an available drive bay and connecting it to the mother board, or seating a video card in an available bus slot and connecting an external monitor, the force required to make connections shall be no greater than 5 lbf (22.2 N). 2. Audible and visual prompts will occur under the following circumstances: 1. The installer needs to observe any error and system status messages displayed as a device boots, or as applications fail to function properly 2. The installer (or user)is prompted when the system comes online properly, or is required to gain access to configuration menus 3. If the device provides the user some indication that it is ready for use, such indication shall be supplied through clear and readily identifiable visual and audible indicators; and another clearly different yet readily identifiable pair of visual and audible indicators shall advise that the device has failed to boot should it so fail. In the latter circumstance, any standard data port on the device should be usable to obtain diagnostic information through standard protocols. 4. The installer/user is required to edit system configuration data in BIOS/CMOS 5. The need to obtain data from diagnostic tools or when applications fail to function properly. 2. If a keyboard is provided for user data entry, the keyboard should allow: 2.1 Keyboard Enhancement. The Offer shall provide keyboard enhancement which provides the functionality outlined below. The keyboard enhancement offered shall be capable of operating on the standard keyboard offered with the proposed desktop, laptop, or portable computer. The keyboard enhancement shall be able to execute independently or in combination at a minimum, the following functions: ú Execution of multiple keystroke commands (e.g., "CTRL-C") serially rather than simultaneously. ú Disabling and adjustment of the keyboard repeat tolerances. ú Emulation of a mouse or similar pointing input device movements from the keyboard. ú Visual and auditory indication of key status for the; Number Lock, Shift/Caps Lock, and Scroll Lock keys. ú Adjustment of volume level of the keyboard audible feedback. 2.2. Keyboard Alternative(s). The Offer shall provide an alternate input device to accommodate users unable to use the standard keyboard. The alternate keyboard shall be integrated with the proposed end-user system(s) and provide the following functions: ú Emulation and transmission of user input of any valid keystroke combination available from the standard keyboard. ú Emulation of a mouse or similar pointing input device movements from the keyboard. The proposed workstations must be capable of working with the following types of alternate input devices. ú Mini keyboard ú Large keyboard ú Row/column scanner ú Braille Chord input ú Chordic device ú DVORAK keyboard (NOTE: Further language may be necessary to describe exactly what is required by the alternative device. For example a keyboard with l l/2" or l/2" keys or one that is activated by single switch supported by row/column scanning software will have to be specified to meet the particular requirements.) 2.3 Keyboard Accessories. The Offer shall provide the following product(s) to aid users in the use of the standard keyboard: 2.3.1 Keyguard. Keyguards or keyboard guards prevent inadvertent or multiple key depressions. Keyguard template holes shall be no less than 1..5 cm or l/2" in diameter and correspond to the key arrangement of the standard as described in Section 1.1. The keyguard shall be attachable to the surface of the keyboard to ensure stability. The keyguard and any attaching hardware shall be removable. 2.3.2 Keyboard overlays. Keyboard tactile overlays to identify locations of home row keys and important non-standard location keys, e.g., ESC, ENTER, CTRL and ALT. 2.3.3 Keyboard covers. Molded plastic covers, designed to cover the standard keyboard, to prevent damage to the keyboard from spilled liquids. 2.4 Keyboard Layout: 2.4.1 Nibs on the "f" and "j" keys of a QWERTY keyboard; 2.4.2 Either some amount of readily identifiable space between the three sets of four "F" keys on a standard PC keyboard (F1, F2, F3, F12), or nibs on the F4, F8, and F12 keys to indicate these groupings 2.4.3 A nib on the "FN" key on a computer notebook; 2.4.4 A nib on the "5" key of a number input key group; 3.0 Ejecting any user storable disk, data cartridge, CD ROM, or similar external data storage medium shall require no more than the force required than 5 lbf (22.2 N). 4.0 Any device which is intended for use on a voice or data network should be fully configurable through a standard data network connection using W3 standard browsers. 5.0 Laptops: 5.1 Laptop covers will be capable of opening with one hand. 5.2 Battery life status will be available in an alternative text format 5.3 PCMCIA cards will be removable with two fingers 6.0 Device drivers will support current industry protocols 7.0 The mouse will be capable of disabling without going into CMOS 8.0 Mainframe: 8.1 Allow hardware configuration console to be accessible 9.0 Integration issues: 9.1 Video card compatible with screen readers and magnifier 9.2 Configuration settings for compatible keyboard emulators 9.3 Flash ROM to perform updated chip programming ..END OF DRAFT OF 5.5 5.6. Proposed Family Standards: Documentation, Labeling & Support [1/29/99 draft, unsigned] On-line resources offered by a vendor for the purpose of supporting product information, documentation or other product related services must be accessible. 1. If the product vendor offers support by way of e-mail for the purpose of supporting product information, documentation or other product related services, then all such email-- including attachments must be available in text format. 2. All product support and documentation provided by way of the Web must be accessible. * If on-line support is provided, then it must be fully functional and navigable using graphical web browsers) with graphics, sounds and style sheets turned off. * If background patterns are used, then there should be significant contrast between text and background colors. * If style sheets are used, then the page should be fully functional when custom settings for font, color or other features are applied by the user. * If audio files are used, then offer a text transcript of the file. * If videos are used, then offer both captioning and a text transcript. * If the use of tables and columns is necessary, then provide a text-only version of the table or page containing columns. * If bitmapped text (such as clickable maps) are used, then provide text links as an alternative to bitmap text. Text anchors can be provided above or below the bitmapped text. * Use only proportional font markups, such as H1, H2, H3 rather than specifying font sizes. * Avoid using text that changes or moves, i.e. avoid using the BLINK and MARQUEE tags. * If graphics are used, then provide ALT-TEXT tags for graphics. If using graphics to provide organization or structure to the document, then attach ALT-TEXT to images so as to supply the same changes in context that the visual cues provide. * Use consistent and simple layout. Buttons that perform the same function on different pages (for example, "return to home page") should be located in a consistent location on the page. * If following these standards would significantly interfere with the presentation of the information, then provide a text-only page which shows the same information in an accessible format. The link to the text-only page should be one of the first encountered on the graphics page and vice- versa. Please note: It is not necessary or desirable to offer text-only versions of web pages on your site. Most web pages can be, and should be, made accessible without creating a separate text-only site. [Steve Mendelsohn draft 1/26/99] (Note: Except where otherwise indicated, this Proposed Standard addresses only verbal material, (that is, material and information which is presented in words, either textual or oral). Proposed Standards for the presentation of pictorial, graphical, nonverbal-audible or other nonverbal information (including standards for accessibility of such information in terms of content and methodology of presentation) will be presented elsewhere.) For purposes of this procurement, all product documentation, as defined below, shall comply with the requirements set forth herein, and shall be tendered or made available in accessible formats and alternative modes, as specified below. For purposes of this Standard, the term "documentation" includes all informational, instructional, descriptive, technical or other materials furnished, whether routinely or pursuant to special contract provisions, by the vendor to the purchasing agency, in connection with or as part of the electronic and/or information technology product, whether such materials are singly or separately packaged with the procured items, and whether such materials are furnished at the time of delivery of the procured items or at a later time. When a procurement involves multiple items of the same nature, the accessible documentation requirement shall apply to the same extent as does the obligation to provide print documentation. Thus, if 100 workstations are normally accompanied by 100 user manuals, 100 accessible user manuals (as defined below) must be supplied. Typical documentation would include instruction manuals, technical specifications, product support contact information, lists of peripherals and software supported or accommodated, maintenance and extended maintenance agreements, reference cards and product registration instructions/information. This list is offered for illustrative purposes only, and should not be considered as exhaustive. Any information provided in written or oral form in the context of the contract shall be regarded as documentation for purposes of these standards. Audio and videotapes, multimedia disks and CD-ROMs, DVDs and in-person presentations shall be regarded as documentation and support within the meaning of this Standard, and shall be subject to the same accessibility requirements set forth below. E-mail and web access shall also be considered product documentation or support resources, as the case may be, if they are provided with the product or recommended as a resource for those who own or use the product. The term "accessibility" means that materials are provided in alternative formats in addition to print, or in multiple formats, so that no information is available through only one medium or through the use of one sensory modality, and so that no user's access to information pertaining to the equipment items will be restricted by reason of a limitation of vision, a limitation of hearing, or a limitation associated with any other disability. The concept of accessibility presupposes that all information is available, at the election of the user, in hard-copy and electronic media, and for visual or audio input. Accessibility also denotes the timely availability of documentation and the accuracy and completeness of information. Finally, it requires that the format chosen be appropriate to the nature of the material in question. If information is normally conveyed in writing because of its length or complexity, oral presentation would not comport with the requirements of accessibility, because the ordinary user cannot be expected to absorb or to retrieve it when presented in that form. Examples of measures that will be deemed to meet the requirements of accessible documentation include the provision of textual material in identical print and diskette versions; the incorporation of closed-captioning and video-description on all videotape or other audio-visual materials, the provision of written transcripts of all audio, videotape, other multimedia, or scripted live presentations. When videotapes or other AV, slides or materials are utilized in product demonstration or as part of other contractually-determined support services, the requirements of accessibility herein described are not satisfied unless the closed-captioning contains a full rendition of the entire spoken content, and unless the video-description includes complete descriptions, sufficient to convey the key informational elements and content, of all visual information presented on the screen. "Labeling", which is a component of documentation, means information sufficient to allow users to identify the various components of equipment that must be set, attached or detached or monitored, or that are otherwise in the assemblage, configuration, activation or upgrading of equipment. Examples of label information include the identification of various ports, connectors, jacks and non-keyboard controls on equipment; the readouts, settings and other sources of status information that must be monitored or modified in order to use the equipment; and the identification of accessibility features. Information required for registration of a product, especially when such registration or the ability to provide the registration number is a prerequisite for customer support, shall also be considered to be label information for purposes of this Standard. For purposes of this Standard, a bid or offer shall be deemed to provide "accessibility" when it includes details of the methods used to achieve the functional capabilities and informational outputs described in this Standard. Contracts will vary widely in the customer, product or other ongoing support they specify. For purposes of this Standard, "support" services are defined as those requested or mandated under the contract, or those routinely expected and offered to public sector purchasers in comparable settings or with the given kind of equipment. To the extent such support services are provided to the purchaser or to individual users, such support services shall meet the requirements set forth above. Therefore, if the bidder's commitments extend to the provision of written materials, background or technical materials of any kind, then such documents must be made available in print, via diskette and either through e-mail or on the web. If online support materials are utilized, either as a primary communications/information modality for all users or specifically as an accessibility strategy, it shall be designed so as to ensure that e-mail messages are communicated in an appropriate manner; and such web sites shall be designed and maintained in accordance with the Accessibility Guidelines established by the World Wide Web Consortium or such successor Guidelines as the Access Board may from time to time designate. If the contract calls for telephone support, the bidder shall assure that such support is available via text telephone, and that a mechanism exists whereby callers who cannot effectively utilize telephone response systems can bypass such systems and be put directly in contact with a customer service representative or an operator who can promptly route the call to the appropriate personnel. Support personnel shall be familiar with the accessibility features of the equipment they support, and shall be able to give instructions predicated on the use of either a mouse or a keyboard. All requirements and definitions set forth herein shall apply to the documentation and support materials/services accompanying software as well. In addition, contracts shall require that bidders take steps to make disks identifiable to users by distinct visual and by non-visual means. Measures for accomplishing this contractual goal may include incorporation on each disk of a "readme" file, stating the identity of the disk; the use of tactile markers on each disk of multi-disk programs to indicate which disk is which; or the packaging of associated disks or other electronic media in such a way as to make the order, as for example from front to back, obvious and that will readily allow for retention and storage of the disks in their original order. 6. Appendices 6.1. Glossary (borrowed from Part 1193, mostly) Alternate formats. Alternate formats may include, but are not limited to, Braille, ASCII text, large print, and audio cassette recording. (HTML?) Alternate modes. Different means of providing information to users of products including product documentation and information about the status or operation of controls. Examples of alternate modes may include, but are not limited to, voice, fax, relay service, TTY, Internet posting, captioning, text-to-speech synthesis, and video description. Compatible. Need a real definition. The TAAC is quite tied to telecommunications. Here's a rewrite to generalize it: Compatible means the EIT can be used with, does not interfere with, and where applicable, can be connected to assistive technology products (hardware and/or software) used by individuals with disabilities to achieve access. Customer premises equipment. Equipment employed on the premises of a person (other than a carrier) to originate, route, or terminate telecommunications. Peripheral devices. Devices employed in connection with electronic equipment and information technology to translate, enhance, or otherwise transform information into a form accessible to individuals with disabilities. Telecommunications. The transmission, between or among points specified by the user, of information of the user's choosing, without change in the form or content of the information as sent and received. Telecommunications equipment. Equipment, other than customer premises equipment, used by a carrier to provide telecommunications services, and includes software integral to such equipment (including upgrades). Telecommunications service. The offering of telecommunications for a fee directly to the public, or to such classes of users as to be effectively available directly to the public, regardless of the facilities used. TTY. An abbreviation for teletypewriter. Machinery or equipment that employs interactive text based communications through the transmission of coded signals across the standard telephone network. TTYs can include, for example, devices known as TDDs (telecommunication display devices or telecommunication devices for deaf persons) or computers with special modems. TTYs are also called text telephones. Usable. Means that individuals with disabilities have access to the full functionality and documentation for the product, including instructions, product information (including accessible feature information), documentation, and technical support functionally equivalent to that provided to individuals without disabilities. 6.2 Bibliography 6.3 Scenarios 6.4 References IEEE Std 100-1997, The New IEEE Standard Dictionary of Electrical and Electronics Terms 5th ed. 6.5 Disability Access Compliance Form Disability Access Compliance Form This form is design to summarize the 508 compliance of a product or contract offering. The contractor should complete the form and present it with the bid package. Additional information on access features that are believed to be new or exemplary may be attached. Supporting documentation for the items summarized on this form should not be submitted with the form, but made available, if requested by the contracting officer. Is this product Degree of Notes & Comments accessible Accessibility To an individual who has: - No Vision Core functionality is accessible. Entire functionality is accessible. Product has new or superior accessibility. Industry standards exist for this category and product type and can be used to support this claim. - Low Vision (no Core functionality is audio) accessible. Entire functionality is accessible. Product has new or superior accessibility. Industry standards exist for this category and product type and can be used to support this claim. - No Hearing Core functionality is accessible. Entire functionality is accessible. Product has new or superior accessibility. Industry standards exist for this category and product type and can be used to support this claim. - Hard of Core functionality is Hearing accessible. Entire functionality is accessible. Product has new or superior accessibility. Industry standards exist for this category and product type and can be used to support this claim. - Manipulation Core functionality is accessible. Entire functionality is accessible. Product has new or superior accessibility. Industry standards exist for this category and product type and can be used to support this claim. - Reach and Core functionality is Strength accessible. Entire functionality is accessible. Product has new or superior accessibility. Industry standards exist for this category and product type and can be used to support this claim. - Cognitive Core functionality is accessible. Entire functionality is accessible. Product has new or superior accessibility. Industry standards exist for this category and product type and can be used to support this claim. Disability Access Compliance Form (Instructions) This form is provided as a means of summarizing a product's accessibility. It should be completed and submitted with the bid package. 1. For each product a division shall be made between the core functionality and entire functionality. Core functionality is the minimum functionality required to operate the product for its primary functions. The entire functionality is the functionality required to operate all of a product's functions and features. 2. The form is to be completed based on an analysis of operational chains for each product. This is done by performing the following analysis: a. A list of all operations required to operate the product is made. Care should be taken to include the activities required to learn how to operate the product and provide regular maintenance. b. The list of operations is then divided into a core list and the entire list. The core list identifies the basic operations necessary to operate the product for its primary mode or purpose. The entire list of operations includes the core list and extends to all features and functions provided with the product. c. For each operation construct operational chains of the steps required to perform each operation. d. a .Analyze each operational chain for each of the areas of limitation. e. If in a given category all of the operational steps can be accomplished then the product may be listed as accessible for that category. If it is not then the box should not be checked. Illustration For a desktop telephone business phone a list of operations might include reading the user documentation, making a call, receiving a call, making a conference call. The first three operations would be listed as core operations and the ability to make a conference call would be included in the extended list. A list of steps is then made for each of these operations. As one example, if the user documentation can be accessed by someone without vision then that operation is accessible. As another example, to make a call the phone must be taken off hook, the dialtone sensed, the number dialed, the call conducted, the call terminated and the phone placed back on-hook. For the no vision category, if all of these steps can be accomplished without vision then that operation is accessible. If all of the core operations are accessible without vision then that box should be checked. The process then repeats itself for the other categories listed. 1. A claim of new or superior accessibility should only be made if the product offers something unique or demonstrably superior for a given class of accessibility, as compared to what is generally available in comparable product offerings on the market. Details and supporting evidence may be provided to amplify such claims. 2. If industry standards exist, which apply to the product type and can be used to objectively substantiate the claim of accessibility these should be cited and used as the basis for the claim. Where they exist, the use of industry standards, which provide an objective basis for making a claim of accessibility, is preferred.