Hello. Please sign in!

36 CFR Part 1194 - Proposed Information and Communication Technology (ICT) Standards and Guidelines NPRM - Preamble

This document is the preamble to the NPRM. Click here to view the NPRM. See also: Final Rule published to the Federal Register 1/18/17 that jointly updates requirements for ICT covered by Section 508 of the Rehabilitation Act and Section 255 of the Communication Act.

2. Justification for Applying WCAG 2.0 to Non-Web ICT

The Access Board is proposing to require not only Web content to conform to the Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0—an approach with which commenters to the 2010 and 2011 ANPRMs unanimously agreed—but also software and non-Web documents. Several commenters to the 2011 ANRPM were critical of this approach, and questioned the propriety of applying WCAG 2.0 to non-Web ICT. For the reasons noted below, the Board believes that applying WCAG 2.0 outside the web browser environment not only ensures greater accessibility for persons with disabilities, but also minimizes the incremental burden on regulated entities by simplifying compliance through incorporation of a technologically-neutral consensus standard.

Because WCAG 2.0 was written to be technology neutral, the language and phrasing of the Success Criteria can be applied to any technology found on the Web. Since most file types are found on the Web and much software is now Web-enabled, it is reasonable to utilize WCAG 2.0 to evaluate off-line documents and software interfaces with straightforward substitution of terms to address this new application. This approach has the potential to significantly simplify accessibility conformance and assessment.

We find support for our approach from two other sources, namely the European Commission’s Standardization Mandate M 376 (M376) of March 2012 and the World Wide Web Consortium’s WCAG2ICT Task Force (“Task Force”). The W3C formed the Task Force in June 2012 in part to address reservations, expressed by some of the commenters to our 2011 ANPRM, about applying the criteria for accessible Web content to off-line documents and software. W3C invited participation from subject-matter experts from around the world, including representatives of federal agencies and others who had concerns with our approach. The Task Force’s final consensus report provides guidance concerning application of WCAG 2.0 to non-Web ICT, specifically non-Web documents and software. See W3C Web Accessibility Initiative, WSC Working Group Note - Guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies (Sept. 5, 2013), available at http://www.w3.org/TR/wcag2ict/.

The Task Force analyzed each of the WCAG 2.0 Success Criteria to determine their suitability for application to non-Web content. There are thirty-eight Level A and Level AA Success Criteria in WCAG 2.0. The Task Force found that the majority of Success Criteria from WCAG 2.0 can be applied to non-Web documents and software with no, or only minimal, changes. Specifically, twenty-six Success Criteria do not include any Web-related terms and, therefore, can be applied directly as written and as described in the “Intent” sections of the most current version of “Understanding WCAG 2.0.” Thirteen of these twenty-six can be applied without any additional notes. The other thirteen also can be applied as written, but the Task Force provided additional informative notes in its report for the sake of clarity.

Of the remaining twelve Success Criteria, the Task Force found that eight of them can be applied as written when certain Web-specific terms or phrases like “Web page” are replaced with non-Web terms or phrases like “non-Web documents and software.” Additional notes are provided in the Task Force report to assist in the application of these Success Criteria to non-Web ICT. One example is Success Criterion 2.4.5 Multiple Ways. The Task Force noted that, when applied to the non-Web environment, this criterion requires that there be more than one way to locate a document (or software program) within a set of documents or programs. For mobile devices, this criterion could be satisfied by an operating system that makes files locatable by directory and search functions—features that are nearly ubiquitous among mobile operating systems in use today.

Another example is Success Criterion 3.2.3 Consistent Navigation. For this criterion, the Task Force noted that application to the non-Web environment would require consistency among navigational elements when such elements were repeated within sets of documents or software programs. To be conformant, navigational elements would be required to occur in the same relative order each time they are presented. It is unlikely that authors would provide navigation elements for a set of related documents and then present them differently from document to document, thereby defeating their purpose.

The Task Force’s report also notes that applying the success criteria in WCAG 2.0 to non-Web ICT with closed functionality proves problematic when a success criterion assumes the presence of assistive technologies, since closed functionality—by definition—does not allow attachment or use of assistive technology. This might occur, for example, when an eBook allows assistive technologies to access all of the user interface controls of the eBook program (open functionality), but does not allow such technologies to access the actual content of books (closed functionality). The Task Force identified 14 success criteria for which compliance might prove challenging for developers of ICT products with closed functionality. We propose to resolve this issue by exempting ICT with closed functionality from certain WCAG 2.0 Success Criteria, in conjunction with the addition of requirements specific to such products in Chapter 402, Closed Functionality.

By incorporating WCAG 2.0 by reference, the proposed standards would provide a single set of requirements for websites, documents, and software. WCAG 2.0 addresses new technologies and is responsive to the fact that the characteristics of products (e.g., native browser behavior and plug-ins and applets) have converged over time. Today, there are fewer distinctions among product categories, and some are outdated. For example, modern smartphones include: software applications and operating systems, Web-based intranet and Internet information and applications, and video and multimedia products. Additionally, smartphones are portable computers, telecommunications products, and self-contained closed products. New requirements in WCAG 2.0 also address gaps in the existing 508 Standards. Examples include: a requirement for a logical reading order, the ability to resize text, and the ability to turn off background audio that might interfere with comprehension and screen reading software.

[MORE INFO...]

*You must sign in to view [MORE INFO...]