What is Accessible Name?

The label that assistive technologies announce for an interactive element. It is computed from visible text, aria-label, aria-labelledby, or other sources. A button with no accessible name is invisible to screen reader users.

U.S. civil rights law enacted in 1990 that prohibits discrimination based on disability. Title II covers state and local government entities; Title III covers places of public accommodation, including websites and mobile apps. The ADA is the primary legal basis for most website accessibility lawsuits.

Shorthand for Accessible Rich Internet Applications. A W3C technical specification defining a set of roles, states, and properties that can be added to HTML to improve accessibility for users of assistive technology.

What is Audio Description?

A narration track added to a video that describes visual information not conveyed through dialogue — such as actions, scene changes, on-screen text, and facial expressions. Required by WCAG 2.1 AA for prerecorded video (Success Criterion 1.2.5).

A synchronized text representation of spoken dialogue and relevant non-speech audio (e.g., [applause], [door slams]) displayed during video playback. Required by WCAG 2.1 AA (SC 1.2.2) for prerecorded audio-visual content. Auto-generated captions do not meet the legal standard due to high error rates.

What is Color Contrast Ratio?

A mathematical ratio (from 1:1 to 21:1) measuring the difference in luminance between a foreground color and its background. WCAG 2.1 AA requires a minimum ratio of 4.5:1 for normal text and 3:1 for large text (18pt+). WCAG 2.1 AA also requires 3:1 for UI components and graphical objects.

EU Directive 2019/882 requiring that a wide range of products and services — including e-commerce websites, banking apps, e-books, and digital media — be accessible. EU member states must enforce the EAA from June 28, 2025. Technical requirements reference EN 301 549, which incorporates WCAG 2.1 AA.

What is Focus Indicator?

A visible outline or highlight (typically a colored border or ring) that shows which interactive element currently has keyboard focus. WCAG 2.1 AA (SC 2.4.7) requires that keyboard focus be visible. WCAG 2.2 (SC 2.4.11, 2.4.12) adds more specific requirements for focus appearance.

The market-leading screen reader for Windows, developed by Freedom Scientific (part of Vispero). JAWS converts text and UI elements to synthesized speech and braille output. It is the most widely used screen reader among professional users and is commonly used as a baseline testing tool.

What is Keyboard Navigation?

The ability to operate all functionality on a webpage using only a keyboard — without requiring a mouse or touch screen. WCAG Success Criterion 2.1.1 requires that all functionality be operable via keyboard interface. This is essential for users with motor disabilities and is the foundation of most accessibility testing.

A free, open-source screen reader for Windows developed by NV Access. NVDA is widely used by people who cannot afford commercial screen readers and is heavily used for accessibility testing. Combined with Firefox, it forms one of the most common baseline testing combinations.

A third-party JavaScript widget (AccessiBe, UserWay, AudioEye, etc.) that claims to automatically fix website accessibility issues and achieve WCAG compliance. Overlays are widely criticized by accessibility experts and have been rejected by courts as insufficient for ADA compliance. The DOJ has not recognized overlays as an acceptable compliance solution.

ISO standard 14289-1 (Universal Accessibility for PDF) — the technical standard for making PDF documents accessible. PDF/UA compliance is required for Section 508 document accessibility and is the benchmark for legally defensible accessible PDF creation.

WCAG 2.1 Success Criterion 1.4.10: content must be presentable without loss of information or functionality when the viewport is 320 CSS pixels wide (equivalent to 400% zoom on a 1280px-wide screen) — without requiring horizontal scrolling. This supports users who zoom in significantly due to low vision.

What is Screen Reader?

Software that converts on-screen text, images, and interactive elements into synthesized speech or braille output, enabling blind and low-vision users to navigate and consume digital content. Leading screen readers include JAWS (Windows), NVDA (Windows, free), VoiceOver (Apple), and TalkBack (Android).

Section 508 of the Rehabilitation Act requires federal agencies to make their electronic and information technology accessible to people with disabilities — including websites, documents, software, and hardware. Section 508 was refreshed in 2018 to incorporate WCAG 2.0 Level AA as the standard.

The built-in screen reader for Android devices, developed by Google. TalkBack uses touch exploration and gesture-based navigation to allow blind and low-vision users to interact with Android phones and tablets. It is the most widely used mobile screen reader globally.

The built-in screen reader for Apple platforms — macOS, iOS, iPadOS, and tvOS. VoiceOver is the most widely used screen reader for mobile devices globally (via iPhone). Testing with VoiceOver + Safari is essential for comprehensive accessibility testing.

A standardized template — maintained by the IT Industry Council (ITI) — used to create an Accessibility Conformance Report (ACR). VPATs document how a product meets WCAG, Section 508, and/or EN 301 549. Federal agencies require VPATs from vendors before IT procurement.

The internationally recognized technical standard for web accessibility, published by the W3C Web Accessibility Initiative (WAI). WCAG 2.1 (2018) is the current legal standard in most jurisdictions — required by ADA, Section 508, EAA, and dozens of national regulations. Organized around four principles: Perceivable, Operable, Understandable, Robust (POUR).

Accessibility Glossary

Plain-English definitions for 78 digital accessibility terms — from WCAG and ARIA to VPATs and OCR resolution agreements.

78 terms · Updated 2025 · Written by IAAP-certified consultants

A

Accessibility Conformance Report (ACR): A document — produced using a VPAT template — that describes how a software product or digital service meets accessibility standards such as WCAG 2.1 AA or Section 508. Federal agencies require ACRs from vendors before IT procurement.See also: VPAT
Accessible Name: The label that assistive technologies announce for an interactive element. It is computed from visible text, aria-label, aria-labelledby, or other sources. A button with no accessible name is invisible to screen reader users.
Accessible Rich Internet Applications (ARIA): A W3C specification that adds semantic meaning to HTML elements through role, state, and property attributes (e.g., role="dialog", aria-expanded="true"). ARIA bridges the gap between complex UI patterns and assistive technology — but should only be used when native HTML semantics are insufficient.See also: ARIA
ADA (Americans with Disabilities Act): U.S. civil rights law enacted in 1990 that prohibits discrimination based on disability. Title II covers state and local government entities; Title III covers places of public accommodation, including websites and mobile apps. The ADA is the primary legal basis for most website accessibility lawsuits.
Alternative Text (Alt Text): Text associated with a non-text element (typically an image) that conveys the same information or function. Set via the HTML alt attribute (e.g., alt="Bar chart showing 42% growth in Q3"). Decorative images should use alt="" to be ignored by screen readers.
ARIA: Shorthand for Accessible Rich Internet Applications. A W3C technical specification defining a set of roles, states, and properties that can be added to HTML to improve accessibility for users of assistive technology.See also: Accessible Rich Internet Applications (ARIA)
Assistive Technology (AT): Hardware or software that people with disabilities use to interact with computers and digital content. Examples include screen readers (JAWS, NVDA, VoiceOver), screen magnifiers (ZoomText), switch access devices, braille displays, and voice recognition software (Dragon).
Audio Description: A narration track added to a video that describes visual information not conveyed through dialogue — such as actions, scene changes, on-screen text, and facial expressions. Required by WCAG 2.1 AA for prerecorded video (Success Criterion 1.2.5).
Authoring Tool Accessibility Guidelines (ATAG): A W3C standard that defines how content authoring tools (CMS platforms, design tools, document editors) should support the creation of accessible content and be accessible to authors with disabilities.

B

Baseline: The set of browsers and assistive technology combinations used to test a product for accessibility. A common baseline includes JAWS + Chrome, NVDA + Firefox, VoiceOver + Safari on macOS, VoiceOver + Safari on iOS, and TalkBack + Chrome on Android.
Blind / Blindness: Complete or significant loss of vision that prevents a person from reading or perceiving visual content. Blind users typically rely on screen readers, braille displays, and keyboard navigation rather than a mouse and monitor.

C

Caption: A synchronized text representation of spoken dialogue and relevant non-speech audio (e.g., [applause], [door slams]) displayed during video playback. Required by WCAG 2.1 AA (SC 1.2.2) for prerecorded audio-visual content. Auto-generated captions do not meet the legal standard due to high error rates.
Cognitive Accessibility: Design and content practices that support users with cognitive or learning disabilities — including plain language, consistent navigation, error prevention, and minimizing unnecessary cognitive load. Addressed in WCAG 2.1 (Clear Language, Error Prevention) and the forthcoming WCAG 2.2 cognitive criteria.
Color Contrast Ratio: A mathematical ratio (from 1:1 to 21:1) measuring the difference in luminance between a foreground color and its background. WCAG 2.1 AA requires a minimum ratio of 4.5:1 for normal text and 3:1 for large text (18pt+). WCAG 2.1 AA also requires 3:1 for UI components and graphical objects.
Conformance Level: WCAG 2.1 has three levels: Level A (minimum — 30 criteria), Level AA (standard — 50 criteria total, required by ADA, Section 508, and most regulations), and Level AAA (enhanced — 78 criteria, best practice but not globally required).
CPWA (Certified Professional in Web Accessibility): An advanced certification credential awarded by IAAP (International Association of Accessibility Professionals) for practitioners who demonstrate expert-level knowledge of web accessibility, including WCAG, assistive technology, and accessible development.See also: IAAP
CVAA (Communications and Video Accessibility Act): U.S. law (21st Century Communications and Video Accessibility Act, 2010) requiring that advanced communications services and video programming delivered over the internet be accessible to people with disabilities. Enforced by the FCC.

D

Demand Letter (ADA): A legal notice sent by a plaintiff's attorney to a business alleging ADA non-compliance and demanding remediation and/or monetary settlement. Thousands of ADA website demand letters are sent each year, particularly targeting e-commerce and financial services websites.
Disability: Under the ADA, a physical or mental impairment that substantially limits one or more major life activities, a record of such an impairment, or being regarded as having such an impairment. Disabilities affecting digital access include visual, auditory, motor, cognitive, speech, and neurological conditions.
Document Accessibility: The practice of making PDFs, Word documents, PowerPoint presentations, and spreadsheets accessible to people using assistive technology. Accessible documents have tagged structure, reading order, alt text for images, proper heading hierarchy, and color contrast — meeting PDF/UA and Section 508 standards.See also: PDF/UA
Dragon NaturallySpeaking: Leading voice recognition and voice control software by Nuance that allows users to control computers and dictate text entirely by voice. Essential assistive technology for users with motor disabilities who cannot use a keyboard or mouse.
Dyslexia: A learning disability that affects reading fluency, decoding, and spelling. Digital content supports users with dyslexia through sans-serif fonts, sufficient line spacing, short paragraphs, plain language, and the ability to adjust text size and spacing.

E

EAA (European Accessibility Act): EU Directive 2019/882 requiring that a wide range of products and services — including e-commerce websites, banking apps, e-books, and digital media — be accessible. EU member states must enforce the EAA from June 28, 2025. Technical requirements reference EN 301 549, which incorporates WCAG 2.1 AA.See also: EN 301 549
EN 301 549: The European harmonized accessibility standard for ICT products and services (websites, apps, documents, software). EN 301 549 v3.2.1 incorporates WCAG 2.1 Level AA as the web accessibility requirement. Referenced by the European Accessibility Act and European public sector accessibility directive.See also: EAA (European Accessibility Act)
Error Identification: WCAG Success Criterion 3.3.1: if an input error is automatically detected, the item in error must be identified and described to the user in text. This means error messages must be programmatically associated with their form fields so screen readers announce them.

F

Focus Indicator: A visible outline or highlight (typically a colored border or ring) that shows which interactive element currently has keyboard focus. WCAG 2.1 AA (SC 2.4.7) requires that keyboard focus be visible. WCAG 2.2 (SC 2.4.11, 2.4.12) adds more specific requirements for focus appearance.
Focus Management: The practice of programmatically moving keyboard focus to the appropriate element when the UI changes — such as moving focus into a dialog when it opens, or back to the trigger element when it closes. Poor focus management leaves keyboard users stranded in inaccessible states.
Focus Trap: A situation where keyboard focus becomes confined to a region and cannot escape using the Tab key. Focus traps are intentional in modal dialogs (required by ARIA dialog pattern) but are bugs when they occur accidentally on carousels, menus, or other components.
Form Label: A visible text element programmatically associated with a form input using the HTML <label> element (with a for/id pair) or aria-labelledby. Without a proper label, screen readers cannot announce the purpose of form fields, making forms inaccessible.

H

Heading Hierarchy: The logical structure of heading levels (H1–H6) that organizes page content. A page should have one H1, with H2–H6 used in descending order to create an outline. Screen reader users navigate by headings; a broken hierarchy makes it impossible to understand or skim the page structure.
High Contrast Mode: An OS or browser display mode that dramatically increases color contrast — often using black backgrounds with white or yellow text. Windows High Contrast Mode (WHCM) and forced colors mode override website CSS. Accessible websites must function correctly in these modes.

I

IAAP (International Association of Accessibility Professionals): The professional organization for digital accessibility practitioners. IAAP offers certifications including CPACC (foundation), WAS (web accessibility specialist), and CPWA (advanced). IAAP membership and certification signal demonstrated expertise in the field.See also: CPWA (Certified Professional in Web Accessibility)
Input Purpose: WCAG 2.1 Success Criterion 1.3.5: form inputs collecting personal information (name, email, phone, address, etc.) must be programmatically identified so browsers and assistive technology can auto-fill them — reducing cognitive load for users with motor or cognitive disabilities.

J

JAWS (Job Access With Speech): The market-leading screen reader for Windows, developed by Freedom Scientific (part of Vispero). JAWS converts text and UI elements to synthesized speech and braille output. It is the most widely used screen reader among professional users and is commonly used as a baseline testing tool.

K

Keyboard Navigation: The ability to operate all functionality on a webpage using only a keyboard — without requiring a mouse or touch screen. WCAG Success Criterion 2.1.1 requires that all functionality be operable via keyboard interface. This is essential for users with motor disabilities and is the foundation of most accessibility testing.
Keyboard Trap: An accessibility bug where keyboard focus enters a component and cannot escape using standard keys (Tab, Shift+Tab, arrow keys, Escape). WCAG SC 2.1.2 prohibits keyboard traps. They are commonly caused by custom carousels, embedded media players, or auto-focus scripts.See also: Focus Trap

L

Language of Page: WCAG Success Criterion 3.1.1 requires that the default human language of a page be programmatically determinable — set via the HTML lang attribute (e.g., lang="en"). This allows screen readers to use the correct pronunciation rules and language-specific voice synthesis.
Level A / AA / AAA: The three conformance levels in WCAG 2.1. Level A addresses the most severe barriers. Level AA is the globally accepted legal standard (required by ADA, Section 508, EAA, and most regulations). Level AAA represents best practice and is not required globally.See also: Conformance Level
Live Region: An ARIA construct (aria-live="polite" or aria-live="assertive") that causes screen readers to announce dynamic content changes without requiring the user to move focus. Used for status messages, search results, form validation errors, and real-time notifications.
Low Vision: Visual impairment that significantly reduces vision but cannot be fully corrected with glasses or contact lenses. Users with low vision may use screen magnification software, high contrast modes, and large text. WCAG requires that content be usable when zoomed to 200% (SC 1.4.4) and 400% (SC 1.4.10 Reflow).

M

Motor Disability: A physical disability affecting movement, muscle control, or fine motor coordination that makes using a standard keyboard and mouse difficult or impossible. Users may rely on switch access, eye tracking, voice control (Dragon), head pointers, or other alternative input devices.
Motion / Animation: WCAG Success Criterion 2.3.3 (AAA) requires that motion animation triggered by interaction can be disabled unless the animation is essential. The prefers-reduced-motion CSS media query detects this user preference, allowing sites to reduce or eliminate animations for users with vestibular disorders.

N

Name, Role, Value: WCAG Success Criterion 4.1.2: all user interface components must have an accessible name and role that can be programmatically determined, and states, properties, and values that can be set programmatically. This ensures assistive technologies can identify and interact with all UI components.
Non-text Contrast: WCAG 2.1 Success Criterion 1.4.11: user interface components (buttons, form fields, focus indicators) and informational graphical objects must have a contrast ratio of at least 3:1 against adjacent colors. This makes interactive elements visible to users with low vision.
NVDA (NonVisual Desktop Access): A free, open-source screen reader for Windows developed by NV Access. NVDA is widely used by people who cannot afford commercial screen readers and is heavily used for accessibility testing. Combined with Firefox, it forms one of the most common baseline testing combinations.

O

OCR (Office for Civil Rights): The enforcement division within the U.S. Department of Education that investigates accessibility complaints against educational institutions receiving federal funding. OCR resolution agreements require institutions to achieve full WCAG 2.1 AA compliance and implement ongoing accessibility programs.
Operable: The second principle of WCAG (the O in POUR). All interface components and navigation must be operable — meaning all functionality must be accessible via keyboard, timing must be sufficient, users must be able to avoid seizure-inducing content, and navigation must be easy.See also: Perceivable
Overlay (Accessibility Overlay): A third-party JavaScript widget (AccessiBe, UserWay, AudioEye, etc.) that claims to automatically fix website accessibility issues and achieve WCAG compliance. Overlays are widely criticized by accessibility experts and have been rejected by courts as insufficient for ADA compliance. The DOJ has not recognized overlays as an acceptable compliance solution.

P

PDF Accessibility: The practice of ensuring PDF documents can be read and navigated by screen readers and other assistive technology. Accessible PDFs have a tagged structure (headings, lists, tables), a logical reading order, alt text for images, a document title, and proper language settings.See also: PDF/UA
PDF/UA: ISO standard 14289-1 (Universal Accessibility for PDF) — the technical standard for making PDF documents accessible. PDF/UA compliance is required for Section 508 document accessibility and is the benchmark for legally defensible accessible PDF creation.See also: PDF Accessibility
Perceivable: The first principle of WCAG (the P in POUR). All information and user interface components must be presentable to users in ways they can perceive — including text alternatives for non-text content, captions for audio, sufficient color contrast, and content that can adapt to different presentations.
Photosensitive Epilepsy: A neurological condition in which seizures are triggered by flashing or strobing visual content. WCAG Success Criterion 2.3.1 requires that content not flash more than 3 times per second. High-luminance or red flashes are especially dangerous and are evaluated using the General Flash and Red Flash Thresholds.
Plain Language: A writing style using clear, direct language at an appropriate reading level for the intended audience. WCAG 3.1.5 (AAA) recommends content at no higher than a lower secondary education reading level. Plain language reduces barriers for users with cognitive disabilities, lower literacy, and non-native speakers.

R

Reflow: WCAG 2.1 Success Criterion 1.4.10: content must be presentable without loss of information or functionality when the viewport is 320 CSS pixels wide (equivalent to 400% zoom on a 1280px-wide screen) — without requiring horizontal scrolling. This supports users who zoom in significantly due to low vision.
Rehabilitation Act: U.S. federal law including two accessibility-critical sections: Section 504 (prohibiting disability discrimination by federal funding recipients) and Section 508 (requiring federal agencies and contractors to make electronic and information technology accessible).See also: Section 508
Robust: The fourth WCAG principle (the R in POUR). Content must be robust enough to be interpreted reliably by a wide variety of current and future user agents, including assistive technology. This is primarily achieved through valid HTML, correct ARIA use, and following established patterns.
Role (ARIA): Semantic meaning assigned to an HTML element via the role attribute, telling assistive technologies what kind of UI component it is (e.g., role="button", role="dialog", role="navigation"). Many HTML5 elements have implicit roles; ARIA roles extend semantics to custom components.See also: ARIA

S

Screen Reader: Software that converts on-screen text, images, and interactive elements into synthesized speech or braille output, enabling blind and low-vision users to navigate and consume digital content. Leading screen readers include JAWS (Windows), NVDA (Windows, free), VoiceOver (Apple), and TalkBack (Android).
Section 504: Section 504 of the Rehabilitation Act of 1973 prohibits organizations that receive federal financial assistance from discriminating against people with disabilities. It requires equal access to programs and services — including digital platforms. It applies to virtually all universities, hospitals, and nonprofits that accept federal grants.See also: Rehabilitation Act
Section 508: Section 508 of the Rehabilitation Act requires federal agencies to make their electronic and information technology accessible to people with disabilities — including websites, documents, software, and hardware. Section 508 was refreshed in 2018 to incorporate WCAG 2.0 Level AA as the standard.See also: Rehabilitation Act
Semantic HTML: Using HTML elements for their intended semantic meaning rather than just for visual appearance. For example, using <button> for clickable actions (not <div>), <nav> for navigation, <h1>–<h6> for headings, and <table> only for tabular data. Semantic HTML provides built-in accessibility that ARIA supplements but cannot replace.
Skip Navigation: A "Skip to main content" link at the top of each page that allows keyboard users to bypass repeated navigation and jump directly to the main content. Required by WCAG SC 2.4.1. Skip links are typically visually hidden until focused, then become visible.
Status Message: WCAG 2.1 Success Criterion 4.1.3: status messages (search results, cart updates, error summaries, form submission confirmations) must be programmatically determinable through role or property so they can be announced by assistive technology without requiring focus to move to them.
Success Criterion: A specific, testable statement in WCAG that a product must satisfy to conform at a given level (A, AA, or AAA). WCAG 2.1 contains 78 success criteria across 13 guidelines. Each criterion has a clear pass/fail outcome that can be verified during an audit.
Switch Access: An assistive technology input method using one or more physical switches for users with severe motor disabilities. Switch users navigate by scanning through options — making keyboard-accessible, well-ordered content critical. iOS and Android both have built-in switch access support.

T

Tab Order: The sequence in which interactive elements receive keyboard focus when the user presses Tab. Tab order should follow the visual reading order and must not create confusion or traps. Elements with tabindex="0" join the natural order; tabindex values greater than 0 are generally considered an anti-pattern.
TalkBack: The built-in screen reader for Android devices, developed by Google. TalkBack uses touch exploration and gesture-based navigation to allow blind and low-vision users to interact with Android phones and tablets. It is the most widely used mobile screen reader globally.
Text Spacing: WCAG 2.1 Success Criterion 1.4.12: content must remain readable and functional when the following CSS properties are adjusted — line height to 1.5× font size, letter spacing to 0.12× font size, word spacing to 0.16× font size, and spacing after paragraphs to 2× font size.
Time Limits: WCAG Success Criterion 2.2.1: if a time limit is set by content, users must be able to turn it off, adjust it (to at least 10× the default), or extend it (with at least 20 seconds warning and 10 requests). Critical for users with cognitive disabilities and slow typists.
Touch Target Size: WCAG 2.5.5 (AAA) recommends touch targets of at least 44×44 CSS pixels. WCAG 2.2 SC 2.5.8 (AA) requires a minimum of 24×24 CSS pixels with adequate spacing. Larger touch targets reduce errors for users with motor disabilities and older adults.

U

Understandable: The third WCAG principle (the U in POUR). Information and the operation of the user interface must be understandable — including readable text with correct language attributes, predictable behavior, error identification, and input assistance.See also: Operable
User Agent: Any software that retrieves and renders web content for users — including browsers (Chrome, Safari, Firefox), media players, screen readers, and web crawlers. WCAG's Robust principle focuses on ensuring content works across diverse current and future user agents.

V

VoiceOver: The built-in screen reader for Apple platforms — macOS, iOS, iPadOS, and tvOS. VoiceOver is the most widely used screen reader for mobile devices globally (via iPhone). Testing with VoiceOver + Safari is essential for comprehensive accessibility testing.
VPAT (Voluntary Product Accessibility Template): A standardized template — maintained by the IT Industry Council (ITI) — used to create an Accessibility Conformance Report (ACR). VPATs document how a product meets WCAG, Section 508, and/or EN 301 549. Federal agencies require VPATs from vendors before IT procurement.See also: Accessibility Conformance Report (ACR)

W

WAS (Web Accessibility Specialist): A professional certification awarded by IAAP to practitioners who demonstrate expertise in web accessibility testing, development, and standards. WAS-certified professionals pass a rigorous exam covering WCAG, ARIA, assistive technology, and accessible design patterns.See also: IAAP
WCAG (Web Content Accessibility Guidelines): The internationally recognized technical standard for web accessibility, published by the W3C Web Accessibility Initiative (WAI). WCAG 2.1 (2018) is the current legal standard in most jurisdictions — required by ADA, Section 508, EAA, and dozens of national regulations. Organized around four principles: Perceivable, Operable, Understandable, Robust (POUR).
Word Spacing: The space between words in text. WCAG 2.1 SC 1.4.12 (Text Spacing) requires that content remain readable when word spacing is increased to 0.16× the font size. Websites that use pixel-fixed container widths often break at this setting.See also: Text Spacing

Z

ZoomText: Screen magnification software (by Freedom Scientific) for Windows that enlarges the screen up to 60× for users with low vision, and optionally provides text-to-speech. ZoomText is one of the most widely used assistive technologies among older adults with low vision.

Want to know if your site meets these standards?

A free consultation with a certified accessibility specialist will tell you where you stand — and what it takes to get fully compliant.

Book a Free Consultation Download Free WCAG Checklist