WCAG Compliance Knowledge Base

WCAG-1.1.1-alt-text-not-descriptive · content scope

Your website has images with alt text that doesn't properly describe what's shown. Screen reader users who are blind cannot understand what these images contain. Under the ADA Title II rule, all images must have meaningful descriptions.

WCAG-1.1.1-decorative-not-marked · content scope

Your website has decorative images that are being read aloud to blind users when they shouldn't be. This creates unnecessary noise and confusion for people using screen readers. Under the ADA Title II rule, decorative images must be properly marked as decorative.

WCAG-1.1.1-empty-alt-text · content scope

Your website has informational images with empty alt text, making them invisible to screen reader users. People who are blind or have low vision cannot understand what these images show or why they're important. Under the ADA Title II rule, all meaningful images must have descriptive text alternatives.

WCAG-1.1.1-missing-alt-text · content scope

One or more images on your website have no text description. People who are blind or have low vision use screen readers that read web pages aloud — when an image has no description, they have no way to know what the image shows. Under the ADA Title II rule, all informational images must have a text alternative before your compliance deadline.

WCAG-1.2.2-captions-missing · content scope

Videos on your website are missing captions for speech and important sounds. Deaf and hard of hearing people cannot access this content. Under ADA Title II, all prerecorded video with audio must include synchronized captions.

WCAG-1.2.3-audio-description · content scope

Videos on your website show visual information that people who are blind cannot see. You must provide audio description that explains what's happening visually or offer a full text transcript. Under the ADA Title II rule, this is required for all video content.

WCAG-1.2.4-captions-live · content scope

Your live video streams (like city council meetings or public hearings) don't have real-time captions for the spoken audio. Deaf and hard-of-hearing residents cannot follow what's being said. Under the ADA Title II rule, live government meetings must be accessible to all citizens.

WCAG-1.2.5-audio-description-prerecorded · content scope

Videos on your website don't have audio descriptions explaining important visual information like charts, text on screen, or actions that viewers can't hear. Blind and low-vision residents cannot fully understand this content. The ADA Title II rule requires audio descriptions for government video content.

WCAG-1.3.1-heading-structure-invalid · content scope

Your website's headings skip from H1 to H3, or H2 to H5, without the levels in between. Screen readers rely on proper heading order to help blind users navigate your content. Under ADA Title II, this structure must be logically organized.

WCAG-1.3.1-layout-table · cms scope

Your website uses HTML tables to arrange content in columns or rows instead of presenting actual data. Screen readers announce table headers and navigate by rows, making your content confusing for blind users. Under the ADA Title II rule, this creates a barrier that must be fixed.

WCAG-1.3.1-list-not-marked · content scope

Content that looks like a list on your website isn't properly coded as a list. Screen reader users can't navigate through these items efficiently or understand how many items are in the group. This violates ADA Title II requirements for accessible information structure.

WCAG-1.3.1-missing-form-labels · cms scope

Forms on your website have input fields without proper labels, making them unusable for people who rely on screen readers. This prevents citizens from completing essential government services online. Under ADA Title II, all form controls must be properly labeled.

WCAG-1.3.1-table-missing-headers · content scope

Data tables on your website lack proper header markup, making them incomprehensible to screen readers. Blind users cannot understand what each cell contains because the table structure isn't properly defined. Under the ADA Title II rule, this creates a barrier that must be fixed.

WCAG-1.3.2-reading-order · cms scope

Screen readers announce your website's content in the wrong order, making it confusing or impossible to understand. People who rely on assistive technology get a scrambled version of your information. Under ADA Title II, content must be presented in a logical sequence.

WCAG-1.3.3-sensory-instructions · content scope

Instructions on your website tell users to click things like 'the red button on the right' or 'the square icon below.' People using screen readers can't see colors, shapes, or visual layout, so these instructions are meaningless to them. Under ADA Title II, all users must be able to follow your site's instructions.

WCAG-1.3.4-orientation · cms scope

Your website forces mobile users to hold their device in only one direction (portrait or landscape), making it impossible for people who can't rotate their device to use your site. Under ADA Title II, content must work in both orientations unless technically essential.

WCAG-1.3.5-identify-input-purpose · cms scope

Form fields for common information like names, emails, and addresses are missing autocomplete attributes. This makes it harder for people with disabilities to fill out forms and prevents browsers from offering helpful auto-fill suggestions. Under ADA Title II, government forms must support assistive technologies.

WCAG-1.4.10-reflow · cms scope

Your website forces people to scroll left and right to read content when viewed on phones or when zoomed in to 400%. This makes your site unusable for people with low vision who need to magnify text. Under the ADA Title II rule, all content must fit within the screen width.

WCAG-1.4.11-non-text-contrast · cms scope

Important interface elements like buttons, form fields, and icons are too faint to see clearly against their background. People with low vision or color blindness may not be able to identify or use these elements. Under the ADA Title II rule, this is a required fix before your compliance deadline.

WCAG-1.4.12-text-spacing · cms scope

Your website's design breaks when users increase text spacing to help with reading disabilities like dyslexia. Content gets cut off, overlaps, or becomes unusable when people adjust spacing settings their browsers or assistive technology. This violates ADA Title II requirements.

WCAG-1.4.13-hover-focus-content · cms scope

Tooltips or popup content that appears when hovering over elements cannot be dismissed without moving the mouse away, blocking access for keyboard users and people with motor disabilities. Under the ADA Title II rule, users must be able to dismiss these popups using the Escape key.

WCAG-1.4.1-color-as-only-indicator · cms scope

Your website uses color as the only way to communicate certain information — for example, marking required form fields only in red, showing calendar availability only through green and gray colors, or distinguishing chart categories only by color. Approximately 8% of men have some form of color blindness and cannot reliably distinguish certain color combinations. Information conveyed only through color is inaccessible to these users and must also be communicated through text, pattern, shape, or another non-color means.

WCAG-1.4.2-audio-control · cms scope

Audio or video files on your website start playing automatically when the page loads, and visitors cannot pause or stop them. This interferes with screen readers and creates accessibility barriers. Under ADA Title II, auto-playing media must include user controls or be limited to 3 seconds or less.

WCAG-1.4.3-insufficient-contrast · cms scope

Some text on your website is too faint to read clearly. People with low vision, color blindness, or who are viewing the site on a phone in sunlight may not be able to read this content. Under the ADA Title II rule, this is a required fix before your compliance deadline.

WCAG-1.4.3-large-text-contrast · cms scope

Your site's large text (like headings or 18-point text) doesn't have enough contrast against its background. People with low vision or color blindness cannot read this content clearly. Under ADA Title II requirements, large text must meet at least a 3:1 contrast ratio.

WCAG-1.4.4-text-resize · cms scope

Your website breaks when people zoom in to make text larger. Users with low vision who rely on magnification cannot read your content when text gets cut off or overlaps. Under ADA Title II, this prevents equal access to government services.

WCAG-1.4.5-images-of-text · content scope

Your website displays text as pictures instead of actual text. This prevents screen readers from reading the content aloud and stops users from enlarging text or changing fonts. The ADA Title II rule requires using real text instead of text images.

WCAG-2.1.1-keyboard-trap · cms scope

Some interactive elements on your website trap keyboard users — they can Tab into the element but cannot Tab out of it. This prevents people who cannot use a mouse from navigating your site. Under the ADA Title II rule, this blocks access and must be fixed.

WCAG-2.1.1-no-keyboard-access · cms scope

Some buttons, links, or interactive features on your website can only be used with a mouse — people who rely on keyboards cannot access them. This affects users with mobility disabilities who cannot use a mouse. Under the ADA Title II rule, all website functions must work with keyboard navigation alone.

WCAG-2.1.2-no-keyboard-trap · cms scope

Some parts of your website trap keyboard users so they cannot navigate away using Tab or arrow keys. People who cannot use a mouse become stuck and cannot access the rest of your site. Under the ADA Title II rule, this prevents equal access and must be fixed.

WCAG-2.1.4-character-key-shortcuts · cms scope

Your website has keyboard shortcuts that interfere with assistive technology like voice control software. Users who rely on speech recognition may accidentally trigger website functions when trying to dictate text. Under ADA Title II requirements, these shortcuts must be configurable or removable.

WCAG-2.2.1-timing-adjustable · cms scope

Your website automatically logs people out after a period of inactivity without warning them first. This prevents people with disabilities who work more slowly from completing forms or transactions. Under ADA Title II, you must give users control over time limits or provide adequate warning before timeout occurs.

WCAG-2.2.2-pause-stop-hide · cms scope

Your website has moving content like auto-playing slideshows or animations that people cannot pause or stop. Users with attention disorders or vestibular conditions may find this content distracting or physically harmful. Under ADA Title II, you must provide controls to pause, stop, or hide any moving content.

WCAG-2.3.1-flashing-content · content scope

Your website contains animations, videos, or graphics that flash rapidly — more than 3 times per second. This can trigger seizures in people with photosensitive epilepsy. Under ADA Title II, this is a critical safety violation that must be fixed immediately.

WCAG-2.4.1-bypass-blocks · cms scope

Your website lacks a 'skip to main content' link that allows keyboard users to bypass repetitive navigation menus. People who can't use a mouse must tab through dozens of navigation items on every page to reach the actual content. Under ADA Title II, this creates an unreasonable barrier to accessing government services.

WCAG-2.4.2-page-title-duplicate · content scope

Multiple pages on your website have identical titles that appear in browser tabs and search results. Screen reader users cannot distinguish between these pages when navigating, creating confusion and legal compliance issues under ADA Title II.

WCAG-2.4.2-page-title-missing · content scope

Some pages on your website are missing titles that appear in browser tabs and bookmarks. Screen reader users rely on these titles to understand what page they're on and navigate between browser tabs. Under the ADA Title II rule, every page must have a descriptive title.

WCAG-2.4.3-focus-order · cms scope

When people use the Tab key to navigate your website, the focus jumps around in a confusing order instead of flowing logically through the page. Keyboard users and screen reader users cannot navigate your site efficiently. Under ADA Title II, this creates a barrier that must be fixed.

WCAG-2.4.4-link-purpose-unclear · content scope

Some links on your website use vague text like 'click here,' 'read more,' or 'learn more' that doesn't tell the user where the link goes. People who navigate using screen readers often browse a list of all links on a page — if every link says 'click here,' they have no way to tell them apart. This is a required fix under ADA Title II.

WCAG-2.4.5-multiple-ways · cms scope

Your website only provides one way for people to find content — usually just the main menu. Users with cognitive disabilities or unfamiliar visitors need multiple ways to locate information, like search boxes or site maps. ADA Title II requires government sites to offer these alternative navigation methods.

WCAG-2.4.6-headings-labels · content scope

Your website has headings like 'More Information' or 'Click Here' that don't tell users what the section is actually about. People using screen readers rely on headings to navigate your site quickly. Under the ADA Title II rule, headings must clearly describe their content.

WCAG-2.4.7-focus-visible · cms scope

People navigating your website with a keyboard (Tab key) can't see which link or button they've selected because the focus outline is invisible. This makes the site unusable for people who can't use a mouse, including many people with disabilities. Under ADA Title II, visible focus indicators are required.

WCAG-2.5.1-pointer-gestures · cms scope

Your website requires pinch-to-zoom, two-finger swipes, or other multi-finger gestures without providing single-touch alternatives. People who can only use one finger, have tremors, or use assistive devices cannot access these functions. This violates ADA Title II requirements.

WCAG-2.5.2-pointer-cancellation · cms scope

Some buttons or links on your site trigger actions the moment someone starts clicking, without allowing them to cancel by releasing the click elsewhere. This creates accidental actions for people with motor disabilities who may slip while clicking. The ADA Title II rule requires users to be able to cancel pointer actions before completion.

WCAG-2.5.3-label-in-name · cms scope

Form fields and buttons on your website show one label text visually but use different text for screen readers. This confuses voice control users who can't activate elements by saying what they see. Under the ADA Title II rule, visible labels must match the accessible names announced by assistive technology.

WCAG-2.5.4-motion-actuation · cms scope

Your website has features that only work by tilting or shaking a mobile device, with no other way to trigger them. People with mobility impairments who cannot physically move their device will be locked out of this functionality, violating ADA Title II requirements.

WCAG-3.1.1-page-language · cms scope

Your website pages don't specify what language they're written in, which breaks screen readers for blind users. Screen readers need to know whether to pronounce text as English, Spanish, or another language to read it correctly. Under the ADA Title II rule, this is a required fix before your compliance deadline.

WCAG-3.1.2-language-of-parts · content scope

Foreign language words or phrases in your content are not marked with the correct language code. Screen reader users who are blind may hear these words pronounced incorrectly, making content confusing or unintelligible.

WCAG-3.2.1-on-focus-change · cms scope

Form fields or links on your website are automatically submitting forms or redirecting users when they simply tab through the page. This prevents keyboard users and people using screen readers from navigating your site predictably. Under ADA Title II, this creates a barrier that must be fixed.

WCAG-3.2.2-on-input-change · cms scope

Your website's forms or controls automatically change pages, submit information, or trigger major interface changes without warning users first. This confuses people using screen readers and can cause them to lose their place or accidentally submit incomplete forms.

WCAG-3.2.3-consistent-navigation · cms scope

Your navigation menu items appear in different orders on different pages, making it harder for users to find information. This creates confusion for people with cognitive disabilities and those using screen readers. The ADA Title II rule requires consistent navigation.

WCAG-3.2.4-consistent-identification · cms scope

The same buttons, links, or features work differently or have different labels across pages on your site. This confuses users who rely on screen readers or have cognitive disabilities. Under ADA Title II, government websites must provide consistent, predictable experiences.

WCAG-3.3.1-error-identification · cms scope

When people fill out forms on your website and make errors, the system isn't clearly telling them what went wrong. Users with disabilities may not be able to identify or understand the errors, preventing them from completing important government services. Under ADA Title II, form errors must be clearly identified and explained.

WCAG-3.3.2-labels-instructions · cms scope

Your website has form fields that don't tell users what information to enter. People using screen readers or those with cognitive disabilities can't figure out how to complete your forms. This violates ADA Title II requirements and prevents citizens from accessing government services.

WCAG-3.3.3-error-suggestion · cms scope

Your website's error messages tell users something is wrong but don't explain how to fix it. This leaves people stuck and unable to complete forms or tasks. Under ADA Title II compliance requirements, error messages must provide clear guidance on how to correct the problem.

WCAG-3.3.4-error-prevention · cms scope

Your legal or financial forms allow users to submit irreversible transactions without a chance to review or confirm their entries. This creates serious problems for people with disabilities who may misunderstand fields or make input errors. Under ADA Title II, government forms that handle legal commitments or financial data must include error prevention mechanisms.

WCAG-4.1.1-parsing-errors · cms scope

Your website's HTML code has structural errors like duplicate IDs or improperly nested tags. These coding mistakes prevent screen readers and other assistive technologies from properly interpreting your content, creating barriers for disabled users under ADA Title II requirements.

WCAG-4.1.2-button-no-label · cms scope

Some buttons on your website have no text or labels that screen readers can announce. Blind and vision-impaired users cannot understand what these buttons do, blocking them from completing forms or navigating your site. Under the ADA Title II rule, this is a critical accessibility barrier that must be fixed.

WCAG-4.1.2-missing-form-label · cms scope

Form fields on your website have no labels telling users what information to enter. Screen reader users cannot complete forms because they cannot identify what each field is for. Under the ADA Title II rule, all forms must be accessible to complete transactions and access government services.

WCAG-4.1.2-name-role-value · cms scope

Your website has custom interactive elements (like dropdown menus or sliders) that screen readers cannot identify or use. People who are blind or have severe vision impairments depend on assistive technology to understand what these elements do. Under ADA Title II requirements, these widgets must be properly labeled and coded.

WCAG-4.1.3-status-messages · cms scope

When your website displays success confirmations, error messages, or loading updates, screen reader users aren't being notified of these changes. This leaves blind and visually impaired residents unable to know when their form submissions succeed or fail. The ADA Title II rule requires these status updates to be announced.