WCAG Compliance Knowledge Base
Plain-language explanations of every accessibility issue we check, with step-by-step fix guides for government websites and documents.
Web Accessibility Issues
Perceivable
Content must be presentable in ways all users can perceive.
WCAG 1.1.1 — Non-descriptive Alt Text
moderateWCAG-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 Image Not Marked Null
minorWCAG-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 — Non-text Content (Empty Alt Text on Informational Images)
seriousWCAG-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 on Images
criticalWCAG-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 (Prerecorded) — No Captions on Video
criticalWCAG-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 or Media Alternative
seriousWCAG-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)
seriousWCAG-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) — Level AA
seriousWCAG-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 — Info and Relationships: Heading Structure Skips Levels
moderateWCAG-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 — Table Used for Layout
moderateWCAG-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 — Info and Relationships — List Not Marked Up As List
minorWCAG-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 — Info and Relationships — Missing Form Labels
criticalWCAG-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 Header Markup
seriousWCAG-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 — Meaningful Sequence — Visual Reading Order Not Conveyed in DOM
seriousWCAG-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 Characteristics — instructions rely solely on shape/location
moderateWCAG-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 Locked to Single View
moderateWCAG-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 — autocomplete attributes missing
moderateWCAG-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: Content Requires Horizontal Scrolling at 320px
seriousWCAG-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
seriousWCAG-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 — Content Breaks When Spacing Overrides Applied
seriousWCAG-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 — Content on Hover or Focus — tooltip/popup not dismissible
moderateWCAG-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 Is the Only Visual Means of Conveying Information
seriousWCAG-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 — Auto-Playing Audio Cannot Be Stopped
seriousWCAG-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 Color Contrast
seriousWCAG-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 Below 3:1 Contrast Ratio
moderateWCAG-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 — Resize Text — text cannot be resized to 200% without loss
seriousWCAG-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
moderateWCAG-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.
Operable
Interface components and navigation must be operable by all users.
WCAG 2.1.1 — Keyboard Trap Present
criticalWCAG-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 — Interactive Element Not Keyboard Accessible
criticalWCAG-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
criticalWCAG-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
minorWCAG-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 (Session Timeout with No Warning)
seriousWCAG-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 — Moving Content Cannot Be Paused
seriousWCAG-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 — Three Flashes or Below Threshold
criticalWCAG-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 — No Skip Navigation Link
seriousWCAG-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 Titled — Page Title is Duplicate
moderateWCAG-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 Titled: Page Has No Meaningful Title
seriousWCAG-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 — focus order is illogical
seriousWCAG-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 — Ambiguous Link Text
seriousWCAG-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 to Find Content
moderateWCAG-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 and Labels Not Descriptive
moderateWCAG-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 — keyboard focus indicator not visible
seriousWCAG-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 — multipoint gesture with no single-pointer alternative
seriousWCAG-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
moderateWCAG-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: Visible Label Not in Accessible Name
seriousWCAG-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 — device motion with no alternative
moderateWCAG-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.
Understandable
Information and operation of the UI must be understandable.
WCAG 3.1.1 — Language of Page — lang attribute missing or incorrect
seriousWCAG-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 — inline language change not marked
minorWCAG-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 — Context Changes Unexpectedly on Focus
seriousWCAG-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 — Context Changes Unexpectedly on Input
seriousWCAG-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 — nav order varies across pages
moderateWCAG-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
moderateWCAG-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 — form errors not identified
seriousWCAG-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 or Instructions Missing for Form Inputs
seriousWCAG-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
moderateWCAG-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 — Legal/Financial Form Has No Confirm/Review
seriousWCAG-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.
Robust
Content must be robust enough for diverse user agents and assistive technologies.
WCAG 4.1.1 — Parsing — HTML has duplicate IDs or invalid nesting
moderateWCAG-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 Has No Accessible Name
criticalWCAG-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 — Name, Role, Value: Form Input Has No Accessible Label
criticalWCAG-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 — Custom Widget Missing ARIA Roles
criticalWCAG-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 — Live Region Not Used for Dynamic Updates
moderateWCAG-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.
PDF & Document Accessibility Issues
PDF Accessibility — Document Has No Bookmarks
moderatePDF-TAG-bookmark-missing · document scope
This PDF document has no bookmarks — the navigational links that appear in a PDF reader's sidebar panel and allow readers to jump directly to sections of a document. For screen reader users and all users navigating a long government document, bookmarks are the equivalent of a clickable table of contents. A 50-page annual report or comprehensive plan without bookmarks forces every user to scroll through the entire document to find any given section.
PDF Text Color Contrast Insufficient
seriousPDF-TAG-color-contrast · document scope
Text in your PDF document is too faint to read clearly. People with low vision or color blindness cannot access this content. Under the ADA Title II rule, government PDFs must meet the same accessibility standards as websites.
PDF Accessibility — Form Field Has No Tooltip (Accessible Name)
criticalPDF-TAG-form-field-no-tooltip · document scope
This PDF form has one or more fields where no tooltip has been set. The tooltip is the text a screen reader announces when a user tabs to that form field — without it, the user hears only 'text field' or 'checkbox' with no indication of what information should be entered or selected. This makes the form effectively unusable for blind users trying to complete a permit application, registration, or service request.
Form field tab order incorrect
seriousPDF-TAG-form-tab-order · document scope
Form fields in your PDF don't follow a logical order when people press Tab to move between them. Keyboard users, including people with mobility disabilities who can't use a mouse, get confused and may abandon the form. Under the ADA Title II rule, PDF forms must be keyboard accessible.
PDF Accessibility — Headings Not Tagged as Heading Elements
moderatePDF-TAG-heading-not-tagged · document scope
This PDF contains text that looks like headings — large, bold section titles — but those elements have not been tagged as heading elements in the document's tag structure. Screen reader users navigate long PDF documents by jumping between headings, the same way they navigate web pages. Without heading tags, every part of a multi-section report looks the same to a screen reader, making it impossible to quickly jump to the section the user needs.
PDF Accessibility — Image Has No Alternate Text
criticalPDF-TAG-image-missing-alt · document scope
This PDF contains one or more images that have no alternate text — a text description that a screen reader can read aloud in place of the image. A blind user encountering these images hears nothing, or hears a generic announcement like 'figure,' with no information about what the image shows. Photos, charts, diagrams, maps, signatures, logos, and agency seals in PDF documents all require alternate text if they convey information.
Lists not tagged as list elements
minorPDF-TAG-list-not-tagged · document scope
Lists in your PDF documents aren't properly structured for screen readers. People who are blind or use assistive technology can't navigate these lists efficiently, making your content harder to understand. This creates ADA Title II compliance issues for government documents.
PDF Accessibility — Document Title Not Set in Metadata
moderatePDF-TAG-missing-document-title · document scope
This PDF document either has no title set in its metadata, or the title is set but not configured to display in the title bar. When a screen reader opens a PDF without a title, it announces the filename (such as 'CC-2024-minutes-final-v3-PRINT.pdf') instead of a meaningful document name. Descriptive titles help users orient themselves, especially when multiple documents are open, and are one of the simplest accessibility fixes to apply.
PDF Accessibility — Document Language Not Specified
moderatePDF-TAG-missing-language · document scope
This PDF does not specify its language, so screen readers cannot select the correct pronunciation rules or text-to-speech voice for the document's content. Without a language declaration, a screen reader configured for a Spanish-speaking user may attempt to read English content using Spanish phonetics, producing unintelligible output. Setting the document language is a one-minute fix in Adobe Acrobat's Document Properties.
PDF Accessibility — Incorrect or Missing Reading Order
seriousPDF-TAG-missing-reading-order · document scope
This PDF has tags, but the order in which content is tagged does not match the order a reader would naturally read the page. When a screen reader reads this document, it will read content in the wrong sequence — perhaps reading a sidebar before the main body text, or reading a page footer before the first paragraph. For a multi-column document or a presentation slide, incorrect reading order can make the content completely nonsensical to a blind user.
Document is image-only — no text layer
criticalPDF-TAG-scanned-image-only · document scope
Your PDF document is just a picture of text that screen readers cannot process. Blind and low-vision users cannot access any of the information in this document. Under ADA Title II requirements, all government documents must be accessible to people with disabilities.
PDF Accessibility — Table Cells Have No Header Association
seriousPDF-TAG-table-missing-headers · document scope
This PDF contains a data table where the header cells — the row or column labels that give meaning to the data — have not been properly tagged. When a screen reader user navigates to a cell in the table, they hear the cell value but not its context. For a budget table, this means hearing '$2,400,000' with no indication of which department or budget category the number belongs to.
PDF Accessibility — Untagged Document
criticalPDF-TAG-untagged-document · document scope
This PDF document has no tag structure, which means screen readers cannot read it in a meaningful way. A person who is blind would hear a jumble of text with no headings, no reading order, and no way to navigate the document. This is the most critical PDF accessibility issue and must be fixed before your ADA compliance deadline.
Document Types & Compliance Approaches
Not all documents require the same remediation approach. These articles explain how OctoComply classifies documents and what compliance means for each type.
CAD Drawing / GIS Map
informationalDOC-CLASS-cad-gis
Technical drawings and maps in your documents are invisible to screen readers used by blind residents. You must provide alternative text descriptions or data tables so everyone can access the same information. This is required under ADA Title II compliance.
Complex Data Table Document
informationalDOC-CLASS-complex-tables
Your document contains data tables with multiple header rows, columns, or merged cells that screen readers cannot interpret properly. People who are blind or have low vision cannot understand the relationships between data points. The ADA Title II rule requires government documents to be accessible.
Form (Fillable or Static)
informationalDOC-CLASS-form
Forms in PDFs or documents can't be filled out by people using screen readers or keyboard navigation. Citizens with disabilities may be unable to submit applications, permits, or other required government forms, creating ADA Title II compliance issues.
Document Class — General Information Document
informationalDOC-CLASS-general-information
This document is a general information document — such as a policy, press release, meeting minutes, letter, or report. These documents require full accessibility remediation: proper heading structure, reading order, alt text on images, and tagged tables. This is the standard remediation path and most agencies can handle it with Adobe Acrobat Pro or a remediation service.
Presentation Deck (PDF Export)
informationalDOC-CLASS-presentation-pdf · document scope
PDF presentations from PowerPoint need proper structure and alternative text to be usable by screen readers. People with disabilities may not be able to access meeting materials or public information without these fixes.
Scanned / Image-Only PDF
informationalDOC-CLASS-scanned-image-pdf
Your PDF is a scanned image that screen readers cannot read aloud to blind users. This creates a complete barrier to accessing the information. Under ADA Title II, these documents must be converted to accessible text-based formats.
Technical / Engineering Plan
informationalDOC-CLASS-technical-plan
Technical drawings like site plans and engineering blueprints cannot be read by screen readers or understood by people with visual impairments. Under ADA Title II requirements, you must provide accessible alternatives that convey the same information.
Check if your government website has these issues
OctoComply scans your website for WCAG 2.1 AA violations and gives you a plain-language report with fix instructions. The free tier covers up to 10 pages.
Run a complimentary scan