#wcag 2.0 compliance | Explore Tumblr Posts and Blogs

xneontragedyx · 5 months

Text

Skip to Table of Contents

U.S. flag

An official website of the United States government

Here’s how you know

Notice

The Public Right-of-Way Accessibility Guidelines (PROWAG) rulemaking has concluded. The PROWAG final rule has been published in the Federal Register. Please visit the Access Board’s PROWAG page for the guidelines.

USAB star logo

U.S. Access Board

Advancing Full Access and Inclusion for All

Information and Communication Technology

Revised 508 Standards and 255 Guidelines

PDF

About the ICT Accessibility 508 Standards and 255 Guidelines

These standards address access to information and communication technology (ICT) under Section 508 of the Rehabilitation Act and Section 255 of the Communications Act.

Section 508 of the Rehabilitation Act charges the Access Board with developing and promulgating this rule. The statute also charges the Access Board with providing Technical Assistance on Section 508, which is provided through webinars, trainings, and in close collaboration with GSA and materials available from Section508.gov.

Section 508 requires access to ICT developed, procured, maintained, or used by federal agencies. Examples include computers, telecommunications equipment, multifunction office machines such as copiers that also operate as printers, software, websites, information kiosks and transaction machines, and electronic documents. The Section 508 Standards, which are part of the Federal Acquisition Regulation, ensure access for people with physical, sensory, or cognitive disabilities.

The Section 255 Guidelines cover telecommunications equipment and customer-premises equipment — such as telephones, cell phones, routers, set-top boxes, and computers with modems, interconnected Voice over Internet Protocol products, and software integral to the operation of telecommunications function of such equipment.

Background

February 3, 1998 – The Board publishes the original Telecommunications Act Accessibility Guidelines.

December 21, 2000 – The Board issues the original Section 508 Standards.

July 6, 2006 – The Board organizes TEITAC, the Telecommunications and Electronic and Information Technology Advisory Committee, to assist in updating the Section 508 Standards and Telecommunications Act Guidelines.

April 3, 2008 – The Advisory Committee presents its final report to the Board.

March 22, 2010 – The Board releases a draft proposed rule for public comment, docket ATBCB-2010-0001.

December 8, 2011 – The Board issues a revised draft proposed rule for public comment, docket ATBCB-2011-0007.

February 27, 2015 – The Board ICT proposed rule for public comment, docket ATBCB-2015-0002.

January 18, 2017 – The Board issues the final rule, docket ATBCB-2015-0002-014.

January 22, 2018 – The Board issues correction to the final rule to restore provisions for TTY access, docket document ATBCB-2015-0002-0146.

Additional Resources

Section508.gov — GSA’s Government-wide IT Accessibility Program

Section 508 of the Rehabilitation Act (29 U.S.C. §794d)

Final Regulatory Impact Analysis (FRIA)

Comparison Table of WCAG 2.0 to Original 508 Standards

Mapping of WCAG 2.0 to Functional Performance Criteria

ICT Testing Baseline for Web Accessibility

Appendix A to Part 1194 – Section 508 of the Rehabilitation Act: Application and Scoping Requirements

508 Chapter 1: Application and Administration

E101 General

E101.1 Purpose

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).

E101.2 Equivalent Facilitation

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.

E101.3 Conventional Industry Tolerances

Dimensions are subject to conventional industry tolerances except where dimensions are stated as a range with specific minimum or maximum end points.

E101.4 Units of Measurement

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.

E102 Referenced Standards

E102.1 Application

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.

E103 Definitions

E103.1 Terms Defined in Referenced Standards

Terms defined in referenced standards and not defined in E103.4 shall have the meaning as defined in the referenced standards.

E103.2 Undefined Terms

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.

E103.3 Interchangeability

Words, terms, and phrases used in the singular include the plural and those used in the plural include the singular.

E103.4 Defined Terms

For the purpose of the Revised 508 Standards, the terms defined in E103.4 have the indicated meaning.

Agency

Any agency or department of the United States as defined in 44 U.S.C. 3502, and the United States Postal Service.

Alteration

A change to existing ICT that affects interoperability, the user interface, or access to information or data.

Application.

Software designed to perform, or to help the user to perform, a specific task or tasks.

Assistive Technology (AT)

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.

Audio Description.

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”.

Authoring Tool

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.

Closed Functionality

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.

Content

Electronic information and data, as well as the encoding that defines its structure, presentation, and interactions.

Document

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.

Existing ICT

ICT that has been procured, maintained or used on or before January 18, 2018.

Hardware

A tangible device, equipment, or physical component of ICT, such as telephones, computers, multifunction copy machines, and keyboards.

Information Technology

Shall have the same meaning as the term “information technology” set forth in 40 U.S.C. 11101(6).

Information and Communication Technology (ICT)

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.

Keyboard

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.

Label

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.

A set of selectable options.

Name

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.

Non-Web Document

A document that is not: a Web page, embedded in a Web page, or used in the rendering or functioning of Web pages.

Non-Web Software

Software that is not: a Web page, not embedded in a Web page, and not used in the rendering or functioning of Web pages.

Operable Part

Hardware-based user controls for activating, deactivating, or adjusting ICT.

Platform Accessibility Services

Services provided by a platform enabling interoperability with assistive technology. Examples are Application Programming Interfaces (API) and the Document Object Model (DOM).

Platform Software

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.

Programmatically Determinable

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.

Public Facing

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.

Real-Time Text (RTT)

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.

Revised 508 Standards

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).

Software

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.

Software Tools

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®.

Telecommunications

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.

Terminal

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.

Text

A sequence of characters that can be programmatically determined and that expresses something in human language.

TTY

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.

Variable Message Signs (VMS)

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.

Voice over Internet Protocol (VoIP)

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.

Web page

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.

508 Chapter 2: Scoping Requirements

E201 Application

E201.1 Scope

ICT that is procured, developed, maintained, or used by agencies shall conform to the Revised 508 Standards.

E202 General Exceptions

E202.1 General

ICT shall be exempt from compliance with the Revised 508 Standards to the extent specified by E202.

E202.2 Legacy ICT

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.

E202.3 National Security Systems

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).

E202.4 Federal Contracts

ICT acquired by a contractor incidental to a contract shall not be required to conform to the Revised 508 Standards.

E202.5 ICT Functions Located in Maintenance or Monitoring Spaces

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.

E202.6 Undue Burden or Fundamental Alteration

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.

E202.6.1 Basis for a Determination of Undue Burden

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.

E202.6.2 Required Documentation

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.

E202.6.3 Alternative Means

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.

E202.7 Best Meets

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.

E202.7.1 Required Documentation

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.

E202.7.2 Alternative Means

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.

E203 Access to Functionality

E203.1 General

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:

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

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.

E203.2 User Needs

When agencies procure, develop, maintain or use ICT they shall identify the needs of users with disabilities to determine:

How users with disabilities will perform the functions supported by the ICT; and

How the ICT will be developed, installed, configured, and maintained to support users with disabilities.

E204 Functional Performance Criteria

E204.1 General

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.

E205 Electronic Content

E205.1 General

Electronic content shall comply with E205.

E205.2 Public Facing

Electronic content that is public facing shall conform to the accessibility requirements specified in E205.4.

E205.3 Agency Official Communication

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:

An emergency notification;

An initial or final decision adjudicating an administrative claim or proceeding;

An internal or external program or policy announcement;

A notice of benefits, program eligibility, employment opportunity, or personnel action;

A formal acknowledgement of receipt;

A survey questionnaire;

A template or form;

Educational or training materials; or

Intranet content designed as a Web page.

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.

E205.4 Accessibility Standard

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).

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.

E205.4.1 Word Substitution when Applying WCAG to Non-Web Documents

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”.

E206 Hardware

E206.1 General

Where components of ICT are hardware and transmit information or have a user interface, such components shall conform to the requirements in Chapter 4.

E207 Software

E207.1 General

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.

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.

E207.2 WCAG Conformance

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).

EXCEPTIONS:

Software that is assistive technology and that supports the accessibility services of the platform shall not be required to conform to E207.2.

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.

Non-Web software shall not be required to conform to Conformance Requirement 3 Complete Processes in WCAG 2.0.

E207.2.1 Word Substitution when Applying WCAG to Non-Web Software

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.”

E207.3 Complete Processes for Non-Web Software

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.

E208 Support Documentation and Services

E208.1 General

Where an agency provides support documentation or services for ICT, such documentation and services shall conform to the requirements in Chapter 6.

Appendix B to Part 1194 – Section 255 of the Communications Act: Application and Scoping Requirements

255 Chapter 1: Application and Administration

C101 General

C101.1 Purpose

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).

C101.2 Equivalent Facilitation

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.

C101.3 Conventional Industry Tolerances

Dimensions are subject to conventional industry tolerances except where dimensions are stated as a range with specific minimum or maximum end points.

C101.4 Units of Measurement

C102 Referenced Standards

C102.1 Application

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.

C103 Definitions

C103.1 Terms Defined in Referenced Standards

Terms defined in referenced standards and not defined in C103.4 shall have the meaning as defined in the referenced standards.

C103.2 Undefined Terms

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.

C103.3 Interchangeability

Words, terms, and phrases used in the singular include the plural and those used in the plural include the singular.

C103.4 Defined Terms

For the purpose of the Revised 255 Guidelines, the terms defined in C103.4 have the indicated meaning.

Application

Software designed to perform, or to help the user perform, a specific task or tasks.

Assistive Technology (AT)

Audio Description

Authoring Tool

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.

Closed Functionality

Characteristics that limit functionality or prevent a user from attaching or installing assistive technology.

Content

Electronic information and data, as well as the encoding that defines its structure, presentation, and interactions.

Customer Premises Equipment (CPE)

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).

Document

Hardware

A tangible device, equipment, or physical component of ICT, such as telephones, computers, multifunction copy machines, and keyboards.

Information and Communication Technology (ICT)

Keyboard

Label

Manufacturer

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.

A set of selectable options.

Name

Non-Web Document

A document that is not: a Web page, embedded in a Web page, or used in the rendering or functioning of Web pages.

Non-Web Software

Software that is not: a Web page, not embedded in a Web page, and not used in the rendering or functioning of Web pages.

Operable Part

Hardware-based user controls for activating, deactivating, or adjusting ICT.

Platform Accessibility Services

Services provided by a platform enabling interoperability with assistive technology. Examples are Application Programming Interfaces (API) and the Document Object Model (DOM).

Platform Software

Programmatically Determinable

Real-Time Text (RTT)

Revised 255 Guidelines

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).

Software

Software Tools

Specialized Customer Premises Equipment

Assistive technology used by individuals with disabilities to originate, route, or terminate telecommunications or interconnected VoIP service. Examples are TTYs and amplified telephones.

Telecommunications

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.

Telecommunications Equipment

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.

Terminal

Text

A sequence of characters that can be programmatically determined and that expresses something in human language.

TTY

Variable Message Signs (VMS)

Voice over Internet Protocol (VoIP)

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.

Web page

255 Chapter 2: Scoping Requirements

C201 Application

C201.1 Scope

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.

C201.2. Readily Achievable

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.

C201.3 Access to Functionality

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.

C201.4 Prohibited Reduction of Accessibility, Usability, and Compatibility

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.

EXCEPTION: Discontinuation of a product shall not be prohibited.

C201.5 Design, Development, and Fabrication

Manufacturers shall evaluate the accessibility, usability, and interoperability of telecommunications equipment and customer premises equipment during its product design, development, and fabrication.

C202 Functional Performance Criteria

C202.1 General

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.

C203 Electronic Content

C203.1 General

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).

C203.1.1 Word Substitution when Applying WCAG to Non-Web Documents

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.”

C204 Hardware

C204.1 General

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.

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.

C205 Software

C205.1 General

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.

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.

C205.2 WCAG Conformance

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).

EXCEPTIONS:

Software that is assistive technology and that supports the accessibility services of the platform shall not be required to conform to C205.2.

Non-Web software shall not be required to conform to Conformance Requirement 3 Complete Processes in WCAG 2.0.

C205.2.1 Word Substitution when Applying WCAG to Non-Web Software

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.”

C205.3 Complete Processes for Non-Web Software

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.

C206 Support Documentation and Services

C206.1 General

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.

Appendix C to Part 1194 – Functional Performance Criteria and Technical Requirements

Chapter 3: Functional Performance Criteria

301 General

301.1 Scope

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.

302 Functional Performance Criteria

302.1 Without Vision

Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that does not require user vision.

302.2 With Limited Vision

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.

302.3 Without Perception of Color

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.

302.4 Without Hearing

Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that does not require user hearing.

302.5 With Limited Hearing

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.

302.6 Without Speech

Where speech is used for input, control, or operation, ICT shall provide at least one mode of operation that does not require user speech.

302.7 With Limited Manipulation

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.

302.8 With Limited Reach and Strength

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.

302.9 With Limited Language, Cognitive, and Learning Abilities

ICT shall provide features making its use by individuals with limited cognitive, language, and learning abilities simpler and easier.

Chapter 4: Hardware

401 General

401.1 Scope

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.

EXCEPTION: Hardware that is assistive technology shall not be required to conform to the requirements of this chapter.

402 Closed Functionality

402.1 General

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.

402.2 Speech-Output Enabled

ICT with a display screen shall be speech-output enabled for full and independent use by individuals with vision impairments.

EXCEPTIONS:

Variable message signs conforming to 402.5 shall not be required to be speech-output enabled.

Speech output shall not be required where ICT display screens only provide status indicators and those indicators conform to 409.

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.

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.

Speech output shall not be required for: the machine location; date and time of transaction; customer account number; and the machine identifier or label.

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.

402.2.1 Information Displayed On-Screen

Speech output shall be provided for all information displayed on-screen.

402.2.2 Transactional Outputs

Where transactional outputs are provided, the speech output shall audibly provide all information necessary to verify a transaction.

402.2.3 Speech Delivery Type and Coordination

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.

402.2.4 User Control

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.

402.2.5 Braille Instructions

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.

EXCEPTION: Devices for personal use shall not be required to conform to 402.2.5.

402.3 Volume

ICT that delivers sound, including speech output required by 402.2, shall provide volume control and output amplification conforming to 402.3.

EXCEPTION: ICT conforming to 412.2 shall not be required to conform to 402.3.

402.3.1 Private Listening

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.

402.3.2 Non-private Listening

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.

402.4 Characters on Display Screens

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.

402.5 Characters on Variable Message Signs

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).

403 Biometrics

403.1 General

Where provided, biometrics shall not be the only means for user identification or control.

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.

404 Preservation of Information Provided for Accessibility

404.1 General

ICT that transmits or converts information or communication shall not remove non-proprietary information provided for accessibility or shall restore it upon delivery.

405 Privacy

405.1 General

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.

406 Standard Connections

406.1 General

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.

407 Operable Parts

407.1 General

Where provided, operable parts used in the normal operation of ICT shall conform to 407.

407.2 Contrast

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.

407.3 Input Controls

At least one input control conforming to 407.3 shall be provided for each function.

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.

407.3.1 Tactilely Discernible

Input controls shall be operable by touch and tactilely discernible without activation.

407.3.2 Alphabetic Keys

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.

407.3.3 Numeric Keys

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).

407.4 Key Repeat

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.

407.5 Timed Response

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.

407.6 Operation

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.

407.7 Tickets, Fare Cards, and Keycards

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.

407.8 Reach Height and Depth

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.

407.8.1 Vertical Reference Plane

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.

407.8.1.1 Vertical Plane for Side Reach

Where a side reach is provided, the vertical reference plane shall be 48 inches (1220 mm) long minimum.

graphical representation of dimensions for vertical plane side reach

407.8.1.2 Vertical Plane for Forward Reach

Where a forward reach is provided, the vertical reference plane shall be 30 inches (760 mm) long minimum.

graphical representation of dimensions for vertical plane forward reach

407.8.2 Side Reach

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.

407.8.2.1 Unobstructed Side Reach

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.

graphical representation of dimensions for unobstructed side reach

407.8.2.2 Obstructed Side Reach

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.

graphical representation of dimensions for obstructed side reach

407.8.3 Forward Reach

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.

407.8.3.1 Unobstructed Forward Reach

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.

graphical representation of dimensions for unobstructed forward reach

407.8.3.2 Obstructed Forward Reach

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).

graphical representation of dimensions for obstructed forward reach

407.8.3.2.1 Operable Part Height for ICT with Obstructed Forward Reach

The height of the operable part shall conform to Table 407.8.3.2.1.

Table 407.8.3.2.1 Operable Part Height for ICT with Obstructed Forward Reach Reach Depth Operable Part Height

Less than 20 inches (510 mm) 48 inches (1220 mm) maximum

20 inches (510 mm) to 25 inches (635 mm) 44 inches (1120 mm) maximum

graphical representation of dimensions for operable part height for obstructed forward reach

407.8.3.2.2 Knee and Toe Space under ICT with Obstructed Forward Reach

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.

graphical representation of dimensions for knee and toe space for obstructed forward reach

EXCEPTIONS:

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.

graphical representation of dimensions for knee and toe space for obstructed forward reach exception one

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.

graphical representation of dimensions for knee and toe space for obstructed forward reach exception two

Supplemental graphic combining both Exceptions 1 and 2:

graphical representation of dimensions for knee and toe space for obstructed forward reach exceptions one and two

408 Display Screens

408.1 General

Where provided, display screens shall conform to 408.

408.2 Visibility

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.

408.3 Flashing

Where ICT emits lights in flashes, there shall be no more than three flashes in any one-second period.

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.

409 Status Indicators

409.1 General

Where provided, status indicators shall be discernible visually and by touch or sound.

410 Color Coding

410.1 General

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.

411 Audible Signals

411.1 General

Where provided, audible signals or cues shall not be used as the only means of conveying information, indicating an action, or prompting a response

412 ICT with Two-Way Voice Communication

412.1 General

ICT that provides two-way voice communication shall conform to 412.

412.2 Volume Gain

ICT that provides two-way voice communication shall conform to 412.2.1 or 412.2.2.

412.2.1 Volume Gain for Wireline Telephones

Volume gain conforming to 47 CFR 68.317 shall be provided on analog and digital wireline telephones.

412.2.2 Volume Gain for Non-Wireline ICT

A method for increasing volume shall be provided for non-wireline ICT.

412.3 Interference Reduction and Magnetic Coupling

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.

412.3.1 Wireless Handsets

ICT in the form of wireless handsets shall conform to ANSI/IEEE C63.19-2011 (incorporated by reference, see 702.5.1).

412.3.2 Wireline Handsets

ICT in the form of wireline handsets, including cordless handsets, shall conform to TIA-1083-B (incorporated by reference, see702.9.1).

412.4 Digital Encoding of Speech

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).

412.5 Real-Time Text Functionality

[Reserved].

412.6 Caller ID

Where provided, caller identification and similar telecommunications functions shall be visible and audible.

412.7 Video Communication

Where ICT provides real-time video functionality, the quality of the video shall be sufficient to support communication using sign language.

412.8 Legacy TTY Support

ICT equipment or systems with two-way voice communication that do not themselves provide TTY functionality shall conform to 412.8.

412.8.1 TTY Connectability

ICT shall include a standard non-acoustic connection point for TTYs.

412.8.2 Voice and Hearing Carry Over

ICT shall provide a microphone capable of being turned on and off to allow the user to intermix speech with TTY use.

412.8.3 Signal Compatibility

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).

412.8.4 Voice Mail and Other Messaging Systems

Where provided, voice mail, auto-attendant, interactive voice response, and caller identification systems shall be usable with a TTY.

413 Closed Caption Processing Technologies

413.1 General

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.

413.1.1 Decoding and Display of Closed Captions

Players and displays shall decode closed caption data and support display of captions.

413.1.2 Pass-Through of Closed Caption Data

Cabling and ancillary equipment shall pass through caption data.

414 Audio Description Processing Technologies

414.1 General

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.

414.1.1 Digital Television Tuners

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.

414.1.2 Other ICT

ICT other than digital television tuners shall provide audio description processing.

415 User Controls for Captions and Audio Descriptions

415.1 General

Where ICT displays video with synchronized audio, ICT shall provide user controls for closed captions and audio descriptions conforming to 415.1.

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.

415.1.1 Caption Controls

Where ICT provides operable parts for volume control, ICT shall also provide operable parts for caption selection.

415.1.2 Audio Description Controls

Where ICT provides operable parts for program selection, ICT shall also provide operable parts for the selection of audio description.

Chapter 5: Software

501 General

501.1 Scope

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.

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).

502 Interoperability with Assistive Technology

502.1 General

Software shall interoperate with assistive technology and shall conform to 502.

EXCEPTION: ICT conforming to 402 shall not be required to conform to 502.

502.2 Documented Accessibility Features

Software with platform features defined in platform documentation as accessibility features shall conform to 502.2.

502.2.1 User Control of Accessibility Features

Platform software shall provide user control over platform features that are defined in the platform documentation as accessibility features.

502.2.2 No Disruption of Accessibility Features

Software shall not disrupt platform features that are defined in the platform documentation as accessibility features.

502.3 Accessibility Services

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.

502.3.1 Object Information

The object role, state(s), properties, boundary, name, and description shall be programmatically determinable.

502.3.2 Modification of Object Information

States and properties that can be set by the user shall be capable of being set programmatically, including through assistive technology.

502.3.3 Row, Column, and Headers

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.

502.3.4 Values

Any current value(s), and any set or range of allowable values associated with an object, shall be programmatically determinable.

502.3.5 Modification of Values

Values that can be set by the user shall be capable of being set programmatically, including through assistive technology.

502.3.6 Label Relationships

Any relationship that a component has as a label for another component, or of being labeled by another component, shall be programmatically determinable.

502.3.7 Hierarchical Relationships

Any hierarchical (parent-child) relationship that a component has as a container for, or being contained by, another component shall be programmatically determinable.

502.3.8 Text

The content of text objects, text attributes, and the boundary of text rendered to the screen, shall be programmatically determinable.

502.3.9 Modification of Text

Text that can be set by the user shall be capable of being set programmatically, including through assistive technology.

502.3.10 List of Actions

A list of all actions that can be executed on an object shall be programmatically determinable.

502.3.11 Actions on Objects

Applications shall allow assistive technology to programmatically execute available actions on objects.

502.3.12 Focus Cursor

Applications shall expose information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface components.

502.3.13 Modification of Focus Cursor

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.

502.3.14 Event Notification

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.

502.4 Platform Accessibility Features

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:

Section 9.3.3 Enable sequential entry of multiple (chorded) keystrokes;

Section 9.3.4 Provide adjustment of delay before key acceptance;

Section 9.3.5 Provide adjustment of same-key double-strike acceptance;

Section 10.6.7 Allow users to choose visual alternative for audio output;

Section 10.6.8 Synchronize audio equivalents for visual events;

Section 10.6.9 Provide speech output services; and

Section 10.7.1 Display any captions provided.

503 Applications

503.1 General

Applications shall conform to 503.

503.2 User Preferences

Applications shall permit user preferences from platform settings for color, contrast, font type, font size, and focus cursor.

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.

503.3 Alternative User Interfaces

Where an application provides an alternative user interface that functions as assistive technology, the application shall use platform and other industry standard accessibility services.

503.4 User Controls for Captions and Audio Description

Where ICT displays video with synchronized audio, ICT shall provide user controls for closed captions and audio descriptions conforming to 503.4.

503.4.1 Caption Controls

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.

503.4.2 Audio Description Controls

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.

504 Authoring Tools

504.1 General

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.

504.2 Content Creation or Editing

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.

EXCEPTION: Authoring tools shall not be required to conform to 504.2 when used to directly edit plain text source code.

504.2.1 Preservation of Information Provided for Accessibility in Format Conversion

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.

504.2.2 PDF Export

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).

504.3 Prompts

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.

504.4 Templates

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.

Chapter 6: Support Documentation and Services

601 General

601.1 Scope

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.

602 Support Documentation

602.1 General

Documentation that supports the use of ICT shall conform to 602.

602.2 Accessibility and Compatibility Features

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.

602.3 Electronic Support Documentation

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).

602.4 Alternate Formats for Non-Electronic Support Documentation

Where support documentation is only provided in non-electronic formats, alternate formats usable by individuals with disabilities shall be provided upon request.

603 Support Services

603.1 General

ICT support services including, but not limited to, help desks, call centers, training services, and automated self-service technical support, shall conform to 603.

603.2 Information on Accessibility and Compatibility Features

ICT support services shall include information on the accessibility and compatibility features required by 602.2.

603.3 Accommodation of Communication Needs

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.

Chapter 7: Referenced Standards

701 General

701.1 Scope

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.

702 Incorporation by Reference

702.1 Approved IBR Standards

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 National Archives Code of Federal Regulations Incorporation by Reference.

702.2 Advanced Television Systems Committee (ATSC)

Copies of the referenced standard may be obtained from the Advanced Television Systems Committee, 1776 K Street NW, Suite 200, Washington, DC 20006–2304.

702.2.1 ATSC A/53 Part 5:2014

Digital Television Standard, Part 5—AC-3 Audio System Characteristics, August 28, 2014.

IBR approved for Appendix C, Section 414.1.1.

702.3 Association for Information and Image Management (AIIM)

Copies of the referenced standard may be obtained from AIIM, 1100 Wayne Ave., Ste. 1100, Silver Spring, Maryland 20910.

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.

IBR approved for Appendix C, Section 504.2.2.

702.4 Human Factors and Ergonomics Society (HFES)

Copies of the referenced standard may be obtained from the Human Factors and Ergonomics Society, P.O. Box 1369, Santa Monica, CA 90406–1369.

702.4.1 ANSI/HFES 200.2

IBR approved for Appendix C, Section 502.4.

702.5 Institute of Electrical and Electronics Engineers (IEEE)

Copies of the referenced standard may be obtained from the Institute of Electrical and Electronics Engineers, 10662 Los Vaqueros Circle, P.O. Box 3014, Los Alamitos, CA 90720–1264.

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.

IBR approved for Appendix C, Section 412.3.1.

702.6 International Code Council (ICC)

Copies of the referenced standard may be obtained from ICC Publications, 4051 W. Flossmoor Road, Country Club Hills, IL 60478–5795.

702.6.1 ICC A117.1-2009

Accessible and Usable Buildings and Facilities, approved October 20, 2010.

IBR approved for Appendix C, Section 402.5.

702.7 International Telecommunications Union Telecommunications Standardization Sector (ITU-T)

Copies of the referenced standards may be obtained from the International Telecommunication Union, Telecommunications Standardization Sector, Place des Nations CH-1211, Geneva 20, Switzerland.

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.

IBR approved for Appendix C, Section 407.3.3.

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.

IBR approved for Appendix C, Section 412.4.

702.8 Internet Engineering Task Force (IETF)

Copies of the referenced standard may be obtained from the Internet Engineering Task Force.

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.

IBR approved for Appendix C, Section 412.4.

702.9 Telecommunications Industry Association (TIA)

Copies of the referenced standard, published by the Telecommunications Industry Association, may be obtained from IHS Markit, 15 Inverness Way East, Englewood, CO 80112.

702.9.1 TIA-1083-B

Telecommunications—Communications Products—Handset Magnetic Measurement Procedures and Performance Requirements, October 2015.

IBR approved for Appendix C, Section 412.3.2.

702.10 Worldwide Web Consortium (W3C)

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.

702.10.1 WCAG 2.0

Web Content Accessibility Guidelines (WCAG) 2.0, W3C Recommendation, December 11, 2008.

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.

Appendix D to Part 1194: Electronic and Information Technology Accessibility Standards as Originally Published on December 21, 2000

[65 FR 80523, Dec. 21, 2000. Redesignated and amended at 82 FR 5832, Jan. 18, 2017]

Subpart A — General

§ D1194.1 Purpose.

The purpose of this part is to implement section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. 794d). Section 508 requires that when Federal agencies develop, procure, maintain, or use electronic and information technology, 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, unless an undue burden would be imposed on the agency. Section 508 also requires that individuals with disabilities, who are members of the public seeking information or services from a Federal agency, have access to and use of information and data that is comparable to that provided to the public who are not individuals with disabilities, unless an undue burden would be imposed on the agency.

§ D1194.2 Application.

(a) Products covered by this part shall comply with all applicable provisions of this part. When developing, procuring, maintaining, or using electronic and information technology, each agency shall ensure that the products comply with the applicable provisions of this part, unless an undue burden would be imposed on the agency.

(1) When compliance with the provisions of this part imposes an undue burden, agencies shall provide individuals with disabilities with the information and data involved by an alternative means of access that allows the individual to use the information and data.

(2) When procuring a product, if an agency determines that compliance with any provision of this part imposes an undue burden, the documentation by the agency supporting the procurement shall explain why, and to what extent, compliance with each such provision creates an undue burden.

(b) When procuring a product, each agency shall procure products which comply with the provisions in this part when such products are available in the commercial marketplace or when such products are developed in response to a Government solicitation. Agencies cannot claim a product as a whole is not commercially available because no product in the marketplace meets all the standards. If products are commercially available that meet some but not all of the standards, the agency must procure the product that best meets the standards.

(c) Except as provided by §1194.3(b), this part applies to electronic and information technology developed, procured, maintained, or used by agencies directly or used by a contractor under a contract with an agency which requires the use of such product, or requires the use, to a significant extent, of such product in the performance of a service or the furnishing of a product.

§ 1194.3 General exceptions.

(a) This part does not apply to any electronic and information technology operated by agencies, the function, operation, or use of which involves intelligence activities, cryptologic activities related to national security, command and control of military forces, equipment that is an integral part of a weapon or weapons system, or systems which are critical to the direct fulfillment of military or intelligence missions. Systems which are critical to the direct fulfillment of military or intelligence missions do not include a system that is to be used for routine administrative and business applications (including payroll, finance, logistics, and personnel management applications).

(b) This part does not apply to electronic and information technology that is acquired by a contractor incidental to a contract.

(c) Except as required to comply with the provisions in this part, this part does not require the installation of specific accessibility-related software or the attachment of an assistive technology device at a workstation of a Federal employee who is not an individual with a disability.

(d) When agencies provide access to the public to information or data through electronic and information technology, agencies are not required to make products owned by the agency available for access and use by individuals with disabilities at a location other than that where the electronic and information technology is provided to the public, or to purchase products for access and use by individuals with disabilities at a location other than that where the electronic and information technology is provided to the public.

(e) This part shall not be construed to require a fundamental alteration in the nature of a product or its components.

(f) Products located in spaces frequented only by service personnel for maintenance, repair, or occasional monitoring of equipment are not required to comply with this part.

§ D1194.4 Definitions.

The following definitions apply to this part:

Agency

Any Federal department or agency, including the United States Postal Service.

Alternate formats

Alternate formats usable by people with disabilities may include, but are not limited to, Braille, ASCII text, large print, recorded audio, and electronic formats that comply with this part.

Alternate methods

Different means of providing information, including product documentation, to people with disabilities. Alternate methods may include, but are not limited to, voice, fax, relay service, TTY, Internet posting, captioning, text-to-speech synthesis, and audio description.

Assistive technology

2 notes · View notes

aodawebdevelopment · 2 months

Text

Don't Risk Non-Compliance: The Benefits of Conducting an AODA Audit

In our increasingly digital world, ensuring that your website is accessible to all users is paramount. This includes adhering to legal requirements set forth by the Accessibility for Ontarians with Disabilities Act (AODA). Conducting an AODA audit is a proactive approach to ensure compliance and enhance the user experience for everyone. Here are the benefits of conducting an AODA audit and how it can protect your business from the risks of non-compliance.

Understanding AODA Audits

An AODA audit is a thorough evaluation of your website to ensure it meets the accessibility standards mandated by the AODA. These standards align with the Web Content Accessibility Guidelines (WCAG) 2.0 and cover various aspects of accessibility, including:

Perceivable: Information and user interface components must be presentable to users in ways they can perceive.

Operable: User interface components and navigation must be operable.

Understandable: Information and the operation of the user interface must be understandable.

Robust: Content must be robust enough to be reliably interpreted by a wide variety of user agents, including assistive technologies.

The Benefits of Conducting an AODA Audit

1. Legal Compliance

One of the primary benefits of conducting an AODA audit is ensuring legal compliance. The AODA sets strict accessibility standards for websites, and failure to comply can result in hefty fines and legal actions. Regular audits help you stay updated with the latest requirements and ensure your website meets all necessary standards, protecting your business from legal risks.

2. Improved User Experience

An AODA audit enhances the user experience by making your website accessible to everyone, including people with disabilities. Accessible websites are easier to navigate, read, and interact with, leading to higher user satisfaction and engagement. By addressing accessibility issues, you create a more inclusive digital environment that benefits all users.

3. Expanded Audience Reach

Making your website accessible opens it up to a wider audience. People with disabilities represent a significant portion of the population, and ensuring your website is accessible allows you to reach this untapped market. This can lead to increased traffic, higher customer retention, and ultimately, greater revenue.

4. Positive Brand Image

Demonstrating a commitment to accessibility positively impacts your brand image. It shows that your business values inclusivity and is dedicated to providing equal access to all users. This can enhance your reputation, build customer loyalty, and set you apart from competitors who may not prioritize accessibility.

5. Future-Proofing Your Website

Technology and legal requirements are constantly evolving. Conducting regular AODA audits ensures that your website remains compliant with the latest accessibility standards. This proactive approach helps future-proof your website, preventing potential issues and ensuring ongoing compliance.

How to Conduct an AODA Audit

Automated Tools

Utilize automated tools such as WAVE, Axe, and Lighthouse to identify accessibility issues. These tools can quickly scan your website and provide detailed reports on areas that need improvement.

Manual Testing

While automated tools are essential, they may not catch all issues. Manual testing involves using assistive technologies like screen readers and keyboard navigation to identify accessibility barriers that automated tools might miss.

User Testing

Involving users with disabilities in the testing process provides invaluable insights. Their feedback can highlight real-world accessibility challenges and help you address them effectively.

Regular Reviews

Conduct regular reviews and updates to ensure ongoing compliance. Accessibility is not a one-time fix but an ongoing commitment to providing an inclusive digital experience.

Best Practices for Maintaining Accessibility

Descriptive Alt Text: Ensure all images have descriptive alt text for screen reader users.

Keyboard Navigation: Make all functionalities accessible via keyboard.

Consistent Layout: Maintain a clear and consistent layout for easy navigation.

High Contrast: Use high-contrast color schemes and readable fonts for better legibility.

Accessible Forms: Ensure forms are clearly labeled and easy to use.

Conclusion

Conducting an AODA website audit is a vital step in ensuring your website is accessible, compliant, and user-friendly. By prioritizing accessibility, you protect your business from legal risks, enhance user experience, expand your audience, and build a positive brand image. Regular AODA audits and adherence to best practices will ensure your website remains accessible and inclusive, helping you stay ahead in the digital landscape. Don't risk non-compliance—invest in an AODA audit today and secure a better, more inclusive web experience for all.

#AODA audit #AODA website audit

0 notes

affordablewebdesigninadelaide · 4 months

Text

Accessibility for All: How Affordable Web Design Can Make Your Adelaide Website Inclusive

In today's digital world, having a strong online presence is crucial for any business, especially small and medium-sized enterprises (SMEs) in Adelaide. However, a website that looks beautiful and functions flawlessly for some users might leave others behind. This is where web accessibility comes in.

Web accessibility ensures that everyone, regardless of ability, can access and interact with your Adelaide website. This includes people with disabilities such as visual impairments, hearing loss, cognitive difficulties, and motor limitations.

Why Accessibility Matters for Adelaide Businesses

Beyond the ethical imperative of ensuring everyone has equal access to information and services, there are several compelling reasons for Adelaide businesses to prioritize web accessibility:

Market Expansion: By making your website accessible, you unlock a wider audience, including the large and growing population of people with disabilities in Australia.

Improved SEO: Search engines like Google favor websites that are accessible. This can improve your website's ranking in search results, leading to increased organic traffic.

Enhanced Brand Reputation: Demonstrating a commitment to accessibility portrays your Adelaide business in a positive light, fostering trust and loyalty with customers.

Reduced Legal Risk: Discrimination lawsuits based on website inaccessibility are on the rise. An accessible website can help mitigate such risks.

Affordable Web Design in Adelaide and Accessibility:

Many Adelaide businesses, particularly SMEs, might believe that creating an accessible website requires significant investment. However, this is not necessarily true. Affordable web design services in Adelaide can help you achieve accessibility without breaking the bank. Here's how:

Focus on WCAG Guidelines: The Web Content Accessibility Guidelines (WCAG) are a set of international standards for web accessibility. There are different levels of compliance (WCAG 2.0 AA being the most common). Start by focusing on the core WCAG principles, and gradually improve accessibility over time.

Prioritize Essential Features: Identify the crucial features and functionalities of your Adelaide website and ensure they are accessible to everyone. This could include providing alt text for images, using clear and concise language, and ensuring proper keyboard navigation.

Utilize Free Accessibility Tools: Several free online tools and browser extensions can help you identify and address accessibility issues on your website. These tools can be valuable assets for affordable web design projects in Adelaide.

Work with an Accessible Web Design Agency: Many Adelaide web design agencies specialize in creating accessible websites. Look for agencies with experience in WCAG compliance and user-centered design principles. By partnering with such an agency, you can leverage their expertise and avoid costly mistakes.

Examples of Affordable Accessibility Practices for Adelaide Websites:

Here are some specific, cost-effective ways to improve the accessibility of your Adelaide website:

Clear and Simple Design: Use clean layouts, high-contrast colors, and readable fonts. Avoid overly complex design elements that can be confusing for users with visual impairments.

Alternative Text Descriptions: Provide clear and concise alt text descriptions for all images on your website. This allows screen readers to convey the content of the image to visually impaired users.

Keyboard Navigation: Ensure all website elements can be accessed and interacted with using just a keyboard. This is crucial for users who rely on assistive technologies.

Descriptive Links: Use clear and descriptive link text that accurately reflects the destination of the link. Avoid generic links like "Click Here."

Closed Captions on Videos: If your website includes video content, provide closed captions for users with hearing impairments.

FAQs on Affordable Web Design in Adelaide and Website Accessibility

Q: Our Adelaide business has a tight budget. Can we still make our website accessible?

A: Absolutely! As discussed above, many affordable web design strategies can significantly improve accessibility. Focus on core WCAG principles and utilize free resources.

Q: Do I need to redesign my entire website to be accessible?

A: Not necessarily. Accessibility improvements can be implemented gradually. Start with the most critical aspects of your website and build upon them.

Q: How can I tell if my Adelaide website is accessible?

A: Several online tools can help you assess the accessibility of your website. Additionally, consider consulting an affordable web design agency in Adelaide with expertise in accessibility testing.

Conclusion

In today's digital landscape, creating an inclusive online experience is no longer a luxury; it's a necessity. By prioritizing accessibility and partnering with a skilled and affordable web design in Adelaide, you can ensure your website reaches a wider audience, improves your brand reputation, and fosters a more inclusive online environment.

0 notes

adasitecompliance · 7 months

Text

Web Accessibility

Essential Website Compliance Checklists: Resources for Keeping Your Site Compliant and Secure

It might be surprising, but the Americans with Disabilities Act (ADA) does not specifically address websites. This has led to uncertainty about whether websites must comply with ADA regulations. Despite this ambiguity, it remains crucial to ensure that your website is ADA-compliant to ensure accessibility for all users.

Every organization should have a solid understanding of ADA website compliance guidelines. By familiarizing yourself with ADA requirements, you can reduce the risk of costly lawsuits resulting from ADA violations.

Navigating the ever-changing landscape of web accessibility laws can be challenging for businesses and organizations. ADA Site Compliance is here to help you achieve compliance with the California Consumer Privacy Act (CCPA) on your website.

Our knowledgeable compliance professionals stay updated on the latest trends and legislation to ensure your website meets the necessary standards. By prioritizing website accessibility, you can enhance your business’s overall performance and boost your bottom line.

Delving into the Fundamentals of ADA Certification for Websites

The Americans with Disabilities Act (ADA) was formally enacted in 1991. Initially focusing on physical barriers, the ADA ensures equal access to public spaces. However, with the rise of digital environments, the issue of accessibility has expanded to include online platforms.

In recent years, there has been a notable shift in the interpretation of ADA regulations by federal agencies and courts, particularly the Department of Justice (DOJ). Despite the absence of specific government policies addressing web accessibility, courts increasingly recognize the importance of ensuring equal access to digital platforms for individuals with disabilities.

Consequently, websites must prioritize ADA compliance to ensure accessibility for all users, adhere to legal standards, and promote inclusivity online.

Understanding the Link Between web content accessibility guidelines and ADA Compliance

Establishing a clear understanding of how the Web Content Accessibility Guidelines (WCAG) align with the Americans with Disabilities Act (ADA) is crucial for ensuring digital accessibility. Following the Rehabilitation Act 2017 update to Section 508, government agencies and their contractors must adhere to WCAG 2.0 A/AA standards explicitly.

Despite the absence of precise standards for commercial businesses under the ADA, they are still expected to ensure accessibility within their establishments.

While WCAG serves as the de facto standard for web accessibility, adherence to these guidelines is recommended, as past Department of Justice (DOJ) cases have underscored WCAG’s significance in legal rulings. Although WCAG 2.0 AA is considered the minimum standard, striving for compliance with WCAG 2.1 AA or WCAG 2.2 is advisable to future-proof your existing website too.

WCAG 2.1 and its successor, WCAG 2.2, aim to improve upon previous versions and address emerging trends, such as the increasing use of mobile devices for internet access. WCAG 2.2 encompasses all WCAG 2.1 guidelines while accommodating multiple disabilities across various devices.

Despite not being officially adopted into law by the Department of Justice, WCAG guidelines remain the globally recognized standard for ADA compliance. Therefore, adherence to WCAG criteria is essential for creating a fair and inclusive online environment for all individuals, regardless of their abilities. Non-compliance may result in legal ramifications.

Which Websites Must Comply with the Americans with Disabilities Act (ADA)?

All websites, except for personal, hobby, and professional blogs, must comply with the standards set forth by the Americans with Disabilities Act (ADA). Whether a website is used for informational or commercial purposes, adherence to ADA web requirements is essential. Additionally, websites facilitating online transactions, such as e-commerce platforms, must ensure ADA compliance.

A few steps that can be taken to achieve compliance with WCAG 2.1 Level A are:

To prevent seizures, ensure your website has no content that could potentially trigger seizures.

Fast-strobing lights, for instance, have been known to induce seizures in some individuals.

Mere warnings about flashing content are insufficient; instead, design your content to mitigate the risk of seizures.

Any element that flashes more than three times in a single second should be avoided on websites.

Gaining In-Depth Insights into Website Security Compliance

Ensuring robust website security measures is vital for safeguarding your digital assets effectively. These compliance standards are designed to bolster your organization and instill confidence among stakeholders by fostering a secure online environment.

They encompass a broad spectrum of security elements, spanning data protection, privacy safeguards, auditing procedures, incident reporting protocols, and more. Acknowledging that compliance is ongoing, requiring regular updates, continuous monitoring, and proactive engagement is crucial for sustained adherence.

Embracing these standards enhances your credibility and underscores your unwavering commitment to safeguarding customer interests.

Is your Website at Legal Risk Due to Non-Compliance with ADA Standards?

The surge in federal lawsuits against businesses and government entities for inaccessible websites is concerning. High-profile cases demonstrate that no organization is immune to the legal consequences of ADA violations.

For instance, Parkwood Entertainment, owned by Beyoncé, faced legal action for lacking image alt text on its website. Similarly, Harvard University and MIT were sued for not providing captions for those with hearing impairments.

While these cases garner attention, many small businesses face similar legal challenges under the radar. When hit with a lawsuit, businesses incur expenses covering the plaintiff’s legal fees and their legal costs and must implement website improvements.

The financial toll of inaction can be staggering. Investing in web accessibility is a prudent financial decision to mitigate the risk of lawsuits. Proactive risk management remains the most effective form of protection until the Department of Justice establishes clear standards.

ADA Website Compliance Checklist

This comprehensive ADA compliance checklist is designed to ensure compliance with the latest accessibility standards outlined in WCAG 2.1. It covers three levels of compliance: Level A, Level AA, and Level AAA. While achieving Level AA compliance is recommended for all websites, some tools can streamline the process.

1. Enhancing Button Accessibility

Implementing accessible naming conventions and ARIA labels across all website buttons is crucial for facilitating navigation for users with visual or auditory impairments.

2. Alt Text for Enhanced Accessibility

Ensure your website caters to all visitors by providing descriptive alt text for graphical elements like images and buttons.

3. Skip Navigation for Seamless Access

Incorporate skip navigation links to empower users relying on keyboard navigation or screen readers for easy access to your website’s main content.

4. Organize Content Hierarchy

Use bold headers and subheadings to organize page content effectively and communicate its importance to readers.

5. Descriptive Anchor Text for Clarity

Make outbound links more accessible by using descriptive anchor text that is easily understandable and clickable for users and search engines alike.

6. Keyboard Navigation Accessibility

Enable seamless navigation and accessible websites for individuals with disabilities by ensuring all website elements can be accessed using a keyboard.

7. Streamlined Error Reporting

Implement a user-friendly system for reporting all accessibility violations and barriers, allowing for prompt resolution and rectification.

8. Prominently Display Contact Information

Enhance user accessibility by prominently displaying your organization’s contact details, facilitating communication for those seeking assistance with access controls or information related to accessibility.

Ensuring Consistent Compliance Through Thorough Security Audits

Maintaining the security and reliability of your online platform requires strict adherence to industry regulations and standards. Conducting regular security audits is essential to uphold compliance. During these audits, your security infrastructure, including the web application firewall (WAF), undergoes meticulous evaluation to assess its alignment with relevant regulatory standards.

An audit identifies potential security vulnerabilities and provides valuable insights for enhancing your overall security posture. These audits demonstrate your commitment to robust security best practices and provide tangible evidence of your organization’s adherence to regulatory requirements.

Selecting Expert Website Audit Services for Enhanced Security

Securing your online presence demands partnering with a reputable website auditing firm like ADA Site Compliance, renowned for its expertise. Our seasoned professionals in this field possess the knowledge and capabilities to evaluate website security protocols thoroughly.

We dive deep into data protection measures and can thus offer tailored recommendations to mitigate risks effectively. Moreover, their adeptness with compliance standards ensures your website meets regulatory requirements, fostering customer trust and safeguarding your brand integrity in the digital landscape.

Conclusion

Updating your website to meet ADA compliance standards requires significant time and effort. The Americans with Disabilities Act mandates strict adherence, underscoring the importance of taking proactive steps promptly.

Navigating the complex web accessibility regulations can be daunting for businesses. At ADA Site Compliance, we specialize in achieving CCPA website compliance and can provide expert guidance. Our team thoroughly analyses your current website and offers assistance in redesigning it to ensure equal access to all users. Contact us today, or get your free site scan here.

Additionally, we offer training and ongoing support to help you maintain compliance with evolving regulations. Our compliance professionals stay abreast of the latest laws and standards, ensuring your website meets all requirements. Prioritizing website accessibility enhances your overall performance and increases profitability!

0 notes

get-x-media · 7 months

Text

AODA Website Compliance: A Comprehensive Guide to WCAG 2.0

Unlocking the Secrets of AODA Compliance: A Supplementary Guide

Welcome to your next step in embracing digital inclusivity! You've delved into the comprehensive guide to WCAG 2.0 provided by Get X Media, and now it's time to supplement that treasure trove of knowledge with actionable insights. Let's ensure your cyber vessel is not only seaworthy but welcoming to all passengers.

Imagine, your website isn't just a beacon in the vast internet ocean; it's a lighthouse guiding everyone to safe harbor, regardless of their ability to navigate typical waters. It's not just good practice; it's your digital duty. Compliance with the Accessibility for Ontarians with Disabilities Act (AODA) isn't merely about following rules; it's about tearing down barriers and crafting a user experience that is universally exceptional. Now, let’s sail beyond the basics and explore how you can master the waves of web accessibility.

Charting a Course Through AODA Compliance

True mastery comes with understanding the 'why' as much as the 'how'. Acknowledging that every aspect of your website's design, from the colors to the coding, can either be a stepping stone or a stumbling block forms the bedrock of empathetic web design.

With the expertise of a Canada web design team that breathes life into compliance, your website transforms into an inclusive platform. Picture this: a visually impaired visitor navigates your site with ease, thanks to alt-text rich images and keyboard-friendly navigation. This isn't a one-off charitable act; it's the hallmark of a forward-thinking Canada advertising agency.

Setting Sail with SEO and AODA Harmony

Hold fast, SEO enthusiasts—that anchor isn't just weighing you down; it's grounding you in best practices. There's a beautiful symmetry between AODA compliance and Search Engine Optimization. These guidelines urge you to create clear, well-structured content—exactly what search engines and users adore. By leveraging the finesse of a Canada SEO Agency, your compliant site will not only be discoverable but also cherished for its accessibility.

Automate Your Efforts

Perhaps tech isn't your native tongue—fear not. Modern-day marketing mariners have tools at their disposal. Marketing automation can streamline your journey, making AODA compliance less daunting and more intuitive. Enlist these powerful winds, and they'll ensure you're sending the right signals, even as the digital seas change.

Navigating Data Privacy and Web Accessibility

As you chart your course through digital waters, keep the North Star of data privacy compliance in sight. By fostering an environment of trust, you assure visitors that their digital voyage with you is secure from privateer’s eyes.

Don't forget that the ship of accessibility must also be built to welcome every traveler. Aligning with web accessibility compliance is like providing a gangplank for all to board, ensuring no one is left to watch from the docks.

All Hands on Deck for Your Digital Transformation

The tide is changing, and in the sea of digital innovation, those who adapt, thrive. AODA compliance isn't a distant shore; it's within your grasp, and the crew at Get X Media is ready to man the oars alongside you.

Dive into the heart of AODA compliance with confidence, knowing that your brand isn't just meeting standards but setting sail as a beacon of inclusivity and excellence.

Are you ready to hoist the sails and lead your fleet to accessible shores? Request a proposal today, and let Get X Media be your compass to success.

0 notes

jmaartenw · 10 months

Text

What Are the 7 Web Development Life Cycles Recently we had a discussion with a client and talked about what are the 7 web development life cycles. So we thought we'd put a summary into a blog for you. The web development life cycle (WDLC) is a process used to create, maintain, and improve websites. It involves a series of steps that must be followed in order to ensure that the website is successful. The WDLC consists of seven distinct phases: planning, design, development, testing, deployment, maintenance, and optimization. Each phase has its own purpose and is importance in the overall success of the website. In this blog post, we will discuss each phase of the WDLC and its purpose. Planning The planning phase is the first step in the WDLC. During this phase, you will need to determine what your website needs to accomplish and how it should be structured. This includes deciding on a domain name, hosting provider, content management system (CMS), and other necessary components. You will also need to identify your target audience and develop a plan for how you will reach them. This phase is critical for setting up a successful website as it helps you determine what resources are needed for each stage of the process. Some decisions made at this point would create a lot of work if you later changed your mind. You should also use this time to think about what it is you want to say or more importantly, what your potential clients might want to know. This part of the Planning stage is called Keyword research. Design The design phase is where you create the look and feel of your website. This includes selecting colours, fonts, images, layouts, navigation menus, etc. You should also consider how users will interact with your site by creating user flows or wireframes that show how they can move from one page to another. During this phase you should also consider accessibility standards such as WCAG 2.0 AA or Section 508 compliance so that all users can access your site regardless of their abilities or disabilities. often people think the design is about personal preferences, for example you may really be into dark colours like Black with high contrast white text. The important thing to consider though is that the colours, graphics and fonts need to be compatible with your brand. Black may not be appropriate if your business is a children's nursery, it would send totally the wrong message. Development Once you have finalized your design plans it’s time to start developing your website using HTML/CSS/JavaScript or any other programming language you choose to use. At Saint IT our preferred CMS is Wordpress for lots of reasons. One of the most important reasons is the flexibility and the ease of use for the client once the website goes live. During this phase you will need to write code that implements all of the features outlined in your design plans as well as any additional features that may be needed for functionality or interactivity purposes. Once all of the code has been written it’s time to test it out on different browsers and devices to make sure everything works correctly before moving on to deployment. Testing The testing phase is where you make sure everything works properly before launching your website live on the internet. This includes checking for bugs or errors in code as well as ensuring that all features are working correctly across different browsers and devices. It’s important to test thoroughly during this stage so that any issues can be identified and fixed before launch day arrives! Remember that a bad website with lots of errors or bad grammar can negatively impact your brand. Deployment Once all tests have been completed successfully it’s time for deployment! This involves making the website live so that they can be accessed by users online via their web browser or mobile device. Depending on which hosting provider you choose there may be additional steps involved such as setting up databases or configuring security settings but once everything is ready then it’s time for launch day!

At this point it is also important to check your SEO and your reporting, making sure that each page is fully optimised for search engines and you're getting good reporting from your website. Integration with Google Analytics one such useful tool for this. Maintenance Web Development agencies often overlook this stage. The Website has been created, the client has paid the bill and they're now left with a website that requires constant maintenance without any training or instructions to carry this out. The maintenance phase is an ongoing process where changes are made over time based on user feedback or new requirements from stakeholders/clients etc.. This could involve adding new features/functionality or fixing existing bugs/errors in code etc.. It’s important to keep up with maintenance regularly so that users always have an optimal experience when visiting your website! At Saint IT we ensure all our clients receive the best service once their website is live. We have the skills and knowhow to ensure all updates are applied regularly and we perform monthly manual, visual checks and tests to ensure there are no issues. Optimization The optimization phase involves making changes over time in order to improve performance such as increasing page loading speeds or improving search engine rankings etc.. This could involve making changes such as optimizing images/code for faster loading times or implementing SEO best practices like meta tags etc.. It’s important to keep up with optimization regularly so that users always have an optimal experience when visiting your website! Website performance depends on a number of factors and your web developer/agency should have advised you at the planning stage of the best hosting package for your website. If you're running a large corporate website with hundreds of pages you're not going to want to host that on a low cost public cloud web host. Conclusion The web development life cycle (WDLC) with it's seven distinct phases: planning, design, development, testing, deployment, maintenance and optimization outlines the complexities involved in web design. each phase with its own purpose within the website project is crucial to how well your website performs over time. If you have the multiple skills required and the time, you can certainly undertake such a project by following these steps carefully. However we recommend you partner with an experienced web design agency because they have the right tools and differing skills required. By partnering with Saint IT to build your website you can ensure that throughout each stage your website meets its goals while providing an optimal experience for visitors and users of your website. Check out our Other Blogs What Are the 7 Web Development Life Cycles Saint IT Pleased To Support Local Initiatives Unravelling the Roles: What Does a Web Designer and Developer Do? What Are the Benefits of a Cloud-Based Phone System? Follow us on Social media How to be Good in Business

0 notes

kushitworld · 11 months

Text

Discuss The Significance Of Web Accessibility

Web Accessibility: Discuss the significance of web accessibility and offer guidance on making websites more inclusive for users with disabilities.

In an increasingly digital world, web accessibility is not just a matter of good practice; it’s a fundamental requirement. The significance of web accessibility cannot be overstated, as it ensures that everyone, regardless of their abilities or disabilities, can access and interact with online content. In this article, we’ll explore the importance of web accessibility and provide guidance on making websites more inclusive for users with disabilities.

The Significance of Web Accessibility

1. Equal Access to Information

Web accessibility guarantees that all individuals have equal access to information and services online. It levels the playing field, enabling those with disabilities to browse the internet, access educational resources, seek employment, and interact with web-based services just like anyone else.

2. Legal Compliance and Avoiding Discrimination

Many countries have adopted web accessibility standards and laws to ensure that websites are inclusive. Failing to adhere to these standards can lead to legal consequences and discrimination claims. Compliance is not only a legal requirement but also a moral obligation.

3. Expanding Your Audience

By making your website accessible, you expand your potential audience. In the United States alone, over 60 million people have a disability. Neglecting web accessibility effectively excludes a significant portion of the population from accessing your content or using your services.

4. Improved SEO and Search Rankings

Search engines like Google consider web accessibility as a ranking factor. Websites that are accessible and provide a better user experience tend to rank higher in search results. This means that not only does web accessibility improve user experience for people with disabilities, but it can also improve your site’s visibility to a broader audience.

5. Positive Brand Image

Promoting web accessibility enhances your brand’s image as one that values diversity and inclusivity. It can also lead to increased customer loyalty, as users appreciate efforts to make their online experience more comfortable.

Guidance on Making Websites More Inclusive

Now that we understand the importance of web accessibility, let’s explore how to make websites more inclusive:

1. Understand Web Accessibility Guidelines

Familiarize yourself with web accessibility guidelines, such as the Web Content Accessibility Guidelines (WCAG) 2.0 and 2.1. These guidelines provide a framework for creating accessible websites, covering areas like text alternatives, keyboard navigation, and ensuring content is understandable and robust.

2. Use Semantic HTML

Properly structured HTML is the foundation of web accessibility. Use semantic HTML elements to convey the structure and meaning of your content. Heading tags, lists, and labels for form elements should be used correctly.

3. Provide Alternative Text for Images

Images play a significant role in web content. Ensure that all images have descriptive alt text. This helps screen readers convey the content and context of images to users with visual impairments.

4. Keyboard Navigation

Make sure your website can be navigated using a keyboard alone. Ensure that all interactive elements, like links and forms, are accessible via keyboard shortcuts. Avoid relying on mouse-only interactions.

5. Captions and Transcripts

For multimedia content, provide captions for videos and transcripts for audio content. This benefits users with hearing impairments and those who may prefer reading content.

6. Maintain Readable Content

Use clear and legible fonts, provide sufficient contrast between text and background, and keep content organized and concise. This benefits users with visual and cognitive disabilities.

7. Test and Validate Your Website

Regularly test your website with accessibility evaluation tools and seek user feedback. This helps identify and address accessibility issues.

8. Train Your Team

Ensure your web development and content creation teams are knowledgeable about web accessibility best practices. Training can help prevent and address accessibility barriers effectively.

In conclusion, web accessibility is not only about compliance with legal standards; it’s about creating an inclusive digital space where everyone can participate. By understanding the significance of web accessibility and following these guidelines, you can contribute to a more equitable and inclusive online environment. Web accessibility benefits not only users with disabilities but also your website’s reputation, search engine visibility, and overall user experience.

Source:

#kushitworld #saharanpur #india #itcompany #digital marketing #seo services #digitalmarketing #seo #webdevelopment #webdesign

0 notes

robertpattsblog · 4 months

Text

👀 Make your content perceivable by all users! Provide text alternatives for non-text content like images, audio, and video. https://www.acadecraft.com/accessibility/wcag-compliance/

#WCAG #accessibility #wcag compliance #wcag 2.0 compliance #ada wcg compliance