index2.html

---
title: 508 Knowledge Management System
layout: universal
toc: /toc/ict.html
toc-group: ict
order-number: 1
image-directory: /images/ict
right-sidenav: sidenav-right-kms.html
ta-text: link to add stuff to KMS
---
{% assign ict-chapters = site.ict | where: "title","About the ICT Accessibility 508 Standards and 255 Guidelines" %}
{% for chapter in ict-chapters %}
	<!-- <h2 id="about-the-ict-accessibility-standards">{{chapter.title}}</h2> -->
    <!-- <div>{{chapter.content | markdownify}}</div> -->
{% endfor %}
<!-- <hr> --> 

<!-- STANDARDS -->
<div>
	<div id="appendixA">
    	<h1>Appendix A to Part 1194 – Section 508 of the Rehabilitation Act: Application and Scoping Requirements</h1>
			<div class="chapter" id="508chapter1">
				<h2>508 Chapter 1: Application and Administration</h2>
					<h3 id="E101-general">E101 General</h3>
						<h4 id="E101.1">E101.1 Purpose</h4>
							<p class="dot1desc">These Revised 508 Standards, which consist of 508 Chapters 1 and 2 (Appendix A), along with Chapters 3 through 7 (Appendix C), contain scoping and technical requirements for information and communication technology (ICT) to ensure accessibility and usability by individuals with disabilities. Compliance with these standards is mandatory for Federal agencies subject to Section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. 794d).</p>
						<h4 id="E101.2">E101.2 Equivalent Facilitation</h4>
							<p class="dot1desc">The use of an alternative design or technology that results in substantially equivalent or greater accessibility and usability by individuals with disabilities than would be provided by conformance to one or more of the requirements in Chapters 4 and 5 of the Revised 508 Standards is permitted. The functional performance criteria in Chapter 3 shall be used to determine whether substantially equivalent or greater accessibility and usability is provided to individuals with disabilities.</p>
						<h4 id="E101.3">E101.3 Conventional Industry Tolerances</h4>
							<p class="dot1desc">Dimensions are subject to conventional industry tolerances except where dimensions are stated as a range with specific minimum or maximum end points.</p>
						<h4 id="E101.4">E101.4 Units of Measurement</h4>
							<p class="dot1desc">Measurements are stated in metric and U.S. customary units. The values stated in each system (metric and U.S. customary units) may not be exact equivalents, and each system shall be used independently of the other.</p>
					<h3 id="E102-referenced-standards">E102 Referenced Standards</h3>
						<h4 id="E102.1">E102.1 Application</h4>
							<p class="dot1desc">The specific editions of the standards listed in Chapter 7 are incorporated by reference into 508 Chapter 2 (Scoping Requirements) and Chapters 3 through 6 to the prescribed extent of each such reference. Where conflicts occur between the Revised 508 Standards and the referenced standards, these Revised 508 Standards apply. </p>
					<h3 id="E103-definitions">E103 Definitions</h3>
						<h4 id="E103.1">E103.1 Terms Defined in Referenced Standards</h4>
							<p class="dot1desc">Terms defined in referenced standards and not defined in E103.4 shall have the meaning as defined in the referenced standards.</p>
						<h4 id="E103.2">E103.2 Undefined Terms</h4>
							<p class="dot1desc">Any term not defined in E103.4 or in referenced standards shall be given its ordinarily accepted meaning in the sense that the context implies.</p>
						<h4 id="E103.3">E103.3 Interchangeability</h4>
							<p class="dot1desc">Words, terms, and phrases used in the singular include the plural and those used in the plural include the singular.</p>
						<h4 id="E103.4">E103.4 Defined Terms</h4>
							<p class="dot1desc">For the purpose of the Revised 508 Standards, the terms defined in E103.4 have the indicated meaning.</p>
							<div id="definitions">
								<dl>
									<dt>Agency</dt>
										<dd>Any agency or department of the United States as defined in 44 U.S.C. 3502, and the United States Postal Service.</dd>
									<dt>Alteration</dt>
										<dd>A change to existing ICT that affects interoperability, the user interface, or access to information or data.</dd>
									<dt>Application.</dt>
										<dd>Software designed to perform, or to help the user to perform, a specific task or tasks.</dd>
									<dt>Assistive Technology (AT)</dt>
										<dd>Any item, piece of equipment, or product system, whether acquired commercially, modified, or customized, that is used to increase, maintain, or improve functional capabilities of individuals with disabilities.</dd>
									<dt>Audio Description.</dt>
										<dd>Narration added to the soundtrack to describe important visual details that cannot be understood from the main soundtrack alone. Audio description is a means to inform individuals who are blind or who have low vision about visual content essential for comprehension. Audio description of video provides information about actions, characters, scene changes, on-screen text, and other visual content. Audio description supplements the regular audio track of a program. Audio description is usually added during existing pauses in dialogue. Audio description is also called “video description” and “descriptive narration”.</dd>
									<dt>Authoring Tool</dt>
										<dd>Any software, or collection of software components, that can be used by authors, alone or collaboratively, to create or modify content for use by others, including other authors.</dd>
									<dt>Closed Functionality</dt>
										<dd>Characteristics that limit functionality or prevent a user from attaching or installing assistive technology. Examples of ICT with closed functionality are self-service machines, information kiosks, set-top boxes, fax machines, calculators, and computers that are locked down so that users may not adjust settings due to a policy such as Desktop Core Configuration.</dd>
									<dt>Content</dt>
										<dd>Electronic information and data, as well as the encoding that defines its structure, presentation, and interactions.</dd>
									<dt>Document</dt>
										<dd>Logically distinct assembly of content (such as a file, set of files, or streamed media) that: functions as a single entity rather than a collection; is not part of software; and does not include its own software to retrieve and present content for users. Examples of documents include, but are not limited to, letters, email messages, spreadsheets, presentations, podcasts, images, and movies.</dd>
									<dt>Existing ICT</dt>
										<dd>ICT that has been procured, maintained or used on or before January 18, 2018.</dd>
									<dt>Hardware</dt>
										<dd>A tangible device, equipment, or physical component of ICT, such as telephones, computers, multifunction copy machines, and keyboards.</dd>
									<dt id="defIT">Information Technology</dt>
										<dd>Shall have the same meaning as the term “information technology” set forth in 40 U.S.C. 11101(6)</dd>
									<dt>Information and Communication Technology (ICT)</dt>
										<dd> Information technology and other equipment, systems, technologies, or processes, for which the principal function is the creation, manipulation, storage, display, receipt, or transmission of electronic data and information, as well as any associated content. Examples of ICT include, but are not limited to: computers and peripheral equipment; information kiosks and transaction machines; telecommunications equipment; customer premises equipment; multifunction office machines; software; applications; Web sites; videos; and, electronic documents.</dd>
									<dt>Keyboard</dt>
										<dd> A set of systematically arranged alphanumeric keys or a control that generates alphanumeric input by which a machine or device is operated. A keyboard includes tactilely discernible keys used in conjunction with the alphanumeric keys if their function maps to keys on the keyboard interfaces.</dd>
									<dt>Label</dt>
										<dd> Text, or a component with a text alternative, that is presented to a user to identify content. A label is presented to all users, whereas a name may be hidden and only exposed by assistive technology. In many cases, the name and the label are the same.</dd>
									<dt>Menu</dt>
										<dd> A set of selectable options.</dd>
									<dt>Name</dt>
										<dd> Text by which software can identify a component to the user. A name may be hidden and only exposed by assistive technology, whereas a label is presented to all users. In many cases, the label and the name are the same. Name is unrelated to the name attribute in HTML.</dd>
									<dt>Non-Web Document</dt>
										<dd> A document that is not: a Web page, embedded in a Web page, or used in the rendering or functioning of Web pages.</dd>
									<dt>Non-Web Software</dt>
										<dd> Software that is not: a Web page, not embedded in a Web page, and not used in the rendering or functioning of Web pages.</dd>
									<dt>Operable Part</dt>
										<dd> Hardware-based user controls for activating, deactivating, or adjusting ICT.</dd>
									<dt>Platform Accessibility Services</dt>
										<dd> Services provided by a platform enabling interoperability with assistive technology. Examples are Application Programming Interfaces (API) and the Document Object Model (DOM).</dd>
									<dt>Platform Software</dt>
										<dd> Software that interacts with hardware or provides services for other software. Platform software may run or host other software, and may isolate them from underlying software or hardware layers. A single software component may have both platform and non-platform aspects. Examples of platforms are: desktop operating systems; embedded operating systems, including mobile systems; Web browsers; plug-ins to Web browsers that render a particular media or format; and sets of components that allow other applications to execute, such as applications which support macros or scripting.</dd>
									<dt>Programmatically Determinable</dt>
										<dd> Ability to be determined by software from author-supplied data that is provided in a way that different user agents, including assistive technologies, can extract and present the information to users in different modalities.</dd>
									<dt>Public Facing</dt>
										<dd> Content made available by an agency to members of the general public. Examples include, but are not limited to, an agency Web site, blog post, or social media pages.</dd>
									<dt>Real-Time Text (RTT)</dt>
										<dd> Communications using the transmission of text by which characters are transmitted by a terminal as they are typed. Real-time text is used for conversational purposes. Real-time text also may be used in voicemail, interactive voice response systems, and other similar application.</dd>
									<dt>Revised 508 Standards</dt>
										<dd> The standards for ICT developed, procured, maintained, or used by agencies subject to Section 508 of the Rehabilitation Act as set forth in 508 Chapters 1 and 2 (36 CFR part 1194, Appendix A), and Chapters 3 through 7 (36 CFR part 1194, Appendix C).</dd>
									<dt>Software</dt>
										<dd> Programs, procedures, rules, and related data and documentation that direct the use and operation of ICT and instruct it to perform a given task or function. Software includes, but is not limited to, applications, non-Web software, and platform software.</dd>
									<dt>Software Tools</dt>
										<dd> Software for which the primary function is the development of other software. Software tools usually come in the form of an Integrated Development Environment (IDE) and are a suite of related products and utilities. Examples of IDEs include Microsoft® Visual Studio®, Apple® Xcode®, and Eclipse Foundation Eclipse®.</dd>
									<dt>Telecommunications</dt>
										<dd> The signal 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.</dd>
									<dt>Terminal</dt>
										<dd> Device or software with which the end user directly interacts and that provides the user interface. For some systems, the software that provides the user interface may reside on more than one device such as a telephone and a server.</dd>
									<dt>Text</dt>
										<dd> A sequence of characters that can be programmatically determined and that expresses something in human language.</dd>
									<dt>TTY</dt>
										<dd> Equipment that enables interactive text based communications through the transmission of frequency-shift-keying audio tones across the public switched telephone network. TTYs include devices for real-time text communications and voice and text intermixed communications. Examples of intermixed communications are voice carry over and hearing carry over. One example of a TTY is a computer with TTY emulating software and modem.</dd>
									<dt>Variable Message Signs (VMS)</dt>
										<dd> Non-interactive electronic signs with scrolling, streaming, or paging-down capability. An example of a VMS is an electronic message board at a transit station that displays the gate and time information associated with the next train arrival.</dd>
									<dt>Voice over Internet Protocol (VoIP)</dt>
										<dd> A technology that provides real-time voice communications. VoIP requires a broadband connection from the user’s location and customer premises equipment compatible with Internet protocol.</dd>
									<dt>Web page</dt>
										<dd> A non-embedded resource obtained from a single Universal Resource Identifier (URI) using HyperText Transfer Protocol (HTTP) plus any other resources that are provided for the rendering, retrieval, and presentation of content.</dd>
								</dl>
							</div>
            </div> <!-- end 508 chapter 1 -->
            <hr>
			<div class="chapter" id="508chapter2">
				<h2>508 Chapter 2: Scoping Requirements</h2>
					<h3 id="E201-application">E201 Application</h3>
						<h4 id="E201.1">E201.1 Scope</h4>
							<p class="dot1desc"> ICT that is procured, developed, maintained, or used by agencies shall conform to the Revised 508 Standards.</p>
					<h3 id="E202-general-exceptions">E202 General Exceptions</h3>
						<h4 id="E202.1">E202.1 General</h4>
							<p class="dot1desc">ICT shall be exempt from compliance with the Revised 508 Standards to the extent specified by E202.</p>
						<h4 id="E202.2">E202.2 Legacy ICT</h4>
							<p class="dot1desc">Any component or portion of existing ICT that complies with an earlier standard issued pursuant to Section 508 of the Rehabilitation Act of 1973, as amended (as republished in Appendix D), and that has not been altered on or after January 18, 2018, shall not be required to be modified to conform to the Revised 508 Standards.</p>
						<h4 id="E202.3">E202.3 National Security Systems</h4>
							<p class="dot1desc">The Revised 508 Standards do not apply to ICT operated by agencies as part of a national security system, as defined by 40 U.S.C. 11103(a).</p>
						<h4 id="E202.4">E202.4 Federal Contracts</h4>
							<p class="dot1desc">ICT acquired by a contractor incidental to a contract shall not be required to conform to the Revised 508 Standards.</p>
						<h4 id="E202.5">E202.5 ICT Functions Located in Maintenance or Monitoring Spaces</h4>
							<p class="dot1desc">Where status indicators and operable parts for ICT functions are located in spaces that are frequented only by service personnel for maintenance, repair, or occasional monitoring of equipment, such status indicators and operable parts shall not be required to conform to the Revised 508 Standards.</p>
						<h4 id="E202.6">E202.6 Undue Burden or Fundamental Alteration</h4>
							<p class="dot1desc">Where an agency determines in accordance with E202.6 that conformance to requirements in the Revised 508 Standards would impose an undue burden or would result in a fundamental alteration in the nature of the ICT, conformance shall be required only to the extent that it does not impose an undue burden, or result in a fundamental alteration in the nature of the ICT.</p>
							<div class="dotdot">
								<h5 id="E202.6.1">E202.6.1 Basis for a Determination of Undue Burden</h5>
									<p class="dotdotdesc">In determining whether conformance to requirements in the Revised 508 Standards would impose an undue burden on the agency, the agency shall consider the extent to which conformance would impose significant difficulty or expense considering the agency resources available to the program or component for which the ICT is to be procured, developed, maintained, or used.</p>
								<h5 id="E202.6.2">E202.6.2 Required Documentation</h5>
									<p class="dotdotdesc">The responsible agency official shall document in writing the basis for determining that conformance to requirements in the Revised 508 Standards constitute an undue burden on the agency, or would result in a fundamental alteration in the nature of the ICT. The documentation shall include an explanation of why and to what extent compliance with applicable requirements would create an undue burden or result in a fundamental alteration in the nature of the ICT.</p>
								<h5 id="E202.6.3">E202.6.3 Alternative Means</h5>
									<p class="dotdotdesc">Where conformance to one or more requirements in the Revised 508 Standards imposes an undue burden or a fundamental alteration in the nature of the ICT, the agency shall provide individuals with disabilities access to and use of information and data by an alternative means that meets identified needs.</p>
							</div>
						<h4 id="E202.7">E202.7 Best Meets</h4>
							<p class="dot1desc">Where ICT conforming to one or more requirements in the Revised 508 Standards is not commercially available, the agency shall procure the ICT that best meets the Revised 508 Standards consistent with the agency’s business needs.</p>
							<div class="dotdot">
								<h5 id="E202.7.1">E202.7.1 Required Documentation</h5>
									<p class="dotdotdesc">The responsible agency official shall document in writing: (a) the non-availability of conforming ICT, including a description of market research performed and which provisions cannot be met, and (b) the basis for determining that the ICT to be procured best meets the requirements in the Revised 508 Standards consistent with the agency’s business needs.</p>
								<h5 id="E202.7.2">E202.7.2 Alternative Means</h5>
									<p class="dot">Where ICT that fully conforms to the Revised 508 Standards is not commercially available, the agency shall provide individuals with disabilities access to and use of information and data by an alternative means that meets identified needs.</p>
							</div>
					<h3 id="E203-functionality">E203 Access to Functionality</h3>
						<h4 id="E203.1">E203.1 General</h4>
							<p class="dot1desc">Agencies shall ensure that all functionality of ICT is accessible to and usable by individuals with disabilities, either directly or by supporting the use of assistive technology, and shall comply with E203. In providing access to all functionality of ICT, agencies shall ensure the following:</p>
							<div class="dotdot">
								<ol style="list-style-type:upper-alpha">
									<li>That Federal employees with disabilities have access to and use of information and data that is comparable to the access and use by Federal employees who are not individuals with disabilities; and</li>
									<li>That members of the public with disabilities who are seeking information or data from a Federal agency have access to and use of information and data that is comparable to that provided to members of the public who are not individuals with disabilities.</li>
								</ol>
							</div>
						<h4 id="E203.2">E203.2 User Needs</h4>
							<p class="dot1desc">When agencies procure, develop, maintain or use ICT they shall identify the needs of users with disabilities to determine:</p>
							<div class="dotdot">
								<ol class="ol_letters">
									<li>How users with disabilities will perform the functions supported by the ICT; and</li>
									<li>How the ICT will be developed, installed, configured, and maintained to support users with disabilities.</li>
								</ol>
							</div>
					<h3 id="E204-functional-performance-criteria">E204 Functional Performance Criteria</h3>
						<h4 id="E204.1">E204.1 General</h4>
							<p class="dot1desc">Where the requirements in Chapters 4 and 5 do not address one or more functions of ICT, the functions not addressed shall conform to the Functional Performance Criteria specified in Chapter 3.</p>
					<h3 id="E205-content">E205 Electronic Content </h3>
						<h4 id="E205.1">E205.1 General</h4>
							<p class="dot1desc">Electronic content shall comply with E205.</p>
						<h4 id="E205.2">E205.2 Public Facing</h4>
							<p class="dot1desc">Electronic content that is public facing shall conform to the accessibility requirements specified in E205.4.</p>
						<h4 id="E205.3">E205.3 Agency Official Communication</h4>
							<p class="dot1desc">Electronic content that is not public facing shall conform to the accessibility requirements specified in E205.4 when such content constitutes official business and is communicated by an agency through one or more of the following:</p>
							<div class="dotdot">
								<ol class="ol_letters">
									<li>An emergency notification;</li>
									<li>An initial or final decision adjudicating an administrative claim or proceeding;</li>
									<li>An internal or external program or policy announcement;</li>
									<li>A notice of benefits, program eligibility, employment opportunity, or personnel action;</li>
									<li>A formal acknowledgement of receipt;</li>
									<li>A survey questionnaire;</li>
									<li>A template or form;</li>
									<li>Educational or training materials; or</li>
									<li>Intranet content designed as a Web page.</li>
								</ol>
								<p>EXCEPTION: Records maintained by the National Archives and Records Administration (NARA) pursuant to Federal recordkeeping statutes shall not be required to conform to the Revised 508 Standards unless public facing.</p>
							</div>
						<h4 id="E205.4">E205.4 Accessibility Standard</h4>
							<p class="dot1desc">Electronic content shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).<br>
							EXCEPTION: Non-Web documents shall not be required to conform to the following four WCAG 2.0 Success Criteria: 2.4.1 Bypass Blocks, 2.4.5 Multiple Ways, 3.2.3 Consistent Navigation, and 3.2.4 Consistent Identification.</p>
							<div class="dotdot">
								<h5 id="E205.4.1">E205.4.1 Word Substitution when Applying WCAG to Non-Web Documents</h5>
									<p class="dotdotdesc">For non-Web documents, wherever the term “Web page” or “page” appears in WCAG 2.0 Level A and AA Success Criteria and Conformance Requirements, the term “document” shall be substituted for the terms “Web page” and “page”. In addition, in Success Criterion in 1.4.2, the phrase “in a document” shall be substituted for the phrase “on a Web page”.</p>
							</div>
					<h3 id="E206-hardware">E206 Hardware</h3>
						<h4 id="E206.1">E206.1 General</h4>
							<p class="dot1desc"> Where components of ICT are hardware and transmit information or have a user interface, such components shall conform to the requirements in Chapter 4.</p>
					<h3 id="E207-software">E207 Software</h3>
						<h4 id="E207.1">E207.1 General</h4>
							<p class="dot1desc">Where components of ICT are software and transmit information or have a user interface, such components shall conform to E207 and the requirements in Chapter 5.<br>
							EXCEPTION: Software that is assistive technology and that supports the accessibility services of the platform shall not be required to conform to the requirements in Chapter 5.</p>
						<h4 id="E207.2">E207.2 WCAG Conformance</h4>
							<p class="dot1desc">User interface components, as well as the content of platforms and applications, shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).<br>
							EXCEPTIONS: </p>
							<ol>
								<li>Software that is assistive technology and that supports the accessibility services of the platform shall not be required to conform to E207.2.</li>
								<li>Non-Web software shall not be required to conform to the following four Success Criteria in WCAG 2.0: 2.4.1 Bypass Blocks; 2.4.5 Multiple Ways; 3.2.3 Consistent Navigation; and 3.2.4 Consistent Identification.</li>
								<li>Non-Web software shall not be required to conform to Conformance Requirement 3 Complete Processes in WCAG 2.0.</li>
							</ol>
							<div class="dotdot">
								<h5>E207.2.1 Word Substitution when Applying WCAG to Non-Web Software</h5>
									<p class="dotdotdesc">For non-Web software, wherever the term “Web page” or “page” appears in WCAG 2.0 Level A and AA Success Criteria and Conformance Requirements, the term “software” shall be substituted for the terms “Web page” and “page”. In addition, in Success Criterion in 1.4.2, the phrase “in software” shall be substituted for the phrase “on a Web page.”</p>
							</div>
						<h4 id="E207.3">E207.3 Complete Processes for Non-Web Software</h4>
							<p class="dot1desc">Where non-Web software requires multiple steps to accomplish an activity, all software related to the activity to be accomplished shall conform to WCAG 2.0 as specified in E207.2.</p>
					<h3 id="E208-documentation-Services">E208 Support Documentation and Services</h3>
						<h4 id="E208.1">E208.1 General</h4>
							<p class="dot1desc">Where an agency provides support documentation or services for ICT, such documentation and services shall conform to the requirements in Chapter 6.</p>
			</div> <!-- end 508 Chapter 2 -->
	</div> <!-- end appendix a -->
	<hr>
	<div class="appendix" id="appendix-b">
		<h1>Appendix B to Part 1194 – Section 255 of the Communications Act: Application and Scoping Requirements</h1>
			<div class="chapter" id="255chapter1">
				<h2 id="255ch1">255 Chapter 1: Application and Administration</h2>
					<h3 id="C101-general">C101 General</h3>
						<h4 id="C101.1">C101.1 Purpose</h4>
							<p class="dot1desc">These Revised 255 Guidelines, which consist of 255 Chapters 1 and 2 (Appendix B), along with Chapters 3 through 7 (Appendix C), contain scoping and technical requirements for the design, development, and fabrication of telecommunications equipment and customer premises equipment, content, and support documentation and services, to ensure accessibility and usability by individuals with disabilities. These Revised 255 Guidelines are to be applied to the extent required by regulations issued by the Federal Communications Commission under Section 255 of the Communications Act of 1934, as amended (47 U.S.C. 255).</p>
						<h4 id="C101.2">C101.2 Equivalent Facilitation</h4>
							<p class="dot1desc">The use of an alternative design or technology that results in substantially equivalent or greater accessibility and usability by individuals with disabilities than would be provided by conformance to one or more of the requirements in Chapters 4 and 5 of the Revised 255 Guidelines is permitted. The functional performance criteria in Chapter 3 shall be used to determine whether substantially equivalent or greater accessibility and usability is provided to individuals with disabilities.</p>
						<h4 id="C101.3">C101.3 Conventional Industry Tolerances</h4>
							<p class="dot1desc">Dimensions are subject to conventional industry tolerances except where dimensions are stated as a range with specific minimum or maximum end points.</p>
						<h4 id="C101.4">C101.4 Units of Measurement</h4> <p class="dot1desc">Measurements are stated in metric and U.S. customary units. The values stated in each system (metric and U.S. customary units) may not be exact equivalents, and each system shall be used independently of the other.</p>
					<h3 id="C102-referenced-standards">C102 Referenced Standards </h3>
						<h4 id="C102.1">C102.1 Application</h4>
							<p class="dot1desc">The specific editions of the standards listed in Chapter 7 are incorporated by reference into 255 Chapter 2 (Scoping Requirements) and Chapters 3 through 6 to the prescribed extent of each such reference. Where conflicts occur between the Revised 255 Guidelines and the referenced standards, these Revised 255 Guidelines apply. </p>
					<h3 id="C103-definitions">C103 Definitions</h3>
						<h4 id="C103.1">C103.1 Terms Defined in Referenced Standards</h4>
							<p class="dot1desc">Terms defined in referenced standards and not defined in C103.4 shall have the meaning as defined in the referenced standards.</p>
						<h4 id="C103.2">C103.2 Undefined Terms</h4>
							<p class="dot1desc">Any term not defined in C103.4 or in referenced standards shall be given its ordinarily accepted meaning in the sense that the context implies.</p>
						<h4 id="C103.3">C103.3 Interchangeability</h4>
							<p class="dot1desc">Words, terms, and phrases used in the singular include the plural and those used in the plural include the singular.</p>
						<h4 id="C103.4">C103.4 Defined Terms</h4>
							<p class="dot1desc">For the purpose of the Revised 255 Guidelines, the terms defined in C103.4 have the indicated meaning.</p>
								<dl>
									<dt>Application</dt>
										<dd> Software designed to perform, or to help the user perform, a specific task or tasks.</dd>
									<dt>Assistive Technology (AT)</dt>
										<dd> Any item, piece of equipment, or product system, whether acquired commercially, modified, or customized, that is used to increase, maintain, or improve functional capabilities of individuals with disabilities.</dd>
									<dt>Audio Description</dt>
										<dd> Narration added to the soundtrack to describe important visual details that cannot be understood from the main soundtrack alone. Audio description is a means to inform individuals who are blind or who have low vision about visual content essential for comprehension. Audio description of video provides information about actions, characters, scene changes, on-screen text, and other visual content. Audio description supplements the regular audio track of a program. Audio description is usually added during existing pauses in dialogue. Audio description is also called “video description” and “descriptive narration.”</dd>
									<dt>Authoring Tool</dt>
										<dd> Any software, or collection of software components, that can be used by authors, alone or collaboratively, to create or modify content for use by others, including other authors.</dd>
									<dt>Closed Functionality</dt>
										<dd> Characteristics that limit functionality or prevent a user from attaching or installing assistive technology.</dd>
									<dt>Content</dt>
										<dd> Electronic information and data, as well as the encoding that defines its structure, presentation, and interactions.</dd>
									<dt>Customer Premises Equipment (CPE)</dt>
										<dd> Equipment used on the premises of a person (other than a carrier) to originate, route, or terminate telecommunications service or interconnected VoIP service, including software integral to the operation of telecommunications function of such equipment. Examples of CPE are telephones, routers, switches, residential gateways, set-top boxes, fixed mobile convergence products, home networking adaptors and Internet access gateways which enable consumers to access communications service providers’ services and distribute them around their house via a Local Access Network (LAN).</dd>
									<dt>Document</dt>
										<dd> Logically distinct assembly of content (such as a file, set of files, or streamed media) that: functions as a single entity rather than a collection; is not part of software; and does not include its own software to retrieve and present content for users. Examples of documents include, but are not limited to, letters, email messages, spreadsheets, presentations, podcasts, images, and movies.</dd>
									<dt>Hardware</dt>
										<dd> A tangible device, equipment, or physical component of ICT, such as telephones, computers, multifunction copy machines, and keyboards.</dd>
									<dt>Information and Communication Technology (ICT)</dt>
										<dd> Information technology and other equipment, systems, technologies, or processes, for which the principal function is the creation, manipulation, storage, display, receipt, or transmission of electronic data and information, as well as any associated content.</dd>
									<dt>Keyboard</dt>
										<dd> A set of systematically arranged alphanumeric keys or a control that generates alphanumeric input by which a machine or device is operated. A keyboard includes tactilely discernible keys used in conjunction with the alphanumeric keys if their function maps to keys on the keyboard interfaces.</dd>
									<dt>Label</dt>
										<dd> Text, or a component with a text alternative, that is presented to a user to identify content. A label is presented to all users, whereas a name may be hidden and only exposed by assistive technology. In many cases, the name and the label are the same.</dd>
									<dt>Manufacturer</dt>
										<dd> A final assembler of telecommunications equipment or customer premises equipment that sells such equipment to the public or to vendors that sell to the public.</dd>
									<dt>Menu</dt>
										<dd> A set of selectable options.</dd>
									<dt>Name</dt>
										<dd> Text by which software can identify a component to the user. A name may be hidden and only exposed by assistive technology, whereas a label is presented to all users. In many cases, the label and the name are the same. Name is unrelated to the name attribute in HTML.</dd>
									<dt>Non-Web Document</dt>
										<dd> A document that is not: a Web page, embedded in a Web page, or used in the rendering or functioning of Web pages.</dd>
									<dt>Non-Web Software</dt>
										<dd> Software that is not: a Web page, not embedded in a Web page, and not used in the rendering or functioning of Web pages.</dd>
									<dt>Operable Part</dt>
										<dd> Hardware-based user controls for activating, deactivating, or adjusting ICT.</dd>
									<dt>Platform Accessibility Services</dt>
										<dd> Services provided by a platform enabling interoperability with assistive technology. Examples are Application Programming Interfaces (API) and the Document Object Model (DOM).</dd>
									<dt>Platform Software</dt>
										<dd> Software that interacts with hardware or provides services for other software. Platform software may run or host other software, and may isolate them from underlying software or hardware layers. A single software component may have both platform and non-platform aspects. Examples of platforms are: desktop operating systems; embedded operating systems, including mobile systems; Web browsers; plug-ins to Web browsers that render a particular media or format; and sets of components that allow other applications to execute, such as applications which support macros or scripting.</dd>
									<dt>Programmatically Determinable</dt>
										<dd> Ability to be determined by software from author-supplied data that is provided in a way that different user agents, including assistive technologies, can extract and present the information to users in different modalities.</dd>
									<dt>Real-Time Text (RTT)</dt>
										<dd> Communications using the transmission of text by which characters are transmitted by a terminal as they are typed. Real-time text is used for conversational purposes. Real-time text also may be used in voicemail, interactive voice response systems, and other similar application.</dd>
									<dt>Revised 255 Guidelines</dt>
										<dd> The guidelines for telecommunications equipment and customer premises equipment covered by Section 255 of the Communications Act as set forth in 255 Chapters 1 and 2 (36 CFR part 1194, Appendix B), and Chapters 3 through 7 (36 CFR part 1193, Appendix C).</dd>
									<dt>Software</dt>
										<dd> Programs, procedures, rules, and related data and documentation that direct the use and operation of ICT and instruct it to perform a given task or function. Software includes, but is not limited to, applications, non-Web software, and platform software.</dd>
									<dt>Software Tools</dt>
										<dd> Software for which the primary function is the development of other software. Software tools usually come in the form of an Integrated Development Environment (IDE) and are a suite of related products and utilities. Examples of IDEs include Microsoft® Visual Studio®, Apple® Xcode®, and Eclipse Foundation Eclipse®</dd>
									<dt>Specialized Customer Premises Equipment</dt>
										<dd> Assistive technology used by individuals with disabilities to originate, route, or terminate telecommunications or interconnected VoIP service. Examples are TTYs and amplified telephones.</dd>
									<dt>Telecommunications</dt>
										<dd> The signal transmission between or among points specified by the user of information and of the user’s choosing without change in the form or content of the information as sent and received.</dd>
									<dt>Telecommunications Equipment</dt>
										<dd> Equipment, other than customer premises equipment, used by a carrier to provide telecommunications service or interconnected VoIP service and includes software integral to the operation of telecommunications function of such equipment.</dd>
									<dt>Terminal</dt>
										<dd> Device or software with which the end user directly interacts and that provides the user interface. For some systems, the software that provides the user interface may reside on more than one device such as a telephone and a server.</dd>
									<dt>Text</dt>
										<dd> A sequence of characters that can be programmatically determined and that expresses something in human language.</dd>
									<dt>TTY</dt>
										<dd> Equipment that enables interactive text based communications through the transmission of frequency-shift-keying audio tones across the public switched telephone network. TTYs include devices for real-time text communications and voice and text intermixed communications. Examples of intermixed communications are voice carry over and hearing carry over. One example of a TTY is a computer with TTY emulating software and modem.</dd>
									<dt>Variable Message Signs (VMS)</dt>
										<dd> Non-interactive electronic signs with scrolling, streaming, or paging-down capability. An example of a VMS is an electronic message board at a transit station that displays the gate and time information associated with the next train arrival.</dd>
									<dt>Voice over Internet Protocol (VoIP)</dt>
										<dd> A technology that provides real-time voice communications. VoIP requires a broadband connection from the user’s location and customer premises equipment compatible with Internet protocol.</dd>
									<dt>Web page</dt>
										<dd>A non-embedded resource obtained from a single Universal Resource Identifier (URI) using HyperText Transfer Protocol (HTTP) plus any other resources that are provided for the rendering, retrieval, and presentation of content.</dd>
								</dl>
            </div> <!-- end 255 chapter 1 -->
            <hr>
			<div class="chapter" id="255chapter2">
				<h2>255 Chapter 2: Scoping Requirements</h2>
					<h3 id="C201-application">C201 Application</h3>
						<h4 id="C201.1">C201.1 Scope</h4>
							<p class="dot1desc">Manufacturers shall comply with the requirements in the Revised 255 Guidelines applicable to telecommunications equipment and customer premises equipment (and related software integral to the operation of telecommunications functions) when newly released, upgraded, or substantially changed from an earlier version or model. Manufacturers shall also conform to the requirements in the Revised 255 Guidelines for support documentation and services, including electronic documents and Web-based product support.</p>
						<h4 id="C201.2">C201.2. Readily Achievable</h4>
							<p class="dot1desc">When a manufacturer determines that conformance to one or more requirements in Chapter 4 (Hardware) or Chapter 5 (Software) would not be readily achievable, it shall ensure that the equipment or software is compatible with existing peripheral devices or specialized customer premises equipment commonly used by individuals with disabilities to the extent readily achievable.</p>
						<h4 id="C201.3">C201.3 Access to Functionality</h4>
							<p class="dot1desc">Manufacturers shall ensure that telecommunications equipment and customer premises equipment is accessible to and usable by individuals with disabilities by providing direct access to all telecommunications functionality. Where manufacturers can demonstrate that it is not readily achievable for such equipment to provide direct access to all functionality, the equipment shall support the use of assistive technology and specialized customer premises equipment where readily achievable.</p>
						<h4 id="C201.4">C201.4 Prohibited Reduction of Accessibility, Usability, and Compatibility </h4>
							<p class="dot1desc">No change shall be undertaken that decreases, or has the effect of decreasing, the net accessibility, usability, or compatibility of telecommunications equipment or customer premises equipment.<br>
							EXCEPTION: Discontinuation of a product shall not be prohibited.</p>
						<h4 id="C201.5">C201.5 Design, Development, and Fabrication</h4>
							<p class="dot1desc">Manufacturers shall evaluate the accessibility, usability, and interoperability of telecommunications equipment and customer premises equipment during its product design, development, and fabrication.</p>
					<h3 id="C202-functional-performance-criteria">C202 Functional Performance Criteria</h3>
						<h4 id="C202.1">C202.1 General</h4>
							<p class="dot1Where">Where the requirements in Chapters 4 and 5 do not address one or more functions of telecommunications or customer premises equipment, the functions not addressed shall conform to the Functional Performance Criteria specified in Chapter 3.</p>
					<h3 id="C203-electronic-content">C203 Electronic Content</h3>
						<h4 id="C203.1">C203.1 General</h4>
							<p class="dot1Where">Electronic content that is integral to the use of telecommunications or customer premises equipment shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).<br>
							EXCEPTION: Non-Web documents shall not be required to conform to the following four WCAG 2.0 Success Criteria: 2.4.1 Bypass Blocks, 2.4.5 Multiple Ways, 3.2.3 Consistent Navigation, and 3.2.4 Consistent Identification.</p>
							<div class="dotdot">
								<h5 class="C203.1.1">C203.1.1 Word Substitution when Applying WCAG to Non-Web Documents</h5>
									<p class="dotdotdesc">For non-Web documents, wherever the term “Web page” or “page” appears in WCAG 2.0 Level A and AA Success Criteria and Conformance Requirements, the term “document’ shall be substituted for the terms “Web page” and “page.” In addition, in Success Criterion in 1.4.2, the phrase “in a document” shall be substituted for the phrase “on a Web page.”</p>
							</div>
					<h3 id="C204-hardware">C204 Hardware</h3>
						<h4 id="C204.1">C204.1 General</h4>
							<p class="dot1desc">Where components of telecommunications equipment and customer premises equipment are hardware, and transmit information or have a user interface, those components shall conform to applicable requirements in Chapter 4.<br>
							EXCEPTION: Components of telecommunications equipment and customer premises equipment shall not be required to conform to 402, 407.7, 407.8, 408, 412.8.4, and 415.</p>
					<h3 id="C205-software">C205 Software</h3>
						<h4 id="C205.1">C205.1 General</h4>
							<p class="dot1desc">Where software is integral to the use of telecommunications functions of telecommunications equipment or customer premises equipment and has a user interface, such software shall conform to C205 and applicable requirements in Chapter 5.<br>
							EXCEPTION: Software that is assistive technology and that supports the accessibility services of the platform shall not be required to conform to the requirements in Chapter 5.</p>
						<h4 id="C205.2">C205.2 WCAG Conformance</h4>
							<p class="dot1desc">User interface components, as well as the content of platforms and applications shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).<br>
							EXCEPTIONS: </p>
							<ol>
								<li>Software that is assistive technology and that supports the accessibility services of the platform shall not be required to conform to C205.2.</li>
								<li>Non-Web software shall not be required to conform to the following four Success Criteria in WCAG 2.0: 2.4.1 Bypass Blocks; 2.4.5 Multiple Ways; 3.2.3 Consistent Navigation; and 3.2.4 Consistent Identification.</li>
								<li>Non-Web software shall not be required to conform to Conformance Requirement 3 Complete Processes in WCAG 2.0.</li>
							</ol>
							<div class="dotdot">
								<h5 id="C205.2.1">C205.2.1 Word Substitution when Applying WCAG to Non-Web Software</h5> <p class="dotdotdesc">For non-Web software, wherever the term “Web page” or “page” appears in WCAG 2.0 Level A and AA Success Criteria and Conformance Requirements, the term “software” shall be substituted for the terms “Web page” and “page.” In addition, in Success Criterion 1.4.2, the phrase “in software” shall be substituted for the phrase “on a Web page.”</p>
							</div>
						<h4 id="C205.3">C205.3 Complete Processes for Non-Web Software</h4>
							<p class="dot1desc">Where non-Web software requires multiple steps to accomplish an activity, all software related to the activity to be accomplished shall conform to WCAG 2.0 as specified in C205.2.</p>
					<h3 id="C206-documentation-services">C206 Support Documentation and Services</h3>
						<h4 id="C206.1">C206.1 General</h4>
							<p class="dot1desc">Where support documentation and services are provided for telecommunications equipment and customer premises equipment, manufacturers shall ensure that such documentation and services conform to Chapter 6 and are made available upon request at no additional charge.</p>
			</div> <!-- end 255 Chapter 2 -->
	</div> <!-- end Appendix B -->
	<hr>
	<div class="appendix" id="appendix-c">
		<h1>Appendix C to Part 1194 – Functional Performance Criteria and Technical Requirements</h1>
			<div class="chapter" id="508chapter3">
				<h2>Chapter 3: Functional Performance Criteria</h2>
					<h3 id="301-general">301 General</h3>
						<h4 id="301.1">301.1 Scope</h4>
							<p class="dot1desc">The requirements of Chapter 3 shall apply to ICT where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.</p>
					<h3 id="302-functional-performance-criteria">302 Functional Performance Criteria</h3>
						<h4 id="302.1">302.1 Without Vision</h4>
							<p class="dot1desc">Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that does not require user vision.</p>
						<h4 id="302.2">302.2 With Limited Vision</h4>
							<p class="dot1desc"> Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited vision.</p>
						<h4 id="302.3">302.3 Without Perception of Color</h4>
							<p class="dot1desc"> Where a visual mode of operation is provided, ICT shall provide at least one visual mode of operation that does not require user perception of color.</p>
						<h4 id="302.4">302.4 Without Hearing</h4>
							<p class="dot1desc"> Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that does not require user hearing.</p>
						<h4 id="302.5">302.5 With Limited Hearing</h4>
							<p class="dot1desc"> Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited hearing.</p>
						<h4 id="302.6">302.6 Without Speech</h4>
							<p class="dot1desc"> Where speech is used for input, control, or operation, ICT shall provide at least one mode of operation that does not require user speech.</p>
						<h4 id="302.7">302.7 With Limited Manipulation</h4>
							<p class="dot1desc"> Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that does not require fine motor control or simultaneous manual operations.</p>
						<h4 id="302.8">302.8 With Limited Reach and Strength</h4>
							<p class="dot1desc"> Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that is operable with limited reach and limited strength.</p>
						<h4 id="302.9">302.9 With Limited Language, Cognitive, and Learning Abilities</h4>
							<p class="dot1desc"> ICT shall provide features making its use by individuals with limited cognitive, language, and learning abilities simpler and easier. </p>
            </div> <!-- end FPCchapter3-->
            <hr>
			<div class="chapter" id="508chapter4">
				<h2>Chapter 4: Hardware</h2>
					<h3 id="401-general">401 General</h3>
						<h4 id="401.1">401.1 Scope</h4>
							<p class="dot1desc"> The requirements of Chapter 4 shall apply to ICT that is hardware where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.<br>
							EXCEPTION: Hardware that is assistive technology shall not be required to conform to the requirements of this chapter.</p>
					<h3 id="402-closed-functionality">402 Closed Functionality</h3>
						<h4 id="402.1">402.1 General</h4>
							<p class="dot1desc"> ICT with closed functionality shall be operable without requiring the user to attach or install assistive technology other than personal headsets or other audio couplers, and shall conform to 402.</p>
						<h4 id="402.2">402.2 Speech-Output Enabled</h4>
							<p class="dot1desc"> ICT with a display screen shall be speech-output enabled for full and independent use by individuals with vision impairments.<br>
							EXCEPTIONS: </p>
							<ol>
								<li>Variable message signs conforming to 402.5 shall not be required to be speech-output enabled.</li>
								<li>Speech output shall not be required where ICT display screens only provide status indicators and those indicators conform to 409.</li>
								<li>Where speech output cannot be supported due to constraints in available memory or processor capability, ICT shall be permitted to conform to 409 in lieu of 402.2.</li>
								<li>Audible tones shall be permitted instead of speech output where the content of user input is not displayed as entered for security purposes, including, but not limited to, asterisks representing personal identification numbers.</li>
								<li>Speech output shall not be required for: the machine location; date and time of transaction; customer account number; and the machine identifier or label.</li>
								<li>Speech output shall not be required for advertisements and other similar information unless they convey information that can be used for the transaction being conducted.</li>
							</ol>
							<div class="dotdot">
								<h5 id="402.2.1">402.2.1 Information Displayed On-Screen</h5>
									<p class="dotdotdesc">Speech output shall be provided for all information displayed on-screen.</p>
								<h5 id="402.2.2">402.2.2 Transactional Outputs</h5>
									<p class="dotdotdesc"> Where transactional outputs are provided, the speech output shall audibly provide all information necessary to verify a transaction.</p>
								<h5 id="402.2.3">402.2.3 Speech Delivery Type and Coordination</h5>
									<p class="dotdotdesc">Speech output shall be delivered through a mechanism that is readily available to all users, including, but not limited to, an industry standard connector or a telephone handset. Speech shall be recorded or digitized human, or synthesized. Speech output shall be coordinated with information displayed on the screen.</p>
								<h5 id="402.2.4">402.2.4 User Control</h5>
									<p class="dotdotdesc">Speech output for any single function shall be automatically interrupted when a transaction is selected. Speech output shall be capable of being repeated and paused.</p>
									<h5 id="402.2.5">402.2.5 Braille Instructions</h5>
									<p class="dotdotdesc">Where speech output is required by 402.2, braille instructions for initiating the speech mode of operation shall be provided. Braille shall be contracted and shall conform to 36 CFR part 1191, Appendix D, Section 703.3.1.<br>
									EXCEPTION: Devices for personal use shall not be required to conform to 402.2.5.</p>
							</div>
						<h4 id="402.3">402.3 Volume</h4>
							<p class="dot1desc"> ICT that delivers sound, including speech output required by 402.2, shall provide volume control and output amplification conforming to 402.3.<br>
							EXCEPTION: ICT conforming to 412.2 shall not be required to conform to 402.3.</p>
							<div class="dotdot">
								<h5 id="402.3.1">402.3.1 Private Listening</h5>
									<p class="dotdotdesc">Where ICT provides private listening, it shall provide a mode of operation for controlling the volume. Where ICT delivers output by an audio transducer typically held up to the ear, a means for effective magnetic wireless coupling to hearing technologies shall be provided.</p>
								<h5 id="402.3.2">402.3.2 Non-private Listening</h5>
									<p class="dotdotdesc">Where ICT provides non-private listening, incremental volume control shall be provided with output amplification up to a level of at least 65 dB. A function shall be provided to automatically reset the volume to the default level after every use.</p>
							</div>
						<h4 id="402.4">402.4 Characters on Display Screens</h4>
							<p class="dot1desc"> At least one mode of characters displayed on the screen shall be in a sans serif font. Where ICT does not provide a screen enlargement feature, characters shall be 3/16 inch (4.8 mm) high minimum based on 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.</p>
						<h4 id="402.5">402.5 Characters on Variable Message Signs</h4>
							<p class="dot1desc"> Characters on variable message signs shall conform to section 703.7 Variable Message Signs of ICC A117.1-2009 (incorporated by reference, see 702.6.1).</p>
					<h3 id="403-biometrics">403 Biometrics</h3>
						<h4 id="403.1">403.1 General</h4>
							<p class="dot1desc"> Where provided, biometrics shall not be the only means for user identification or control.<br>
							EXCEPTION: Where at least two biometric options that use different biological characteristics are provided, ICT shall be permitted to use biometrics as the only means for user identification or control.</p>
					<h3 id="404-preservation-information">404 Preservation of Information Provided for Accessibility</h3>
						<h4 id="404.1">404.1 General</h4>
							<p class="dot1desc"> ICT that transmits or converts information or communication shall not remove non-proprietary information provided for accessibility or shall restore it upon delivery.</p>
					<h3 id="405-privacy">405 Privacy</h3>
						<h4 id="405.1">405.1 General</h4>
							<p class="dot1desc"> The same degree of privacy of input and output shall be provided to all individuals. When speech output required by 402.2 is enabled, the screen shall not blank automatically.</p>
					<h3 id="406-standard-connections">406 Standard Connections</h3>
						<h4 id="406.1">406.1 General</h4>
							<p class="dot1desc"> Where data connections used for input and output are provided, at least one of each type of connection shall conform to industry standard non-proprietary formats.</p>
					<h3 id="407-operable-parts">407 Operable Parts</h3>
						<h4 id="407.1">407.1 General</h4>
							<p class="dot1desc"> Where provided, operable parts used in the normal operation of ICT shall conform to 407.</p>
						<h4 id="407.2">407.2 Contrast</h4>
							<p class="dot1desc"> Where provided, keys and controls shall contrast visually from background surfaces. Characters and symbols shall contrast visually from background surfaces with either light characters or symbols on a dark background or dark characters or symbols on a light background.</p>
						<h4 id="407.3">407.3 Input Controls</h4>
							<p class="dot1desc"> At least one input control conforming to 407.3 shall be provided for each function.<br>
							EXCEPTION: Devices for personal use with input controls that are audibly discernable without activation and operable by touch shall not be required to conform to 407.3.</p>
							<div class="dotdot">
								<h5 id="407.3.1">407.3.1 Tactilely Discernible</h5>
									<p class="dotdotdesc">Input controls shall be operable by touch and tactilely discernible without activation.</p>
								<h5 id="407.3.2">407.3.2 Alphabetic Keys</h5>
									<p class="dotdotdesc">Where provided, individual alphabetic keys shall be arranged in a QWERTY-based keyboard layout and the “F” and “J” keys shall be tactilely distinct from the other keys.</p>
								<h5 id="407.3.3">407.3.3 Numeric Keys</h5>
									<p class="dotdotdesc">Where provided, numeric keys shall be arranged in a 12-key ascending or descending keypad layout. The number five key shall be tactilely distinct from the other keys. Where the ICT provides an alphabetic overlay on numeric keys, the relationships between letters and digits shall conform to ITU-T Recommendation E.161 (incorporated by reference, see 702.7.1).</p>
							</div>
						<h4 id="407.4">407.4 Key Repeat</h4>
							<p class="dot1desc"> Where a keyboard with key repeat is provided, the delay before the key repeat feature is activated shall be fixed at, or adjustable to, 2 seconds minimum.</p>
						<h4 id="407.5">407.5 Timed Response</h4>
							<p class="dot1desc"> Where a timed response is required, the user shall be alerted visually, as well as by touch or sound, and shall be given the opportunity to indicate that more time is needed.</p>
						<h4 id="407.6">407.6 Operation</h4>
							<p class="dot1desc"> At least one mode of operation shall be operable with one hand and shall not require tight grasping, pinching, or twisting of the wrist. The force required to activate operable parts shall be 5 pounds (22.2 N) maximum.</p>
						<h4 id="407.7">407.7 Tickets, Fare Cards, and Keycards</h4>
							<p class="dot1desc"> Where tickets, fare cards, or keycards are provided, they shall have an orientation that is tactilely discernible if orientation is important to further use of the ticket, fare card, or keycard.</p>
						<h4 id="407.8">407.8 Reach Height and Depth</h4>
							<p class="dot1desc"> At least one of each type of operable part of stationary ICT shall be at a height conforming to 407.8.2 or 407.8.3 according to its position established by the vertical reference plane specified in 407.8.1 for a side reach or a forward reach. Operable parts used with speech output required by 402.2 shall not be the only type of operable part complying with 407.8 unless that part is the only operable part of its type.</p>
							<div class="dotdot">
								<h5 id="407.8.1">407.8.1 Vertical Reference Plane</h5>
									<p class="dotdotdesc">Operable parts shall be positioned for a side reach or a forward reach determined with respect to a vertical reference plane. The vertical reference plane shall be located in conformance to 407.8.2 or 407.8.3.</p>
									<div class="dotdot">
										<h6 id="407.8.1.1">407.8.1.1 Vertical Plane for Side Reach</h6>
											<p class="dotdotdesc">Where a side reach is provided, the vertical reference plane shall be 48 inches (1220 mm) long minimum.</p>
											<div class="moreinfo">
												<img class="img-large" alt="graphical representation of dimensions for vertical plane side reach" src="{{ site.baseurl }}/images/ict/407-8-1side.PNG">
											</div>
										<h6 id="407.8.1.2">407.8.1.2 Vertical Plane for Forward Reach</h6>
											<p class="dotdotdesc">Where a forward reach is provided, the vertical reference plane shall be 30 inches (760 mm) long minimum.</p>
											<div class="moreinfo">
												<img class="img-large" alt="graphical representation of dimensions for vertical plane forward reach" src="{{ site.baseurl }}/images/ict/407-8-1forward.PNG">
											</div>
									</div>
								<h5 id="407.8.2">407.8.2 Side Reach</h5>
									<p class="dotdotdesc">Operable parts of ICT providing a side reach shall conform to 407.8.2.1 or 407.8.2.2. The vertical reference plane shall be centered on the operable part and placed at the leading edge of the maximum protrusion of the ICT within the length of the vertical reference plane. Where a side reach requires a reach over a portion of the ICT, the height of that portion of the ICT shall be 34 inches (865 mm) maximum.</p>
									<div class="dotdot">
										<h6 id="407.8.2.1">407.8.2.1 Unobstructed Side Reach</h6>
											<p class="dotdotdesc">Where the operable part is located 10 inches (255 mm) or less beyond the vertical reference plane, the operable part shall be 48 inches (1220 mm) high maximum and 15 inches (380 mm) high minimum above the floor.</p>
											<div class="moreinfo">
												<img class="img-large" alt="graphical representation of dimensions for unobstructed side reach" src="{{ site.baseurl }}/images/ict/407-8-2-1.PNG">
											</div>
										<h6 id="407.8.2.2">407.8.2.2 Obstructed Side Reach</h6>
											<p class="dotdotdesc">Where the operable part is located more than 10 inches (255 mm), but not more than 24 inches (610 mm), beyond the vertical reference plane, the height of the operable part shall be 46 inches (1170 mm) high maximum and 15 inches (380 mm) high minimum above the floor. The operable part shall not be located more than 24 inches (610 mm) beyond the vertical reference plane.</p>
											<div class="moreinfo">
												<img class="img-large" alt="graphical representation of dimensions for obstructed side reach" src="{{ site.baseurl }}/images/ict/407-8-2-2.PNG">
											</div>
									</div>
								<h5 id="407.8.3">407.8.3 Forward Reach</h5>
									<p class="dotdotdesc">Operable parts of ICT providing a forward reach shall conform to 407.8.3.1 or 407.8.3.2. The vertical reference plane shall be centered, and intersect with, the operable part. Where a forward reach allows a reach over a portion of the ICT, the height of that portion of the ICT shall be 34 inches (865 mm) maximum.</p>
									<div class="dotdot">
										<h6 id="407.8.3.1">407.8.3.1 Unobstructed Forward Reach</h6>
											<p class="dotdotdesc">Where the operable part is located at the leading edge of the maximum protrusion within the length of the vertical reference plane of the ICT, the operable part shall be 48 inches (1220 mm) high maximum and 15 inches (380 mm) high minimum above the floor.</p>
											<div class="moreinfo">
												<img class="img-large" alt="graphical representation of dimensions for unobstructed forward reach" src="{{ site.baseurl }}/images/ict/407-8-3-1.PNG">
											</div>
										<h6 id="407.8.3.2">407.8.3.2 Obstructed Forward Reach</h6>
											<p class="dotdotdesc">Where the operable part is located beyond the leading edge of the maximum protrusion within the length of the vertical reference plane, the operable part shall conform to 407.8.3.2. The maximum allowable forward reach to an operable part shall be 25 inches (635 mm).</p>
											<div class="moreinfo">
												<img class="img-large" alt="graphical representation of dimensions for obstructed forward reach" src="{{ site.baseurl }}/images/ict/407-8-3-2.PNG">
											</div>
										<div class="dotdot">
											<div id="407.8.3.2.1" role="heading" aria-level="7" class="bold">407.8.3.2.1 Operable Part Height for ICT with Obstructed Forward Reach</div>
												<p>The height of the operable part shall conform to Table 407.8.3.2.1.</p>
												<table class="usa-table">
													<caption>Table 407.8.3.2.1 Operable Part Height for ICT with Obstructed Forward Reach</caption>
													<thead>
														<tr>
															<th scope="col">Reach Depth</th>
															<th scope="col">Operable Part Height</th>
														</tr>
														<tr>
															<th scope="row">Less than 20 inches (510 mm)</td>
															<td>48 inches (1220 mm) maximum</td>
														</tr>
													</thead>
													<tbody>
														<tr>
															<th scope="row">20 inches (510 mm) to 25 inches (635 mm)</td>
															<td>44 inches (1120 mm) maximum</td>
														</tr>
													</tbody>
												</table>
												<div class="moreinfo">
													<img class="img-large" alt="graphical representation of dimensions for operable part height for obstructed forward reach" src="{{ site.baseurl }}/images/ict/407-8-3-2-1.PNG">
												</div>
											<div id="407.8.3.2.2" role="heading" aria-level="7" class="bold">407.8.3.2.2 Knee and Toe Space under ICT with Obstructed Forward Reach</div>
												<p>Knee and toe space under ICT shall be 27 inches (685 mm) high minimum, 25 inches (635 mm) deep maximum, and 30 inches (760 mm) wide minimum and shall be clear of obstructions.</p>
												<div class="moreinfo">
													<img class="img-large" alt="graphical representation of dimensions for knee and toe space for obstructed forward reach" src="{{ site.baseurl }}/images/ict/407-8-3-2-2.PNG">
												</div>
												<p>EXCEPTIONS: </p>
												<ol>
													<li style="list-style-type: decimal;">Toe space shall be permitted to provide a clear height of 9 inches (230 mm) minimum above the floor and a clear depth of 6 inches (150 mm) maximum from the vertical reference plane toward the leading edge of the ICT.
													<div class="moreinfo">
														<img class="img-large" alt="graphical representation of dimensions for knee and toe space for obstructed forward reach exception one" src="{{ site.baseurl }}/images/ict/407-8-3-2-2exc1.PNG">
													</div>
													</li>
													<li style="list-style-type: decimal;">At a depth of 6 inches (150 mm) maximum from the vertical reference plane toward the leading edge of the ICT, space between 9 inches (230 mm) and 27 inches (685 mm) minimum above the floor shall be permitted to reduce at a rate of 1 inch (25 mm) in depth for every 6 inches (150 mm) in height.
													<div class="moreinfo">
														<img class="img-large" alt="graphical representation of dimensions for knee and toe space for obstructed forward reach exception two" src="{{ site.baseurl }}/images/ict/407-8-3-2-2exc2.PNG">
													</div>
													</li>
												</ol>
												<div class="moreinfo">
													<p style="font-style: italic;">Supplemental graphic combining both Exceptions 1 and 2:</p>
													<img class="img-large" alt="graphical representation of dimensions for knee and toe space for obstructed forward reach exceptions one and two" src="{{ site.baseurl }}/images/ict/407-8-3-2-2exc1and2.PNG">
												</div>
										</div>
									</div>
								</div>
					<h3 id="408-display-screens">408 Display Screens</h3>
						<h4 id="408.1">408.1 General</h4>
							<p class="dot1desc"> Where provided, display screens shall conform to 408.</p>
						<h4 id="408.2">408.2 Visibility</h4>
							<p class="dot1desc"> Where stationary ICT provides one or more display screens, at least one of each type of display screen shall be visible from a point located 40 inches (1015 mm) above the floor space where the display screen is viewed.</p>
						<h4 id="408.3">408.3 Flashing</h4>
							<p class="dot1desc"> Where ICT emits lights in flashes, there shall be no more than three flashes in any one-second period.<br>
							EXCEPTION: Flashes that do not exceed the general flash and red flash thresholds defined in WCAG 2.0 (incorporated by reference, see 702.10.1) are not required to conform to 408.3.</p>
					<h3 id="409-status-indicators">409 Status Indicators</h3>
						<h4 id="409.1">409.1 General</h4>
							<p class="dot1desc"> Where provided, status indicators shall be discernible visually and by touch or sound.</p>
					<h3 id="410-color-coding">410 Color Coding</h3>
						<h4 id="410.1">410.1 General</h4>
							<p class="dot1desc"> Where provided, color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.</p>
					<h3 id="411-audible-signals">411 Audible Signals</h3>
						<h4 id="411.1">411.1 General</h4>
							<p class="dot1desc"> Where provided, audible signals or cues shall not be used as the only means of conveying information, indicating an action, or prompting a response</p>
					<h3 id="412-two-way-communication">412 ICT with Two-Way Voice Communication</h3>
						<h4 id="412.1">412.1 General</h4>
							<p class="dot1desc"> ICT that provides two-way voice communication shall conform to 412.</p>
						<h4 id="412.2">412.2 Volume Gain</h4>
							<p class="dot1desc"> ICT that provides two-way voice communication shall conform to 412.2.1 or 412.2.2.</p>
							<div class="dotdot">
								<h5 id="412.2.1">412.2.1 Volume Gain for Wireline Telephones</h5>
									<p class="dotdotdesc">Volume gain conforming to 47 CFR 68.317 shall be provided on analog and digital wireline telephones.</p>
								<h5 id="412.2.2">412.2.2 Volume Gain for Non-Wireline ICT</h5>
									<p class="dotdotdesc">A method for increasing volume shall be provided for non-wireline ICT.</p>
							</div>
						<h4 id="412.3">412.3 Interference Reduction and Magnetic Coupling</h4>
							<p class="dot1desc"> Where ICT delivers output by a handset or other type of audio transducer that is typically held up to the ear, ICT shall reduce interference with hearing technologies and provide a means for effective magnetic wireless coupling in conformance with 412.3.1 or 412.3.2.</p>
							<div class="dotdot">
								<h5 id="412.3.1">412.3.1 Wireless Handsets</h5>
									<p class="dotdotdesc">ICT in the form of wireless handsets shall conform to ANSI/IEEE C63.19-2011 (incorporated by reference, see 702.5.1).</p>
								<h5 id="412.3.2">412.3.2 Wireline Handsets</h5>
									<p class="dotdotdesc">ICT in the form of wireline handsets, including cordless handsets, shall conform to TIA-1083-B (incorporated by reference, see702.9.1).</p>
							</div>
						<h4 id="412.4">412.4 Digital Encoding of Speech</h4>
							<p class="dot1desc"> ICT in IP-based networks shall transmit and receive speech that is digitally encoded in the manner specified by ITU-T Recommendation G.722.2 (incorporated by reference, see 702.7.2) or IETF RFC 6716 (incorporated by reference, see 702.8.1).</p>
						<h4 id="412.5">412.5 Real-Time Text Functionality</h4>
							<p class="dot1desc"> [Reserved].</p>
						<h4 id="412.6">412.6 Caller ID</h4>
							<p class="dot1desc"> Where provided, caller identification and similar telecommunications functions shall be visible and audible.</p>
						<h4 id="412.7">412.7 Video Communication</h4>
							<p class="dot1desc"> Where ICT provides real-time video functionality, the quality of the video shall be sufficient to support communication using sign language.</p>
						<h4 id="412.8">412.8 Legacy TTY Support</h4>
							<p class="dot1desc"> ICT equipment or systems with two-way voice communication that do not themselves provide TTY functionality shall conform to 412.8.</p>
							<div class="dotdot">
								<h5 id="412.8.1">412.8.1 TTY Connectability</h5>
									<p class="dotdotdesc">ICT shall include a standard non-acoustic connection point for TTYs.</p>
								<h5 id="412.8.2">412.8.2 Voice and Hearing Carry Over</h5>
									<p class="dotdotdesc">ICT shall provide a microphone capable of being turned on and off to allow the user to intermix speech with TTY use.</p>
								<h5 id="412.8.3">412.8.3 Signal Compatibility</h5>
									<p class="dotdotdesc">ICT shall support all commonly used cross-manufacturer non-proprietary standard TTY signal protocols where the system interoperates with the Public Switched Telephone Network (PSTN).</p>
								<h5 id="412.8.4">412.8.4 Voice Mail and Other Messaging Systems</h5>
									<p class="dotdotdesc">Where provided, voice mail, auto-attendant, interactive voice response, and caller identification systems shall be usable with a TTY.</p>
							</div>
					<h3 id="413-closed-caption">413 Closed Caption Processing Technologies</h3>
						<h4 id="413.1">413.1 General</h4>
							<p class="dot1desc"> Where ICT displays or processes video with synchronized audio, ICT shall provide closed caption processing technology that conforms to 413.1.1 or 413.1.2.</p>
							<div class="dotdot">
								<h5 id="413.1.1">413.1.1 Decoding and Display of Closed Captions</h5>
									<p class="dotdotdesc">Players and displays shall decode closed caption data and support display of captions.</p>
								<h5 id="413.1.2">413.1.2 Pass-Through of Closed Caption Data</h5>
									<p class="dotdotdesc">Cabling and ancillary equipment shall pass through caption data.</p>
							</div>
					<h3 id="414-audio-description">414 Audio Description Processing Technologies</h3>
						<h4 id="414.1">414.1 General</h4>
							<p class="dot1desc"> Where ICT displays or processes video with synchronized audio, ICT shall provide audio description processing technology conforming to 414.1.1 or 414.1.2.</p>
							<div class="dotdot">
								<h5 id="414.1.1">414.1.1 Digital Television Tuners</h5>
									<p class="dotdotdesc">Digital television tuners shall provide audio description processing that conforms to ATSC A/53 Digital Television Standard, Part 5 (2014) (incorporated by reference, see 702.2.1). Digital television tuners shall provide processing of audio description when encoded as a Visually Impaired (VI) associated audio service that is provided as a complete program mix containing audio description according to the ATSC A/53 standard.</p>
								<h5 id="414.1.2">414.1.2 Other ICT</h5>
									<p class="dotdotdesc">ICT other than digital television tuners shall provide audio description processing.</p>
							</div>
					<h3 id="415-user-controls-captions-audio-descriptions">415 User Controls for Captions and Audio Descriptions</h3>
						<h4 id="415.1">415.1 General</h4>
							<p class="dot1desc"> Where ICT displays video with synchronized audio, ICT shall provide user controls for closed captions and audio descriptions conforming to 415.1.<br>
							EXCEPTION: Devices for personal use shall not be required to conform to 415.1 provided that captions and audio descriptions can be enabled through system-wide platform settings.</p>
							<div class="dotdot">
								<h5 id="415.1.1">415.1.1 Caption Controls</h5>
									<p class="dotdotdesc">Where ICT provides operable parts for volume control, ICT shall also provide operable parts for caption selection.</p>
								<h5 id="415.1.2">415.1.2 Audio Description Controls</h5>
									<p class="dotdotdesc">Where ICT provides operable parts for program selection, ICT shall also provide operable parts for the selection of audio description.</p>
							</div>
            </div> <!-- end Hardware Chapter 4 -->
            <hr>
			<div class="chapter" id="508chapter5">
				<h2>Chapter 5: Software</h2>
					<h3 id="501-general">501 General</h3>
						<h4 id="501.1">501.1 Scope</h4>
							<p class="dot1desc"> The requirements of Chapter 5 shall apply to software where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.<br>
							EXCEPTION: Where Web applications do not have access to platform accessibility services and do not include components that have access to platform accessibility services, they shall not be required to conform to 502 or 503 provided that they conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).</p>
					<h3 id="502-interoperability-assistive-technology">502 Interoperability with Assistive Technology</h3>
						<h4 id="502.1">502.1 General</h4>
							<p class="dot1desc"> Software shall interoperate with assistive technology and shall conform to 502.<br>
							EXCEPTION: ICT conforming to 402 shall not be required to conform to 502.</p>
						<h4 id="502.2">502.2 Documented Accessibility Features</h4>
							<p class="dot1desc"> Software with platform features defined in platform documentation as accessibility features shall conform to 502.2.</p>
							<div class="dotdot">
								<h5 id="502.2.1">502.2.1 User Control of Accessibility Features</h5>
									<p class="dotdotdesc"> Platform software shall provide user control over platform features that are defined in the platform documentation as accessibility features.</p>
								<h5 id="502.2.2">502.2.2 No Disruption of Accessibility Features</h5>
									<p class="dotdotdesc"> Software shall not disrupt platform features that are defined in the platform documentation as accessibility features.</p>
							</div>
						<h4 id="502.3">502.3 Accessibility Services</h4>
							<p class="dot1desc"> Platform software and software tools that are provided by the platform developer shall provide a documented set of accessibility services that support applications running on the platform to interoperate with assistive technology and shall conform to 502.3. Applications that are also platforms shall expose the underlying platform accessibility services or implement other documented accessibility services.</p>
							<div class="dotdot">
								<h5 id="502.3.1">502.3.1 Object Information</h5>
									<p class="dotdotdesc"> The object role, state(s), properties, boundary, name, and description shall be programmatically determinable.</p>
								<h5 id="502.3.2">502.3.2 Modification of Object Information</h5>
									<p class="dotdotdesc"> States and properties that can be set by the user shall be capable of being set programmatically, including through assistive technology.</p>
								<h5 id="502.3.3">502.3.3 Row, Column, and Headers</h5>
									<p class="dotdotdesc"> If an object is in a data table, the occupied rows and columns, and any headers associated with those rows or columns, shall be programmatically determinable.</p>
								<h5 id="502.3.4">502.3.4 Values</h5>
									<p class="dotdotdesc"> Any current value(s), and any set or range of allowable values associated with an object, shall be programmatically determinable.</p>
								<h5 id="502.3.5">502.3.5 Modification of Values</h5>
									<p class="dotdotdesc"> Values that can be set by the user shall be capable of being set programmatically, including through assistive technology.</p>
								<h5 id="502.3.6">502.3.6 Label Relationships</h5>
									<p class="dotdotdesc"> Any relationship that a component has as a label for another component, or of being labeled by another component, shall be programmatically determinable.</p>
								<h5 id="502.3.7">502.3.7 Hierarchical Relationships</h5>
									<p class="dotdotdesc"> Any hierarchical (parent-child) relationship that a component has as a container for, or being contained by, another component shall be programmatically determinable.</p>
								<h5 id="502.3.8">502.3.8 Text</h5>
									<p class="dotdotdesc"> The content of text objects, text attributes, and the boundary of text rendered to the screen, shall be programmatically determinable.</p>
								<h5 id="502.3.9">502.3.9 Modification of Text</h5>
									<p class="dotdotdesc"> Text that can be set by the user shall be capable of being set programmatically, including through assistive technology.</p>
								<h5 id="502.3.10">502.3.10 List of Actions</h5>
									<p class="dotdotdesc"> A list of all actions that can be executed on an object shall be programmatically determinable.</p>
								<h5 id="502.3.11">502.3.11 Actions on Objects</h5>
									<p class="dotdotdesc"> Applications shall allow assistive technology to programmatically execute available actions on objects.</p>
								<h5 id="502.3.12">502.3.12 Focus Cursor</h5>
									<p class="dotdotdesc"> Applications shall expose information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface components.</p>
								<h5 id="502.3.13">502.3.13 Modification of Focus Cursor</h5>
									<p class="dotdotdesc"> Focus, text insertion point, and selection attributes that can be set by the user shall be capable of being set programmatically, including through the use of assistive technology.</p>
								<h5 id="502.3.14">502.3.14 Event Notification</h5>
									<p class="dotdotdesc"> Notification of events relevant to user interactions, including but not limited to, changes in the component’s state(s), value, name, description, or boundary, shall be available to assistive technology.</p>
							</div>
						<h4 id="502.4">502.4 Platform Accessibility Features</h4>
							<p class="dot1desc"> Platforms and platform software shall conform to the requirements in ANSI/HFES 200.2, Human Factors Engineering of Software User Interfaces — Part 2: Accessibility (2008) (incorporated by reference, see 702.4.1) listed below:</p>
							<div class="dotdot">
								<ol>
									<li>Section 9.3.3 Enable sequential entry of multiple (chorded) keystrokes;</li>
									<li>Section 9.3.4 Provide adjustment of delay before key acceptance;</li>
									<li>Section 9.3.5 Provide adjustment of same-key double-strike acceptance;</li>
									<li>Section 10.6.7 Allow users to choose visual alternative for audio output;</li>
									<li>Section 10.6.8 Synchronize audio equivalents for visual events;</li>
									<li>Section 10.6.9 Provide speech output services; and</li>
									<li>Section 10.7.1 Display any captions provided.</li>
								</ol>
							</div>

					<h3 id="503-applications">503 Applications</h3>
						<h4 id="503.1">503.1 General</h4><p class="dot1desc"> Applications shall conform to 503.</p>
						<h4 id="503.2">503.2 User Preferences</h4>
							<p class="dot1desc"> Applications shall permit user preferences from platform settings for color, contrast, font type, font size, and focus cursor.<br>
							EXCEPTION: Applications that are designed to be isolated from their underlying platform software, including Web applications, shall not be required to conform to 503.2.</p>
						<h4 id="503.3">503.3 Alternative User Interfaces</h4>
							<p class="dot1desc"> Where an application provides an alternative user interface that functions as assistive technology, the application shall use platform and other industry standard accessibility services.</p>
						<h4 id="503.4">503.4 User Controls for Captions and Audio Description</h4>
							<p class="dot1desc"> Where ICT displays video with synchronized audio, ICT shall provide user controls for closed captions and audio descriptions conforming to 503.4.</p>
							<div class="dotdot">
								<h5 id="503.4.1">503.4.1 Caption Controls</h5>
									<p class="dotdotdesc"> Where user controls are provided for volume adjustment, ICT shall provide user controls for the selection of captions at the same menu level as the user controls for volume or program selection.</p>
								<h5 id="503.4.2">503.4.2 Audio Description Controls</h5>
									<p class="dotdotdesc"> Where user controls are provided for program selection, ICT shall provide user controls for the selection of audio descriptions at the same menu level as the user controls for volume or program selection.</p>
							</div>
					<h3 id="504-authoring-tools">504 Authoring Tools</h3>
						<h4 id="504.1">504.1 General</h4>
							<p class="dot1desc"> Where an application is an authoring tool, the application shall conform to 504 to the extent that information required for accessibility is supported by the destination format.</p>
						<h4 id="504.2">504.2 Content Creation or Editing</h4>
							<p class="dot1desc">Authoring tools shall provide a mode of operation to create or edit content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1) for all supported features and, as applicable, to file formats supported by the authoring tool. Authoring tools shall permit authors the option of overriding information required for accessibility.<br>
							EXCEPTION: Authoring tools shall not be required to conform to 504.2 when used to directly edit plain text source code.</p>
							<div class="dotdot">
								<h5 id="504.2.1">504.2.1 Preservation of Information Provided for Accessibility in Format Conversion</h5>
									<p class="dotdotdesc"> Authoring tools shall, when converting content from one format to another or saving content in multiple formats, preserve the information required for accessibility to the extent that the information is supported by the destination format.</p>
								<h5 id="504.2.2">504.2.2 PDF Export</h5>
									<p class="dotdotdesc"> Authoring tools capable of exporting PDF files that conform to ISO 32000-1:2008 (PDF 1.7) shall also be capable of exporting PDF files that conform to ANSI/AIIM/ISO 14289-1:2016 (PDF/UA-1) (incorporated by reference, see 702.3.1).</p>
							</div>
						<h4 id="504.3">504.3 Prompts</h4>
							<p class="dot1desc"> Authoring tools shall provide a mode of operation that prompts authors to create content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1) for supported features and, as applicable, to file formats supported by the authoring tool.</p>
						<h4 id="504.4">504.4 Templates</h4>
							<p class="dot1desc"> Where templates are provided, templates allowing content creation that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1) shall be provided for a range of template uses for supported features and, as applicable, to file formats supported by the authoring tool.</p>
            </div> <!-- end 508 Chapter 5 -->
            <hr>
			<div class="chapter" id="508chapter6">
				<h2>Chapter 6: Support Documentation and Services</h2>
					<h3 id="601-general">601 General</h3>
						<h4 id="601.1">601.1 Scope</h4>
							<p class="dot1desc"> The technical requirements in Chapter 6 shall apply to ICT support documentation and services where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.</p>
					<h3 id="602-support-documentation">602 Support Documentation</h3>
						<h4 id="602.1">602.1 General</h4>
							<p class="dot1desc"> Documentation that supports the use of ICT shall conform to 602.</p>
						<h4 id="602.2">602.2 Accessibility and Compatibility Features</h4>
							<p class="dot1desc"> Documentation shall list and explain how to use the accessibility and compatibility features required by Chapters 4 and 5. Documentation shall include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.</p>
						<h4 id="602.3">602.3 Electronic Support Documentation</h4>
							<p class="dot1desc"> Documentation in electronic format, including Web-based self-service support, shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).</p>
						<h4 id="602.4">602.4 Alternate Formats for Non-Electronic Support Documentation</h4>
							<p class="dot1desc"> Where support documentation is only provided in non-electronic formats, alternate formats usable by individuals with disabilities shall be provided upon request.</p>
					<h3 id="603-support-services">603 Support Services</h3>
						<h4 id="603.1">603.1 General</h4>
							<p class="dot1desc"> ICT support services including, but not limited to, help desks, call centers, training services, and automated self-service technical support, shall conform to 603.</p>
						<h4 id="603.2">603.2 Information on Accessibility and Compatibility Features</h4>
							<p class="dot1desc"> ICT support services shall include information on the accessibility and compatibility features required by 602.2.</p>
						<h4 id="603.3">603.3 Accommodation of Communication Needs</h4>
							<p class="dot1desc"> Support services shall be provided directly to the user or through a referral to a point of contact. Such ICT support services shall accommodate the communication needs of individuals with disabilities.</p>
            </div> <!-- end 508 chapter 6 -->
            <hr>
			<div class="chapter" id="508chapter7">
				<h2>Chapter 7: Referenced Standards</h2>
					<h3 id="701-general">701 General</h3>
						<h4 id="701.1">701.1 Scope</h4>
							<p class="dot1desc"> The standards referenced in Chapter 7 shall apply to ICT where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.</p>
					<h3 id="702-incorporation-by-reference">702 Incorporation by Reference</h3>
						<h4 id="702.1">702.1 Approved IBR Standards</h4>
							<p class="dot1desc"> The Director of the Office of the Federal Register has approved these standards for incorporation by reference into this part in accordance with 5 U.S.C. 552(a) and 1 CFR part 51. Copies of the referenced standards may be inspected at the U.S. Access Board, 1331 F Street, NW, Suite 1000, Washington, DC 20004, (202) 272-0080, and may also be obtained from the sources listed below. They are also available for inspection at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, call 202–741–6030 or go to <a href="https://www.archives.gov/federal-register/cfr/ibr-locations.html" target="_blank"  rel="noopener noreferrer">National Archives Code of Federal Regulations Incorporation by Reference</a>.</p>
						<h4 id="702.2">702.2 Advanced Television Systems Committee (ATSC)</h4>
							<p class="dot1desc"> Copies of the referenced standard may be obtained from the <a href="http://www.atsc.org" target="_blank"  rel="noopener noreferrer">Advanced Television Systems Committee</a>, 1776 K Street NW, Suite 200, Washington, DC 20006–2304.</p>
							<div class="dotdot">
								<h5 id="702.2.1">702.2.1 ATSC A/53 Part 5:2014, Digital Television Standard, Part 5—AC-3 Audio System Characteristics, August 28, 2014</h5>
									<p class="dotdotdesc">IBR approved for Appendix C, Section 414.1.1.</p>
							</div>
						<h4 id="702.3">702.3 Association for Information and Image Management (AIIM)</h4>
							<p class="dot1desc"> Copies of the referenced standard may be obtained from AIIM,1100 Wayne Ave., Ste. 1100, Silver Spring, Maryland 20910.</p>
							<div class="dotdot">
								<h5 id="702.3.1">702.3.1 ANSI/AIIM/ISO 14289-1-2016, Document Management Applications - Electronic Document File Format Enhancement for Accessibility - Part 1: Use of ISO 32000-1 (PDF/UA-1), ANSI-approved February 8, 2016</h5>
										<p class="dotdotdesc">IBR approved for Appendix C, Section 504.2.2.</p>
							</div>
						<h4 id="702.4">702.4 Human Factors and Ergonomics Society (HFES)</h4>
							<p class="dot1desc"> Copies of the referenced standard may be obtained from the Human Factors and Ergonomics Society, P.O. Box 1369, Santa Monica, CA 90406–1369.</p>
							<div class="dotdot">
								<h5 id="702.4.1">702.4.1 ANSI/HFES 200.2, Human Factors Engineering of Software User Interfaces — Part 2: Accessibility, copyright 2008</h5>
										<p class="dotdotdesc">IBR approved for Appendix C, Section 502.4.</p>
							</div>
						<h4 id="702.5">702.5 Institute of Electrical and Electronics Engineers (IEEE)</h4>
							<p class="dot1desc"> Copies of the referenced standard may be obtained from the <a href="http://www.ieee.org" target="_blank"  rel="noopener noreferrer">Institute of Electrical and Electronics Engineers</a>, 10662 Los Vaqueros Circle, P.O. Box 3014, Los Alamitos, CA 90720–1264.</p>
							<div class="dotdot">
								<h5 id="702.5.1">702.5.1 ANSI/IEEE C63.19-2011, American National Standard for Methods of Measurement of Compatibility between Wireless Communications Devices and Hearing Aids, May 27, 2011</h5>
									<p class="dotdotdesc">IBR approved for Appendix C, Section 412.3.1.</p>
							</div>
						<h4 id="702.6">702.6 International Code Council (ICC)</h4>
							<p class="dot1desc"> Copies of the referenced standard may be obtained from <a href="http://www.iccsafe.org" target="_blank"  rel="noopener noreferrer">ICC Publications</a>, 4051 W. Flossmoor Road, Country Club Hills, IL 60478–5795.</p>
							<div class="dotdot">
								<h5 id="702.6.1">702.6.1 ICC A117.1-2009, Accessible and Usable Buildings and Facilities, approved October 20, 2010</h5>
									<p class="dotdotdesc">IBR approved for Appendix C, Section 402.5.</p>
							</div>
						<h4 id="702.7">702.7 International Telecommunications Union Telecommunications Standardization Sector (ITU-T)</h4>
							<p class="dot1desc"> Copies of the referenced standards may be obtained from the <a href="http://www.itu.int/en/ITU-T" target="_blank"  rel="noopener noreferrer">International Telecommunication Union</a>, Telecommunications Standardization Sector, Place des Nations CH-1211, Geneva 20, Switzerland.</p>
							<div class="dotdot">
								<h5 id="702.7.1">702.7.1 ITU-T Recommendation E.161, Series E. Overall Network Operation, Telephone Service, Service Operation and Human Factors—International operation - Numbering plan of the international telephone service, Arrangement of digits, letters and symbols on telephones and other devices that can be used for gaining access to a telephone network, February 2001</h5>
									<p class="dotdotdesc">IBR approved for Appendix C, Section 407.3.3.</p>
								<h5 id="702.7.2">702.7.2 ITU-T Recommendation G.722.2, Series G. Transmission Systems and Media, Digital Systems and Networks – Digital terminal equipment – Coding of analogue signals by methods other than PCM, Wideband coding of speech at around 16 kbit/s using Adaptive Multi-Rate Wideband (AMR-WB), July 2003</h5>
									<p class="dotdotdesc">IBR approved for Appendix C, Section 412.4.</p>
							</div>
						<h4 id="702.8">702.8 Internet Engineering Task Force (IETF)</h4>
							<p class="dot1desc"> Copies of the referenced standard may be obtained from the <a href="http://www.ietf.org" target="_blank"  rel="noopener noreferrer">Internet Engineering Task Force</a>.</p>
							<div class="dotdot">
								<h5 id="702.8.1">702.8.1 IETF RFC 6716, Definition of the Opus Codec, September 2012, J.M. Valin, Mozilla Corporation, K. Vos, Skype Technologies S.A., T. Terriberry, Mozilla Corporation</h5>
									<p class="dotdotdesc">IBR approved for Appendix C, Section 412.4.</p>
							</div>
						<h4 id="702.9">702.9 Telecommunications Industry Association (TIA)</h4>
							<p class="dot1desc"> Copies of the referenced standard, published by the Telecommunications Industry Association, may be obtained from <a href="http://global.ihs.com" target="_blank"  rel="noopener noreferrer">IHS Markit</a>, 15 Inverness Way East, Englewood, CO 80112.</p>
							<div class="dotdot">
								<h5 id="702.9.1">702.9.1 TIA-1083-B, Telecommunications—Communications Products—Handset Magnetic Measurement Procedures and Performance Requirements, October 2015</h5>
									<p class="dotdotdesc">IBR approved for Appendix C, Section 412.3.2.</p>
							</div>
						<h4 id="702.10">702.10 Worldwide Web Consortium (W3C)</h4><p class="dot1desc"> Copies of the referenced standard may be obtained from the W3C Web Accessibility Initiative, Massachusetts Institute of Technology, 32 Vassar Street, Room 32-G515, Cambridge, MA 02139.</p>
							<div class="dotdot">
								<h5 id="702.10.1">702.10.1 <a href="http://www.w3.org/TR/WCAG20" target="_blank"  rel="noopener noreferrer">WCAG 2.0, Web Content Accessibility Guidelines</a>, W3C Recommendation, December 11, 2008</h5>
									<p class="dotdotdesc">IBR approved for: Appendix A (Section 508 of the Rehabilitation Act: Application and Scoping Requirements), Sections E205.4, E205.4 Exception, E205.4.1, E207.2, E207.2 Exception 2, E207.2 Exception 3, E207.2.1, E207.3; Appendix B (Section 255 of the Communications Act: Application and Scoping Requirements), C203.1, C203.1 Exception, C203.1.1, C205.2, C205.2 Exception 2, C205.2 Exception 3, C205.2.1, C205.3; and Appendix C (Functional Performance Criteria and Technical Requirements), 408.3 Exception, 501.1 Exception, 504.2, 504.3, 504.4, and 602.3.</p>
							</div>
			</div> <!-- end 508 chapter 7 -->
	</div> <!-- end Appendix C -->
	<hr>
	{% assign ict-chapters = site.ict | where: "title","Original 508 Standards (2000)" %}
	{% for chapter in ict-chapters %}
		<div class="usa-prose">{{chapter.content}}</div>
	{% endfor %}
	<!-- <hr>
	{% assign ict-chapters = site.ict | where: "title","Preamble to the Final Rule" %}
	{% for chapter in ict-chapters %}
		<div class="usa-prose">{{chapter.content}}</div>
	{% endfor %} -->
	<hr>
	{% assign ict-chapters = site.ict | where: "title","FAQs" %}
	{% for chapter in ict-chapters %}
		<div class="usa-prose">{{chapter.content | markdownify}}</div>
	{% endfor %}

</div> <!-- end -->