Title IINew Rule
Need to KnowKey Requirements
What is Title II?
Title II of the Americans with Disabilities Act (ADA) prohibits discrimination based on disability by state and local governments. This federal civil rights law requires state and local governments to provide individuals with disabilities effective communication, reasonable modifications, and an equal opportunity to participate in or benefit from their services, programs, and activities.
The Department of Justice’s new final rule, published on April 24, 2024, updates Title II regulations with specific requirements for ensuring that web content (including documents) and mobile applications are accessible to people with disabilities.
Required Standard
All documents, mobile applications, media, and web content must follow WCAG 2.1, Level AA guidelines, unless a clear exception applies.
Compliance Timeline
| State / Government Size | Compliance Deadline |
|---|---|
| 50,000 or more people | April 24, 2026 |
| 0 to 49,999 people | April 26, 2027 |
| Special district governments | April 26, 2027 |
Conforming Alternate Version Disclaimer
State and local governments should not maintain an inaccessible main web page alongside a separate accessible version of the same content. People with disabilities must receive equal access to content on the same page, not a segregated alternative.
Need to KnowRule Exceptions
The following categories of content are not required to conform to WCAG 2.1, Level AA under the new Title II Final Rule. All conditions listed must be met for an exception to apply.
New Final Rule Exceptions
Archived Web Content
All conditions must apply:
- Created before the compliance date
- Kept only for reference, research, or recordkeeping
- Kept in an area designated for archived content
- Not changed since being archived
Preexisting Conventional Electronic Documents
Both conditions must apply:
- In a word processing, presentation, PDF, or spreadsheet format
- Made available before the compliance date
Third Party Content (Non-Contractual)
- Posted by the entity itself or someone acting on the entity’s behalf
- Subject to a contract that gives the entity oversight or control over accessibility
Individual Documents with Password Protection
All conditions must apply:
- In a word processing, presentation, PDF, or spreadsheet format
- About a specific individual, their property, or their account
- Password-protected or otherwise secured
Preexisting Social Media Posts
Who BenefitsFrom Accessibility?
Digital accessibility is not only a fundamental right for people with disabilities, it benefits a wide variety of users and organizations.
| Group | How Does Accessibility Benefit Them? | Example |
|---|---|---|
| People with Disabilities | Eliminates barriers that hinder access to information and communication. | A person with cerebral palsy who cannot speak clearly benefits from AAC systems, speech synthesizers, or text-to-speech applications. |
| Older Adults | Facilitates digital navigation when visual, hearing, or motor difficulties arise with age. | Larger font sizes and high contrast settings improve reading on mobile devices. |
| People with Temporary Disabilities | Helps those with injuries or momentary health conditions. | A person with a cast arm can use voice commands instead of typing. |
| Varying Digital Literacy | Offers more intuitive and accessible navigation options. | A site with clear instructions and pictograms helps users with low literacy navigate easily. |
| Low-Bandwidth Environments | Improves the experience for users with slow connections or older devices. | An optimized site loads quickly in areas with poor internet coverage. |
| Users Who Prefer Accessible Features | Some users without disabilities prefer accessible options for convenience. | Turning on captions while watching a video in a noisy environment. |
| Companies & Organizations | Ensures compliance with accessibility regulations, improves image, and reaches more customers. | An accessible e-commerce site allows more people to shop online. |
| Government Institutions | Ensures compliance with regulations and inclusion in public services. | An accessible services portal ensures all citizens can use it regardless of ability. |
| Educational Institutions | Facilitates learning for students with different needs and abilities. | An online course with audio, video, and text options improves comprehension for all. |
| Content Creators & Developers | Digital products reach more audiences and improve the overall user experience. | A content creator who adds image descriptions makes their content more inclusive. |
AccessibilityQuick Resources
Materials
DocumentAccessibility
Ensure your Word documents are readable and navigable for all students and colleagues, including those using screen readers and other assistive technologies.
Document Setup
- Always Avoid Scanning Documents: All documents must be original digital versions that can be edited
- Always Start from Accessible Templates: Use GLTHS provided Word templates to more easily create accessible documents
Structure & Navigation
- Proper Heading Structure: Use built-in heading styles (Heading 1, 2, 3) instead of just bold text to create logical document navigation
- Lists and Bullets: Use Word's built-in list formatting rather than manual bullets or numbers
- Reading Order: Organize content logically from top to bottom, left to right
- Table Structure: Add proper column headers and use "Repeat Header Rows" for multi-page tables
Text & Readability
- Readable Fonts: Choose clear, sans-serif fonts (Arial, Calibri, Lato) at minimum 12pt size for body text
- Color and Contrast: Don't rely on color alone to convey information; ensure 4.5:1 contrast ratio minimum
- Write in Plain Language: Use short sentences and paragraphs, an active voice, and avoid technical jargon, abbreviations, and acronyms
Images & Links
- Alternative Text (Alt Text) for Images: Add descriptive alt text to all images, charts, and graphics through the Alt Text menu
- Inline Images: All images must be placed in-line and cannot be "tight" to text
- Meaningful Link Text: Write descriptive hyperlinks ("GLTHS Course Catalog") instead of generic text ("click here")
Graph & ChartAccessibility
Ensure your graphs & charts are legible and navigable for all students and colleagues, including those using screen readers and other assistive technologies.
Chart Design
- Avoid Chart Clutter: Avoid 3D charts, shadows, too many gridlines, backgrounds, and intense colors
-
Color and Contrast: Don't rely on color alone to convey information; ensure 4.5:1 contrast ratio minimum. All parts of charts must have high color contrast to background and each other (bar colors, pie colors, gridlines, labels, legends)
- Patterns, borders, and separating chart elements can help distinguish sections
- Use Common Chart Types: Stick with bar, pie, and line charts when possible
Data Presentation
- Round Numbers When Possible: Reduce mental load by decreasing the amount of decimal points and numbers provided visually
- Sort Data Logically: Make sure bar charts are sorted high to low or vice-versa
- Provide Tables for Complex Charts/Graphs: When charts or graphs cannot be simplified enough, provide an accessible table of the same data
Labeling
- Alternative Text (Alt Text) for Images: Add descriptive alt text to all charts and graphs
- Captions: Add easy to understand captions to all charts and graphs through the References menu
Video & MultimediaAccessibility
Make your educational videos, recorded lectures, and multimedia content accessible to all students and colleagues, including those who are deaf, hard of hearing, blind, or have other disabilities.
Audio & Captions
- Audio Descriptions: When informational actions are happening on screen, add narration describing important visual information for viewers who are blind
- Captions: Provide accurate, synchronized captions for all spoken content and important sound effects
- Transcripts: Create full text transcripts that include speaker identification and sound descriptions
- Clear Audio: Record with minimal background noise and clear speech
Visual Safety
- Avoid Flashing Content: No content must flash more than 3 times per second
- Color and Contrast: Don't rely on color alone to convey information; ensure 4.5:1 contrast ratio minimum
PresentationAccessibility
Make your presentations inclusive for all students and colleagues, including those using screen readers, with mobility limitations, or visual impairments.
Before You Start
- Always Start from Accessible Templates: Use GLTHS provided PowerPoint templates to more easily create accessible documents
- Animation Considerations: Limit or avoid flashing animations that could trigger seizures
Slide Structure
- Slide Structure: Use built-in slide layouts and heading styles for proper reading order
- Reading Order: Organize content logically from top to bottom, left to right, and check all slides with the reading order pane
- Title Text: Ensure all slides have a descriptive title
- Lists and Bullets: Use PowerPoint's built-in list formatting rather than manual bullets or numbers
Text & Readability
- Readable Fonts: Choose clear, sans-serif fonts (Arial, Calibri, Lato) at minimum 12pt size for body text
- Color and Contrast: Don't rely on color alone to convey information; ensure 4.5:1 contrast ratio minimum
- Meaningful Link Text: Use descriptive link text instead of "click here" or raw URLs
- Write in Plain Language: Use short sentences and paragraphs, an active voice, and avoid technical jargon, abbreviations, and acronyms
Images & Tables
- Alternative Text (Alt Text) for Images: Add meaningful descriptions for photos, charts, and graphics using PowerPoint's Alt Text feature
- Inline Images: All images must be placed in-line and cannot be "tight" to text
- Table Headers: Properly format data tables with column and row headers
Social MediaAccessibility
Design your social media posts to be accessible to all students, colleagues, and community members, including those who are deaf, hard of hearing, blind, or have other disabilities.
Images & Media
-
Alternative Text (Alt Text) for Images: Write descriptive alternative text for all images posted to social media
- Text within image posts needs to appear in the post content or ALT text if short enough
- Avoid GIFs and Animations: GIFs and animations are often unstoppable and may contain harmful flashing
- Captions: Provide accurate, synchronized captions for all spoken content and important sound effects
Text & Formatting
- Readable Fonts: Choose clear, sans-serif fonts (Arial, Calibri, Lato) at minimum 12pt size for body text
- Color and Contrast: Don't rely on color alone to convey information; ensure 4.5:1 contrast ratio minimum
- Write in Plain Language: Use short sentences and paragraphs, an active voice, and avoid technical jargon, abbreviations, and acronyms
Platform Best Practices
- CamelCase for Hashtags: Use capital letters for each word in hashtags, e.g., #BackToSchool
-
Use Emojis With Care: Avoid large numbers of emojis and try to place them at the end when possible
- Want to learn more about what emojis mean? Check out the emoji dictionary, Emojipedia!
SurveyAccessibility
Build accessible survey content that is perceivable, operable, and understandable for all students, colleagues, and community members, including those using screen readers, keyboard navigation, or other assistive technologies.
User Experience
- Provide Clear Time Estimates: Let users know up front the expected time to complete the survey
- Show Progress Indicators: Always include progress indicators, especially on multi-page surveys
- Offer Paper Versions: When needed, have a paper version available to be printed
Content
- Write in Plain Language: Use short sentences and paragraphs, an active voice, and avoid technical jargon, abbreviations, and acronyms
TableAccessibility
Ensure your tables in Word documents are properly structured and navigable for all students and colleagues, including those using screen readers and other assistive technologies.
Structure
- Always Use Table Headers: Designate the first row as header rows using Word's "Header Row" option in the Table Design tab
- Proper Table Structure: Use Word's Insert Table feature rather than creating tables with tabs or spaces
- Avoid Merged Cells: Avoid merged cells to prevent breaking table layouts
- Simple Table Layout: Avoid complex nested tables; break complex data into multiple simple tables when possible
Headers & Labels
- Clear Column Headers: Write descriptive, concise headers that clearly identify what data each column contains
- Repeat Header Rows: For multi-page tables, enable "Repeat Header Rows" so headers appear on each page
- Table Captions: Add a descriptive caption above the table using Insert Caption to explain the table's purpose
- Table Summary: For complex tables, include a brief description before the table explaining its structure and key findings
Data & Formatting
- Consistent Data Types: Keep data types consistent within each column (all dates, all numbers, all text)
- No Blank Rows or Columns: Don't use empty rows/columns for spacing; use table formatting options instead
- Text Alignment: Left-align text in data cells; only center-align headers when appropriate
Web ContentAccessibility
Build inclusive web content that works for all students, colleagues, and community members, including those using screen readers, keyboard navigation, or other assistive technologies.
Semantic Structure
- Proper Heading Structure: Use built-in heading styles (Heading 1, 2, 3) instead of just bold text to create logical navigation
- Only One H1 Per Page: Only one H1 tag (Heading 1) is allowed per page
- Use Semantic HTML & WAI-ARIA: Use proper HTML elements for their intended purpose (
button,nav,main,section) and add ARIA labels, roles, and descriptions when needed for complex interactive elements - Use Built-In Features: Lists, tables, and headings should all be created using built-in tools or semantic HTML
- Lists and Bullets: Use
<ul>,<ol>, and<dl>for all lists
Navigation & Links
- Keyboard Navigation: Ensure all interactive elements can be accessed using Tab, Enter, and arrow keys
- Reading Order: Organize content logically from top to bottom, left to right
- Meaningful Link Text: Write descriptive hyperlinks ("GLTHS Course Catalog") instead of generic text ("click here")
- Meaningful Page Title: Use descriptive, unique titles for each page, e.g., "Course Syllabus - Automotive Technology"
Content & Readability
- Alternative Text (Alt Text) for Images: Write concise, descriptive alternative text for all images, charts, and graphics
- Readable Fonts: Choose clear, sans-serif fonts (Arial, Calibri, Lato) at minimum 12pt size for body text
- Color and Contrast: Don't rely on color alone to convey information; ensure 4.5:1 contrast ratio minimum
- Write in Plain Language: Use short sentences and paragraphs, an active voice, and avoid technical jargon, abbreviations, and acronyms
ProcurementAccessibility
Procurement means buying products and services. Accessibility procurement is a planning task, not a cleanup task; requirements must be included before vendor review or contract signing.
Planning: Before You Procure
- State accessibility requirements in the scope, bid language, and contract terms before any vendor review
- Include accessibility for software, websites, learning platforms, documents, hardware, and digital curriculum
- Identify assistive technology compatibility questions early; match scope to real user tasks including forms, alerts, navigation, media, and account access
- Request vendors explain WCAG 2.1 AA support and describe their accessibility duties before committing
Vendor Review
- Obtain a current VPAT or Accessibility Conformance Report (ACR) and ask follow-up questions; reject unsubstantiated "accessible" claims without proof
- Ask which WCAG 2.1 AA criteria the product meets/does not meet and identify all known gaps with remediation timelines and ownership
- Demo must cover keyboard-only use, visible focus, captions, alt text, and basic screen reader compatibility
Decision & Follow-Up
- Tie approval, launch, and fix ownership to measurable, written acceptance criteria
- Maintain written records of questions, responses, and all fix commitments
- Coordinate unresolved issues with leadership and accessibility contacts before signing
- Treat accessibility findings as part of product fit, not optional extras
Common Problems to Avoid
- Purchasing without requesting accessibility evidence
- Accepting incomplete or outdated conformance reports
- Deferring accessibility review to post-implementation
- Skipping real-task demos for key workflows
Emails & NewslettersAccessibility
Accessible email works best when it is clear and simple. Use live text, descriptive buttons, and a reading order that still works when images are blocked or layouts collapse on mobile.
Do This First
- Lead with the message: Subject line, preheader, and opening heading must clearly explain what the email is about and what action is needed
- Build with resilient content: Use live HTML text for the key message, descriptive buttons, and alt text for every meaningful image
- Test fallback states: Check the email with blocked images, dark mode, mobile width, keyboard navigation, and screen reader reading order
Content Checks
- Use plain language and short paragraphs so readers can skim quickly
- Make every button and link clearly state its destination or action
- Repeat essential text that appears inside hero images as real HTML text
Layout Checks
- Prefer a single-column structure with a logical source order
- Use tables only when email-client support requires them, and keep them simple
- Avoid hover-only interactions or content that depends on animation to make sense
Testing Checks
- Confirm body text reaches 4.5:1 contrast and controls meet 3:1 non-text contrast
- Check that linked images still make sense when images are off
- Review any auto-generated caption or transcript links if video is promoted in the message
Common Problems to Avoid
- Sending an image-only flyer as the email body
- Using complex multi-column layouts that collapse into a confusing mobile order
- Relying on color alone to show urgency, status, or discount information
- Writing vague calls to action such as "read more" or "learn more" without context
Resource
Directory
AccessibilityAcronyms
Core Standards & Guidelines
- A11Y: Accessibility (11 letters between A and Y)
- ACR: Accessibility Conformance Report
- ADA: Americans with Disabilities Act
- ARIA: Accessible Rich Internet Applications
- ATAG: Authoring Tool Accessibility Guidelines
- POUR: Perceivable, Operable, Understandable, Robust (WCAG Principles)
- UAAG: User Agent Accessibility Guidelines
- VPAT: Voluntary Product Accessibility Template
- W3C: World Wide Web Consortium
- WAI: Web Accessibility Initiative
- WCAG: Web Content Accessibility Guidelines
Changing to W3C Accessibility Guidelines as of 3.0
Accessibility Specific Media
- AD: Audio Description
- ASL: American Sign Language
- CC: Closed Captions
- SRT: SubRip Subtitle Format
- TTML: Time Text Markup Language
- VTT: Web Video Text Tracks
Assistive Technologies
- AT: Assistive Technologies
- JAWS: Job Access With Speech
- NVDA: Nonvisual Desktop Access
- OCR: Optical Character Recognition
- STT: Speech to Text
- TTS: Text to Speech
Document & Media Formats
- DOCX: Word Document
- EPUB: Electronic Publication
- PDF: Portable Document Format
- PPTX: PowerPoint Document
- RTF: Rich Text Format
Technical & Developmental
- ALT Text: Alternative Text
- ANDI: Accessible Name & Description Inspector
- API: Application Programming Interface
- CSS: Cascading Style Sheets
- DOM: Document Object Model
- GUI: Graphical User Interface
- HTML: Hypertext Markup Language
- UD: Universal Design
- UDL: Universal Design for Learning
- UI: User Interface
- URL: Uniform Resource Locator
- UX: User Experience
AccessibilityGlossary: A
- A11y
- : Numeronym for "accessibility" (A + 11 letters + Y). Typically pronounced "ally," giving the term multiple meanings as it represents both the technical concept and the supportive nature of inclusive design.
- Accessibility
- : The concept of designing physical and virtual spaces and points of contact so that they are usable to all people, with an intentional focus on ensuring usability for people with disabilities. Web accessibility means that websites, tools, and technologies are designed and developed so people with disabilities can perceive, understand, navigate, and interact with them effectively.
- Accessibility Conformance Report (ACR)
- : The final report presented to a client once a full Accessibility Conformance Testing (ACT) has been performed. If you need a legally binding version of the ACR, you would use a version of the Voluntary Product Accessibility Template (VPAT).
- Accessibility Conformance Testing (ACT)
- : Commonly referred to as an accessibility audit. The ACT uses various testing methodologies and tools: primarily automated, manual, and assistive technology (AT) devices.
- Accessibility Object Model (AOM)
- : Often called the Accessibility Tree, this refers to the parts of HTML and ARIA that are understood by assistive technologies.
- Accessibility Tree
- : A subset of the DOM tree that contains accessibility-related information for most HTML elements. It is what assistive technologies use to present and interact with content.
- Accommodation
- : Auxiliary aids and services that are provided upon request in order to facilitate access. Examples include extended time on a test, a sign language interpreter added to an event on request, or a transcript provided on request for a podcast.
- Alternative Text (Alt Text)
- : Text that describes the content and function of an image for people who cannot see it. Every non-text element needs a text equivalent to provide an alternative to the image content.
- Americans with Disabilities Act (ADA)
- : U.S. federal law that prohibits discrimination based on disability and requires accessibility in public accommodations and services.
- API (Application Programming Interface)
- : A set of protocols and tools that define how software components should interact. Accessibility APIs allow assistive technologies to communicate with applications.
- ARIA (Accessible Rich Internet Applications)
- : A specification written by the W3C, defining a set of attributes that you can add to HTML elements to support accessibility. These attributes communicate role, state, and property to assistive technologies via accessibility APIs.
- ASL (American Sign Language)
- : A manual and visual language which uses the hands, arms, and fingers, instead of sound, to communicate words and concepts.
- Assistive Technology (AT)
- : Hardware and software that can be "no-tech" (such as a mouth stick), low-tech (such as a keyboard), or high-tech (such as a screen reader). AT is used to help increase, maintain, or improve the capabilities of performing a task for a person with disabilities.
- ATAG (Authoring Tool Accessibility Guidelines)
- : Guidelines that help make authoring tools themselves accessible and help authors create more accessible content.
- Audio Description (AD)
- : Narration added to the soundtrack to describe important visual details that cannot be understood from the main soundtrack alone. Audio descriptions provide information about actions, characters, scene changes, and on-screen text.
- Automated Testing
- : The use of software tools to automatically scan and identify potential accessibility issues in digital content.
AccessibilityGlossary: B through I
- Baseline
- : The set of technologies that content can rely on having support for accessibility features in user agents and assistive technologies.
- Braille
- : A tactile writing system used by people who are visually impaired, consisting of patterns of raised dots.
- Captions (Closed/Open)
- : Words that describe the audio or sound portion of a program or video. Captions include dialogue, identifying who is speaking, and include non-speech information conveyed through sound, including meaningful sound effects. Closed captions can be turned on/off; open captions cannot.
- Cognitive Accessibility
- : Design considerations for people with cognitive disabilities, including clear navigation, simple language, and consistent layout.
- Color Contrast
- : The difference in luminance between text and its background. WCAG requires minimum contrast ratios for accessibility.
- CSS (Cascading Style Sheets)
- : A style sheet language used for describing the presentation of HTML documents, including accessibility features like focus indicators.
- Digital Accessibility
- : The practice of building digital products so that all users, regardless of their disability, have equal access to the content or functionality of the product.
- DOM (Document Object Model)
- : A programming interface for HTML documents that represents the page structure as a tree of objects.
- Dragon NaturallySpeaking
- : Voice recognition software that allows users to control computers and input text using voice commands.
- EPUB (Electronic Publication)
- : A free and open e-book standard that supports accessibility features like reflowable text and alternative formats.
- Extended Audio Description
- : Audio description that pauses the video when necessary to provide longer descriptions of visual content.
- Focus Indicator
- : A visual indicator that shows which element currently has keyboard focus. WCAG 2.2 specifies that focus indicators must not be hidden by overlapping elements.
- Focus Management
- : The programmatic control of where keyboard focus moves, particularly important in dynamic content and single-page applications.
- GUI (Graphical User Interface)
- : The visual interface through which users interact with digital devices and applications.
- Heading Structure
- : A framework of headings that organizes the content of a web page or document like a table of contents. Headings are hierarchical with Heading 1 (H1) representing the main idea in the document and sub-sections marked with H2, H3, etc.
- HTML (Hypertext Markup Language)
- : The standard markup language used to create web pages, which includes many built-in accessibility features.
- IAAP (International Association of Accessibility Professionals)
- : A non-profit membership organization focused on advancing the accessibility profession globally.
- Interactive Element
- : Part of a web page, app, or system that a user can interact with and it "does something." For example, links and buttons are interactive as clicking a link takes you to a new page, and clicking a button does something on the current page.
- ISO 14289
- : International standard that specifies requirements for PDF accessibility.
- ISO 40500
- : The ISO adoption of WCAG 2.0 as an international standard.
AccessibilityGlossary: J through R
- JAWS (Job Access With Speech)
- : A popular screen reader software for Windows that helps blind and visually impaired users access computer content.
- Keyboard Navigation
- : The ability to navigate and interact with digital content using only a keyboard, without requiring a mouse.
- Keyboard Shortcuts
- : Key combinations that provide quick access to functions, which must be implemented carefully to avoid conflicts with assistive technology.
- Live Region
- : An ARIA technique for announcing dynamic content changes to screen readers without moving focus.
- Low Vision
- : Visual impairment that cannot be fully corrected with glasses, contacts, or surgery but still allows for some functional vision.
- Manual Testing
- : Human evaluation of accessibility, including testing with assistive technologies and checking for usability barriers.
- Motor Disabilities
- : Physical impairments that affect movement, including conditions that limit fine motor control or require alternative input methods.
- NVDA (Nonvisual Desktop Access)
- : A free, open-source screen reader for Windows operating systems.
- OCR (Optical Character Recognition)
- : Technology that converts images of text into machine-readable text, often used to make scanned documents accessible.
- Operable
- : One of the four WCAG principles, meaning that user interface components and navigation must be operable by all users.
- PAC (PDF Accessibility Checker)
- : The globally used, free PDF accessibility checker that has been established since 2010.
- PDF (Portable Document Format)
- : A file format that can be made accessible through proper tagging, alternative text, and logical reading order.
- Perceivable
- : One of the four WCAG principles, meaning that information and user interface components must be presentable to users in ways they can perceive.
- POUR
- : Shorthand for Perceivable, Operable, Understandable, and Robust, which are the foundational human-focused principles of WCAG.
- Reflow
- : The ability of content to adapt to different screen sizes and zoom levels without requiring horizontal scrolling.
- Robust
- : One of the four WCAG principles, meaning that content must be robust enough to work with various user agents and assistive technologies.
- RTF (Rich Text Format)
- : A document file format that supports basic accessibility features like heading structure.
AccessibilityGlossary: S through Z
- Screen Reader
- : A high-tech assistive technology that uses synthetic language to read and navigate digital documents for people with low or no vision, cognitive issues, and other disabilities.
- Section 508
- : U.S. federal law requiring federal agencies to make their electronic information accessible to people with disabilities.
- Semantic Markup
- : The use of HTML markup to ensure content is identified by its meaning as opposed to just its appearance. Semantic markup enables screen readers to more accurately and usefully interpret the content of web pages.
- SRT (SubRip Subtitle Format)
- : A simple text-based subtitle file format commonly used for video captions.
- STT (Speech to Text)
- : Technology that converts spoken words into written text, useful for people with hearing impairments or motor disabilities.
- Switch Control
- : Alternative navigation method that allows users to control devices using external switches, often used by people with severe motor impairments.
- TalkBack
- : Android's built-in screen reader that provides spoken, audible, and vibration feedback.
- Title II (of ADA)
- : The section of the Americans with Disabilities Act that prohibits discrimination on the basis of disability by state and local governments, also known as "public entities."
- Transcripts
- : Text versions of audio content that provide access to spoken information for people who are deaf or hard of hearing.
- TTS (Text to Speech)
- : Technology that converts written text into spoken words, used by screen readers and other assistive technologies.
- TTML (Timed Text Markup Language)
- : An XML-based format for creating captions and subtitles for video content.
- UAAG (User Agent Accessibility Guidelines)
- : Guidelines for making browsers, media players, and other user agents accessible.
- Understandable
- : One of the four WCAG principles, meaning that information and user interface operation must be understandable to users.
- Universal Design
- : Design philosophy that aims to create products usable by all people without need for specialized adaptations.
- UX (User Experience)
- : The overall experience a person has when interacting with a product, which should be inclusive and accessible to all users.
- VoiceOver
- : Apple's built-in screen reader for macOS and iOS devices.
- VPAT (Voluntary Product Accessibility Template)
- : A template to draft an Accessibility Conformance Report (ACR). An ACR clearly states which accessibility standards a product or service meets and warns about any "accessibility blockers" they may encounter.
- VTT (Web Video Text Tracks)
- : A format for displaying timed text tracks (such as subtitles or captions) with HTML5 video elements.
- W3C (World Wide Web Consortium)
- : An international community that develops open standards to ensure the long-term growth of the Web.
- WAI (Web Accessibility Initiative)
- : A sub-group of the W3C focused only on digital accessibility.
- WAVE (Web Accessibility Evaluation Tool)
- : A browser plug-in developed by WebAIM and a semi-automated accessibility testing tool. WAVE can help developers, content editors, and other stakeholders identify a range of accessibility issues on a per-page basis.
- WCAG (Web Content Accessibility Guidelines)
- : An international set of accessibility standards developed through the W3C, in cooperation with individuals and organizations. WCAG's goal is to provide a single, shared standard for digital accessibility that meets the needs of individuals, organizations, and governments worldwide.
- WebVTT
- : The Web Video Text Tracks format for captions, text video descriptions, and other metadata that is time-aligned with audio or video content.
- Windows High Contrast Mode
- : A user setting on Windows which enforces the system to display screens in very high contrast, such as white text on black backgrounds, or any theme a user chooses.
- ZoomText
- : Screen magnification software that enlarges text and graphics on computer screens for users with low vision.