Tumgik
#Web Content Accessibility Guidelines (WCAG)
blogpopular · 3 months
Text
Acessibilidade na Web: Criando Experiências Inclusivas
A acessibilidade na web é chave para experiências digitais que incluam todos, seja qual for a habilidade ou deficiência. Vamos ver como fazer a web ser um lugar mais acessível e acolhedor para todos. Principais Aprendizados A acessibilidade na web permite que qualquer pessoa, incluindo aquelas com deficiências, use e aproveite o conteúdo e funções online. As diretrizes WCAG (Web Content…
Tumblr media
View On WordPress
0 notes
adasitecompliance · 6 months
Text
Tumblr media
Accessible Websites
Design websites with features and functionalities that enable individuals with disabilities to access and interact with online content effectively, promoting a more inclusive and equitable digital experience!
0 notes
uiexpertayyaj · 8 months
Text
youtube
Web Accessibility in UI Design: Explore the principles and best practices of creating accessible user interfaces, ensuring inclusivity for users with disabilities.
In the expansive realm of user interface (UI) design, the commitment to inclusivity has become a central tenet. Web accessibility, the practice of designing and developing digital interfaces that can be used by people of all abilities, is crucial in ensuring that the digital landscape is accessible to everyone, regardless of their physical or cognitive capabilities. In this article, we delve into the principles and best practices of creating accessible user interfaces that prioritize inclusivity for users with disabilities.
Understanding Web Accessibility: Web accessibility encompasses the design and development of websites, applications, and digital tools that can be navigated and used by individuals with various disabilities. This includes but is not limited to visual, auditory, motor, and cognitive impairments. The goal is to remove barriers and provide an equitable digital experience for all users.
Principles of Web Accessibility: Perceivable, Operable, Understandable, Robust Best Practices for Web Accessibility in UI Design: Semantic HTML. Alternative Text for Images, Keyboard Navigation, Contrast and Readability, Captions and Transcripts, Focus Indicators, Form Accessibility, Avoiding Flashing Content, Testing with Assistive Technologies, Education and Awareness Conclusion: Web accessibility is not just a legal requirement; it is a moral imperative and a design philosophy that enriches the digital experience for everyone. By adhering to the principles of perceivability, operability, understandability, and robustness, and implementing best practices in UI design, designers can contribute to a digital landscape that is truly accessible to users of all abilities. In embracing the ethos of inclusivity, we move closer to a future where technology is a bridge rather than a barrier, ensuring that the benefits of the digital age are shared equitably among all individuals.
0 notes
aeldata-usa · 9 months
Text
0 notes
jdunlevy · 2 years
Text
Web “content”?
Web “content” generally refers to the information in a web page or web application, including:
natural information such as text, images, and sounds
code or markup that defines structure, presentation, etc.
I came across this surprisingly concise and thorough definition in the Introduction to the WCAG 2 Overview introducing “the Web Content Accessibility Guidelines (WCAG) international standard, including WCAG 2.0, WCAG 2.1, and WCAG 2.2.” That’s much better than I’ve found anywhere else.
Leave it to the Web Accessibility Initiative to understand that it’s about both “natural information” (e.g. written editorial content like an article or advertising content like an ad) and how it’s presented (like the elements of design within the article, where and how an ad is shown and its design).
And bonus points for putting “content” in quotes. As that term has been fraught—and seems to have it's origins in referring to web “content.” John Long arguing in The Drum in 2018 that “‘Content’ is a terrible term. Please stop using it.”:
“‘The principal substance offered by a website.’
And that’s the first thing everyone should remember about the word ‘content’ — it’s a website term that was probably initially used by programmers to generically describe the stuff that wasn’t code, i.e., the stuff that was mere ‘fluff’ to them. Like, say, The Iliad.
With that in mind, maybe the second part of the WCAG intro definition could be modified so it's not so much the “code or markup” itself but rather the “structure, presentation, etc.” definined by that code or markup.
(There’s a lot of great and useful information over on the Web Accessibility Initiative section of the Wolrd Wide Web Consortium (W3C) site, including the WAI Resources page describing “most technical and educational resources from the World Wide Web Consortium (W3C) Web Accessibility Initiative (WAI).” Many things to keep in mind when making content—doing pretty much anything on the publishing side—on the web.)
0 notes
Note
3rd person jumping into the link conversation. You can find accessible linking guidelines at WCAG (web content accesibility guidelines)
Ironically, tumblr mobile isn't letting me hyperlink the above (WCAG) so I have to paste the raw link as it is
Oh wow it won't even let me do that, some kind of "not supported" message. Ok the article is called "Understanding SC 2.4.4: Link Purpose (In Context) (Level A)"
The start is a bit dense and aimed at web developers and such, and I find it helps to skip to the Examples section and read those to get a feel for it, then go back up to read the guidelines.
"Level A" in the title just means lowest level of accessibility (WCAG) with "AA" and "AAA" being accessible for more people (how WCAG defines it)
thanks for the suggestion! I've just taken a look at the article. From what I've gathered, the options that are better than just 'source' would be either to be more specfic, or to embed the source directly in the quote. I'm going to give two examples below, and then a poll to see which people prefer.
Option 1:
From BBC article 'US Congress avoids government shutdown in last-minute deal'': 'A bill ensuring funding until 17 November received overwhelming support, and was signed into law by President Joe Biden minutes before a deadline.
Option 2:
'A bill ensuring funding until 17 November received overwhelming support, and was signed into law by President Joe Biden minutes before a deadline.'
If anyone has any further suggestions or feedback on accessibility, feel free to comment below.
64 notes · View notes
lodeemmanuelpalle · 1 year
Text
Guidelines & Best Practices for Exceptional Web Design - Lode Palle
Creating exceptional web design involves following guidelines and best practices to ensure your website is visually appealing, user-friendly, and effective in achieving its goals. Here are some key guidelines and best practices for exceptional web designexplained by Lode Palle:
Understand Your Audience: Start by understanding your target audience, their needs, preferences, and behaviors. Tailor your design to appeal to your specific user demographic.
Mobile-First Design: Design your website with a mobile-first approach, ensuring it looks and functions well on various screen sizes and devices. Responsive design is essential for a seamless user experience.
Clear and Intuitive Navigation: Keep navigation menus simple, organized, and easily accessible. Use clear labels and hierarchical structures to help users find information quickly.
Consistent Branding: Maintain a consistent visual identity, including colors, typography, and logo placement, to reinforce your brand's recognition and trustworthiness.
Whitespace: Use whitespace effectively to improve readability and create a sense of balance in your design. Don't overcrowd pages with content and elements.
Typography: Choose legible fonts and maintain consistent typography throughout your website. Use headings, subheadings, and body text appropriately to structure content.
Color Harmony: Create a harmonious color palette that aligns with your brand and evokes the right emotions. Ensure sufficient contrast between text and background for readability.
High-Quality Images: Use high-resolution, relevant images and graphics to enhance visual appeal. Optimize images for web to improve loading times.
Fast Loading Speed: Optimize your website's performance for fast loading times. Minimize HTTP requests, use compressed images, and enable browser caching.
Content Hierarchy: Organize content with a clear hierarchy, emphasizing important information using headings, bullet points, and visual cues. Make use of whitespace to separate content sections.
Call-to-Action (CTA): Create compelling CTAs that stand out and encourage users to take desired actions. Use action-oriented language and place CTAs strategically.
Accessibility: Ensure your website is accessible to individuals with disabilities. Follow WCAG (Web Content Accessibility Guidelines) to provide alternatives for multimedia and ensure keyboard navigation is possible.
Browser Compatibility: Test your website on various browsers and devices to ensure compatibility and a consistent experience across platforms.
SEO-Friendly Design: Incorporate SEO best practices into your design, including using descriptive URLs, optimizing images, and structuring content with appropriate headings.
Content Management: Use a user-friendly content management system (CMS) to make it easy to update and maintain your website. WordPress, for example, is a popular choice.
Security: Implement security measures to protect user data and your website from cyber threats. Keep software and plugins up to date and use secure hosting.
User Testing: Conduct usability testing to gather feedback from real users and make improvements based on their experiences.
Analytics: Install web analytics tools (e.g., Google Analytics) to monitor user behavior, track goals, and make data-driven improvements to your website.
Regular Updates: Keep your website updated with fresh content, new features, and design improvements to stay relevant and engaging.
Legal Compliance: Ensure your website complies with legal requirements, such as GDPR for data privacy or copyright laws for content usage.
Exceptional web design is an ongoing process that involves continuous improvement and adaptation to changing user needs and technologies. By adhering to these guidelines and best practices, you can create a website that not only looks great but also delivers a superior user experience and achieves its intended objectives.
8 notes · View notes
xneontragedyx · 5 months
Text
Skip to main content
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.
Menu
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
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.
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)
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.
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
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.
Hardware
A tangible device, equipment, or physical component of ICT, such as telephones, computers, multifunction copy machines, and keyboards.
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.
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.
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.
Menu
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.
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 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
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®
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
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.
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).
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.
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 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.
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
Human Factors Engineering of Software User Interfaces — Part 2: Accessibility, copyright 2008.
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
madhusachin · 7 months
Text
The Ultimate Guide to Web Development
In today’s digital age, having a strong online presence is crucial for individuals and businesses alike. Whether you’re a seasoned developer or a newcomer to the world of coding, mastering the art of web development opens up a world of opportunities. In this comprehensive guide, we’ll delve into the intricate world of web development, exploring the fundamental concepts, tools, and techniques needed to thrive in this dynamic field. Join us on this journey as we unlock the secrets to creating stunning websites and robust web applications.
Understanding the Foundations
At the core of every successful website lies a solid foundation built upon key principles and technologies. The Ultimate Guide to Web Development begins with an exploration of HTML, CSS, and JavaScript — the building blocks of the web. HTML provides the structure, CSS adds style and aesthetics, while JavaScript injects interactivity and functionality. Together, these three languages form the backbone of web development, empowering developers to craft captivating user experiences.
Collaborating with a Software Development Company in USA
For businesses looking to build robust web applications or enhance their online presence, collaborating with a Software Development Company in USA can be invaluable. These companies offer expertise in a wide range of technologies and services, from custom software development to web design and digital marketing. By partnering with a reputable company, businesses can access the skills and resources needed to bring their vision to life and stay ahead of the competition in today’s digital landscape.
Exploring the Frontend
Once you’ve grasped the basics, it’s time to delve deeper into the frontend realm. From responsive design to user interface (UI) development, there’s no shortage of skills to master. CSS frameworks like Bootstrap and Tailwind CSS streamline the design process, allowing developers to create visually stunning layouts with ease. Meanwhile, JavaScript libraries such as React, Angular, and Vue.js empower developers to build dynamic and interactive frontend experiences.
Embracing Backend Technologies
While the frontend handles the visual aspect of a website, the backend powers its functionality behind the scenes. In this section of The Ultimate Guide to Web Development, we explore the world of server-side programming and database management. Popular backend languages like Python, Node.js, and Ruby on Rails enable developers to create robust server-side applications, while databases such as MySQL, MongoDB, and PostgreSQL store and retrieve data efficiently.
Mastering Full-Stack Development
With a solid understanding of both frontend and backend technologies, aspiring developers can embark on the journey of full-stack development as a Software Development company in USA. Combining the best of both worlds, full-stack developers possess the skills to build end-to-end web solutions from scratch. Whether it’s creating RESTful APIs, integrating third-party services, or optimizing performance, mastering full-stack development opens doors to endless possibilities in the digital landscape.
Optimizing for Performance and Accessibility
In today’s fast-paced world, users expect websites to load quickly and perform seamlessly across all devices. As such, optimizing performance and ensuring accessibility are paramount considerations for web developers. From minimizing file sizes and leveraging caching techniques to adhering to web accessibility standards such as WCAG (Web Content Accessibility Guidelines), every aspect of development plays a crucial role in delivering an exceptional user experience.
Staying Ahead with Emerging Technologies
The field of web development is constantly evolving, with new technologies and trends emerging at a rapid pace. In this ever-changing landscape, staying ahead of the curve is essential for success. Whether it’s adopting progressive web app (PWA) technologies, harnessing the power of machine learning and artificial intelligence, or embracing the latest frontend frameworks, keeping abreast of emerging technologies is key to maintaining a competitive edge.
Collaborating with a Software Development Company in USA
For businesses looking to elevate their online presence, partnering with a reputable software development company in USA can be a game-changer. With a wealth of experience and expertise, these companies offer tailored solutions to meet the unique needs of their clients. Whether it’s custom web development, e-commerce solutions, or enterprise-grade applications, collaborating with a trusted partner ensures seamless execution and unparalleled results.
Conclusion: Unlocking the Potential of Web Development
As we conclude our journey through The Ultimate Guide to Web Development, it’s clear that mastering the art of web development is more than just writing code — it’s about creating experiences that captivate and inspire. Whether you’re a novice coder or a seasoned veteran, the world of web development offers endless opportunities for growth and innovation. By understanding the fundamental principles, embracing emerging technologies, and collaborating with industry experts, you can unlock the full potential of web development and shape the digital landscape for years to come.
2 notes · View notes
trigventsolutions · 8 months
Text
10 Web Developer Secrets You Need to Know for Success in 2024
Tumblr media
In the fast-paced world of web development, staying ahead of the curve is essential for success. As we venture into 2024, it's crucial to uncover the latest secrets and strategies that can propel your web development endeavors to new heights. Let's delve into ten invaluable insights that every web developer should know for a prosperous year ahead.
Embrace Progressive Web Apps (PWAs)
In 2024, the prominence of Progressive Web Apps (PWAs) continues to soar. These innovative web applications offer users an immersive, app-like experience directly from their browsers. By embracing PWAs, developers can enhance user engagement, improve performance, and seamlessly integrate features like push notifications and offline functionality.
Prioritize Mobile-First Design
With mobile devices dominating internet usage, prioritizing mobile-first design is non-negotiable. Crafting websites with mobile users in mind ensures optimal responsiveness and usability across various devices and screen sizes. Embrace responsive design principles to deliver a seamless browsing experience that caters to the needs of your audience.
Harness the Power of AI and Machine Learning
AI and machine learning technologies are revolutionizing the field of web development. From personalized content recommendations to intelligent chatbots, incorporating AI-driven solutions can elevate user experiences and streamline processes. Explore AI-powered tools and frameworks to unlock new possibilities and stay ahead of the competition.
Optimize for Core Web Vitals
In 2021, Google introduced Core Web Vitals as essential metrics for evaluating user experience. To rank higher in search results and provide users with a smoother browsing experience, prioritize optimizing for Core Web Vitals. Focus on metrics like loading speed, interactivity, and visual stability to ensure your website meets Google's standards and delights visitors.
Implement Voice Search Optimization
The prevalence of voice-enabled devices continues to grow, shaping the way users interact with the web. To capitalize on this trend, implement voice search optimization strategies to make your website more discoverable through voice queries. Consider natural language patterns and long-tail keywords to optimize content for voice search queries effectively.
Enhance Security with HTTPS
Security remains a top priority for web developers, especially in an era marked by increasing cyber threats. Transitioning your website to HTTPS not only encrypts data transmitted between the user's browser and your server but also instills trust and credibility among visitors. Prioritize security protocols to safeguard sensitive information and protect your users' privacy.
Leverage Content Delivery Networks (CDNs)
Content Delivery Networks (CDNs) play a pivotal role in optimizing website performance and reliability. By distributing content across multiple servers worldwide, CDNs reduce latency and ensure faster loading times for users across the globe. Integrate CDNs into your web development workflow to deliver content swiftly and efficiently, regardless of geographical location.
Stay Abreast of Accessibility Standards
Accessibility is an integral aspect of web development, ensuring that websites are inclusive and accessible to all users, regardless of disabilities or impairments. Stay abreast of accessibility standards such as the Web Content Accessibility Guidelines (WCAG) and implement best practices to make your website more usable and navigable for everyone.
Embrace Serverless Architecture
Serverless architecture offers a streamlined approach to web development, eliminating the need to manage servers and infrastructure manually. By leveraging cloud-based services and functions, developers can focus on writing code and delivering value without worrying about scalability or maintenance. Embrace serverless architecture to enhance agility, reduce costs, and accelerate development cycles.
Cultivate Continuous Learning and Adaptation
In the dynamic landscape of web development, continuous learning and adaptation are paramount. Stay curious, explore emerging technologies, and embrace new methodologies to evolve with the industry's ever-changing demands. Cultivate a mindset of lifelong learning, experiment with new tools and techniques, and adapt your skills to thrive in the digital ecosystem.
As we navigate the complexities of web development in 2024, embracing these secrets and strategies can position you for success in an ever-evolving landscape. By staying ahead of trends, prioritizing user experience, and leveraging innovative technologies, you can unlock new opportunities and achieve remarkable feats in the realm of web development.
2 notes · View notes
zine-garden · 1 year
Text
Image Description Guidelines
I think it’s really awesome how tumblr users have started incorporating alt text and other accessibility tools into their blogging! I’ve especially noticed this in fandom spaces too! I’ve seen various posts floating around usually asking for different standards, and there are frequently conflicting access needs! I will be basing this guide on resources i have collected over the years as well as mastodon’s art server’s standard practice. My goal is to provide a standard practice that everyone can implement for art-zine describing specifically.
At the moment, it is not a requirement to include alt text in your submissions, however, i am highly encouraging it even if it is a short description. Submissions without image descriptions will be marked as such. If you misuse the alt text tool, your work will not be shared.
why base base it off of mastodon(.)art?
Mastodon is an open source social media site where it is already user standard to use image descriptions. Additionally, the (.)art server is dedicated to artists of all mediums sharing their work and many of the active users describe images of artwork there. If you need help, I encourage you to scroll through the public feed and see how some artists describe their work.
Mastodon’s alt text box has a 1500 character limit, Tumblr’s has a 4096 character limit. WCAG (Web Content Accessibility Guidelines) recommends between 120-150 characters in order to keep things concise and to the point. For example, decorative graphics and things like banner or pfp’s usually remain undescribed. However, art has a bit more leeway since there is more to describe (and Tumblr accommodates this by design.) Feedback from screen reader users on Mastodon(.)art actually prefer when art is more fully described, just try and be concise.
mastodon(.)art’s guide to image descriptions - https://mastodon.art/@Curator/109279035107793247
We have a lot of blind and partially sighted users on the fediverse. Accessibility is important here, and as such, it’s good form to include image descriptions (alt text) when we add media to our posts.
When someone uses a screen reader to read the timeline, and the screen reader comes to an image with no alt text, it just says ‘image’. That’s boring, unhelpful, and provides no clue as to what the image actually is.
This differs slightly depending on how you’re using Mastodon, but after adding an image to your toot, you can click it to open the editing panel where you can write in the image description.
There’s no need to over-think it:
1. Describe the medium (“An oil painting”) 2. Describe the subject (“of a cottage in a field”) 3. Describe the mood (“the colours are warm and create a cozy atmosphere”).
Those are the basics. There’s no need to go into extreme detail.
There is a bit more to the thread, but this is the relevant information.
Here is a link to a great example of a comic with accessible image description on remus jackson’s website. Woven, is written by Veronica Hicks & Alesha Nichols, and illustrated by remus jackson. Image descriptions written by Veronica Hicks.
Woven comic - https://remusjackson.com/woven
Alt text for art from Aitch’s general alt text thread – Alt text thread by Aitch on Masto Art
Art: This is trickier! Mention the medium, the subject, the style, the composition and take a stab at the feeling it’s meant to evoke, the feeling of any expressive characters in it.
On Mastodon, the alt text field is actually pretty damn big, so if you want to you can actually go ham when describing a piece of art, and I’ve seen a few screen reader users here mention that they enjoy that with art posts.
Even though I do this stuff for a living, I admit that with art? I go a bit ham lol
Other Resources:
For describing art and comics – Veroniiiica (dot) com - How To Write Alt Text for Digital Comics
Alt Text for Image - University of Washington Images - Accessible Technology
WCAG (Web Content Accessibility Guidelines) site - https://www.w3.org/WAI/WCAG21/Understanding/
9 notes · View notes
openuiux · 1 year
Text
Exciting Discovery: Accessible Palette - Enhancing Web Accessibility!
As we navigate the digital landscape, ensuring inclusivity and accessibility for all users is paramount. I recently stumbled upon Accessible Palette, a remarkable online tool dedicated to promoting web accessibility.
Tumblr media
Accessible Palette provides a range of features and functionalities that make it easier for web designers and developers to create websites that are accessible to individuals with disabilities.
👁️‍🗨️ Some of its standout features include:
✅ Color Contrast Analyzer: This tool helps you analyze text and background color combinations for compliance with accessibility standards, ensuring content is readable by everyone. ✅ Color Blindness Simulator: Gain insights into how users with color blindness perceive your website, allowing you to make necessary adjustments. ✅ Palette Generator: Create harmonious color palettes with built-in accessibility guidelines, ensuring your designs are both visually appealing and inclusive. ✅ WCAG Checker: Accessible Palette checks your color choices against the Web Content Accessibility Guidelines (WCAG), helping you maintain compliance effortlessly. ✅ Accessible Color Picker: This feature suggests accessible color combinations based on your preferences, streamlining the design process. Accessible Palette is a valuable resource for designers, developers, and anyone committed to making the web a more inclusive space. It empowers us to create digital experiences that leave no one behind. I encourage you to explore Accessible Palette and integrate it into your web design workflow. Let's join forces to create an equitable and accessible digital world that benefits everyone. Our shared effort can make this goal achievable through collaboration..
🔗 Explore Accessible Palette: Create color systems with consistent lightness and contrast and join me in championing web accessibility!
----------------------------------------------------------------------------
Are you passionate about creating an internet that's accessible to all? Our latest article, 'Exciting Discovery: Accessible Palette - Enhancing Web Accessibility,' unveils a groundbreaking approach to inclusive web design through accessible color palettes. This exciting discovery can positively impact millions of users with varying abilities.
Sharing this article will help us spread the message of inclusivity and the power of accessible design. Let's join hands in making the web a welcoming space for everyone.
Share now and be a part of this transformative movement! 🌐💫
#WebAccessibility #InclusiveDesign #AccessiblePalette #UIUX #DesignInnovation #DigitalExperience
5 notes · View notes
adasitecompliance · 6 months
Text
ADA Accessibility
Tumblr media
Accessibility For All: How ADA Website Compliance Benefits Everyone
Website design ensures user accessibility, prompting businesses to prioritize ADA compliance. Enacted in 1990, the Americans with Disabilities Act (ADA) marked a significant milestone in fostering inclusivity by addressing disability discrimination across various domains, including digital platforms.
With an estimated 61 million disabled individuals in the United States, ADA compliance assumes paramount importance in the contemporary digital landscape. Failure to achieve ADA accessibility translates to the denial of equal online content access for people with disabilities.
Consequently, businesses must ensure their websites cater to all users, irrespective of disability. However, navigating the intricate web of evolving web accessibility laws poses challenges for companies and organizations.
ADA Site Compliance offers comprehensive solutions, facilitating regulatory compliance. Equipped with a team of adept compliance professionals who track regulatory trends, businesses can ensure their websites meet requisite standards.
What exactly is web accessibility?
Web accessibility encompasses the deliberate planning and development of websites to ensure equitable access and usability for individuals with and without disabilities. By adhering to web accessibility standards, websites enable all users, irrespective of their abilities, to utilize and derive value from web-based services, content, and digital products.
10 Must-Know ADA Accessible Website Benefits
If you are unsure about ADA compliance, take a look at this: Here is a list of ten ways an ADA website benefits everyone:
1. Enhanced Audience Engagement
The integration of WCAG and ADA standards makes websites accessible for individuals with disabilities. By prioritizing adherence to these regulations, businesses engage with an estimated 61 million disabled Americans, thus extending their audience reach significantly.
This proactive initiative provides for broader audience reach, digital marketing, and wider audience engagement for enterprises while underscoring their dedication to fostering diversity and equal access to online resources.
2. Enhanced Search Engine Visibility
While the connection between ADA compliance and Search Engine Optimization (SEO) may not be immediately apparent, it is significant. ADA compliance, such as using alt text, aligns with SEO best practices.
Alt text enhances accessibility and helps search engines effectively understand and index page content. It thus improves the website’s visibility on search engine results pages (SERPs).
3. Optimized User Experience for Users with Screen Readers
An accessible design enhances the user journey, especially those using screen readers, to increase customer satisfaction, thus increasing conversion rates. Effective compliance strategies include:
Clear Information Architecture: Organize content logically to help users of assistive technologies navigate the site effectively.
Navigational Clues: Use breadcrumbs and other navigational aids to guide visitors seamlessly through the website.
Simplified Forms: Use descriptive labels and plain language to simplify form completion and increase conversion rates.
Streamlined Checkout Process: Minimizing the steps required for checkout facilitates faster transactions.
Clear Instructions and Links: Provide concise instructions and descriptive link text at each stage to enhance user understanding and engagement.
Extended Session Timeouts: Ensure that users with assistive technologies have sufficient time to complete tasks without interruptions. These strategies prioritize user satisfaction, engagement, conversion rates, and website performance.
4. Legal Protection
The Americans with Disabilities Act (ADA) mandates online accessibility, emphasizing its significance in ensuring equitable access. With a surge in lawsuits targeting non-compliant websites, adherence to ADA and Web Content Accessibility Guidelines (WCAG) standards offers legal protection, less legal risk, prevents expensive lawsuits, and guarantees user accessibility.
5. Enhanced Brand Image
In today’s socially conscious landscape, diversity and accessibility are not mere buzzwords but integral brand values. ADA-compliant websites signify a brand’s commitment to inclusivity and equal access. This proactive stance enhances brand reputation, fosters consumer goodwill and customer loyalty, and strengthens audience relations.
6. Fosters Creative Exploration
Incorporating more accessible web experiences and design principles demands a commitment to creativity and flexibility in response to evolving trends. Business leaders thus explore innovative solutions and continuously refine website designs to align with accessibility standards.
7. Enhanced Search Engine Optimization (SEO)
Accessible web design plays a vital role in improving SEO and fostering inclusivity. Adhering to WCAG standards by implementing alt-text for images, ensuring straightforward content, and adopting simplified page layouts significantly enhances website SEO.
Furthermore, accessible websites facilitate higher user engagement, reduce bounce rates, and elevate search engine rankings with search engine web crawlers. The website’s online presence and accessibility is further strengthened through additional SEO tactics such as:
Abstaining from using images for textual content
Providing video transcripts
Incorporating descriptive text alternatives for images, links, and buttons
8. Ethical Responsibility
Ensuring web accessibility is both a fundamental human right and an ethical duty. By prioritizing accessibility, you uphold principles of dignity, equality, and inclusivity for elderly individuals and those with disabilities.
9. Employee Retention
Accessible digital platforms empower disabled employees to access essential information, such as important resources like benefits and work schedules, fostering a supportive and inclusive work environment. This increases employee satisfaction and retention as individuals feel valued and accommodated within the organization.
10. Gives a Competitive Advantage
Embracing accessibility not only ensures compliance with regulatory mandates but also drives innovation. By addressing the unique needs of individuals with disabilities, organizations can develop innovative solutions that enhance the overall user experience.
This proactive stance distinguishes them as leaders in promoting inclusion while positioning them ahead of competitors in adopting user-centric design principles.
Web Content Accessibility Guidelines Determine Compliance
Developing an ADA-compliant website necessitates an ongoing process of thoroughly examining elements by web designers. Key considerations to enhance your website traffic usability and accessibility include:
Alternative text for images
Captions for videos
Transcripts for audio content, facilitating accessibility
Optimal color contrast, text size, and keyboard navigation
Assessing Website Accessibility
During the development or reconstruction of a website, it is essential to check accessibility from the outset and continuously throughout the process. Identifying accessibility issues early enables prompt rectification, simplifying the overall correction process.
While adjusting browser settings can reveal basic accessibility aspects, a comprehensive review to ensure compliance with all accessibility standards necessitates a more extensive examination.
While evaluation tools can aid the assessment process, they are not the sole determinant of a website’s accessibility status. Expert evaluation by knowledgeable individuals is indispensable for accurately gauging the accessibility of a website.
Conclusion
The prioritization of digital accessibility underscores proactive engagement with potential customers in the dynamic digital landscape, strategically positioning organizations for prosperity. This concerted effort ensures that all individuals can seamlessly engage with online platforms. Such commitment to accessibility fosters societal benefits by promoting digital equity.
Accessible websites transcend regulatory mandates, embodying the ethos of digital inclusivity. By rendering content, products, and services accessible to the diverse online community, businesses expand their customer base and outreach significantly.
Navigating the intricate web of web accessibility legislation can be challenging for businesses and organizations. ADA Site Compliance offers holistic solutions to ensure alignment with compliance regulations. Get your FREE WEBSITE SCAN today!
youtube
0 notes
captino · 1 year
Text
Web Accessibility Testing
Hi all, I am offering walkthrough lessons on how to test websites for compliance with WCAG(Web Content Accessibility Guidelines) in line with the DHS Trusted Tester Process, Feel free to message me in case you want to learn. Thank you.
2 notes · View notes
aeldata-usa · 9 months
Text
0 notes
scungledfiles · 2 years
Text
I'm seeing a lot of discourse going around on tumblr, especially in the MOGAI community, about image descriptions, and in turn I'm noticing a lot more image descriptions that are either entirely unnecessary or poorly written. So, I'd just like to say the following.
Image descriptions should not be a mile long, and they should only contain the general meaning or information provided in the image they are describing in a reasonably concise format.
Stop providing insanely specific details of images that are not contextually relevant and may even potentially be meaningless to those who require an image description.
If an image is purely decorative it does not need an image description
For additional context, I am a professional web developer. I develop for an organisation of over 20 schools totaling more than 18000 students (not to mention staff and parents). A major component of web development, at least in the contexts I have worked in, is ensuring web content is accessible. I also, on occasion, use a screen reader to access content due to visual overstimulation and am not unfamiliar with the experience of dealing with inaccessible content.
Different countries have different standards that organisations are expected to comply with in order for their website to be considered accessible, but the Web Content Accessibility Guideline (WCAG) from W3C are often considered to be an internationally applied standard, and the full page on alt text for non-text content can be found here: Understanding Success Criterion 1.1.1 | Understanding WCAG 2.0 (w3.org)
An additional tutorial in a more layman friendly format that is based on these guidelines is available here: Images Tutorial | Web Accessibility Initiative (WAI) | W3C
I might make a summary of Dos and Don'ts that would be more specific to tumblr in the future, and I'm happy to answer asks about this, but I'm currently low on spoons and just wanted to get this out of the drafts for now.
12 notes · View notes