ADA (Americans with Disabilities Act) and Section 508 both point US organizations toward the same technical target: WCAG accessibility. DOJ's Title II rule now sets specific WCAG 2.1 Level AA deadlines for state and local government websites, April 26, 2027 for governments serving 50,000 or more residents, and April 26, 2028 for smaller governments and special districts. Section 508 sets a different baseline: the Revised Section 508 Standards incorporate WCAG 2.0 Level AA for federal agencies and the technology their contractors supply. Private businesses are not covered by Title II, but the DOJ's web guidance points businesses to WCAG, and settlements and court orders in ADA Title III cases commonly use WCAG 2.1 AA as the benchmark, and lawsuit filings keep climbing year over year. An ADA Section 508 accessibility audit combines automated scanning, manual keyboard and screen reader testing, and a WCAG mapping that shows exactly where a site or app falls short and what to fix first.
Think of this audit like a legal and technical health check for your website or product. Instead of guessing whether you meet local accessibility law, we test against the exact standard that law references and show you precisely where you stand.
- DOJ Title II sets WCAG 2.1 AA deadlines of April 26, 2027 for larger governments and April 26, 2028 for smaller governments and special districts
- The Revised Section 508 Standards incorporate WCAG 2.0 AA for federal agencies and contractors, a different baseline from Title II's WCAG 2.1 AA
- Private businesses are not covered by Title II, but WCAG 2.1 AA is the benchmark most often used in ADA Title III settlements
- ADA website lawsuit filings keep rising year over year
- An audit produces developer-ready findings mapped to WCAG, not just a pass or fail score
- VPAT and ACR documentation supports federal and enterprise procurement
workspace_premium
10+ Years of Accessibility Experience
verified
CPWA, CPACC and WAS Certified Specialists
fact_check
Manual + Automated Testing
hearing
Screen Reader Testing
code
Developer-Friendly Reports
public
Global Accessibility Consulting
Lawsuit Filings Keep Rising
ADA Title III website lawsuit filings have climbed for years. Title III itself names no specific technical standard, but DOJ guidance points businesses to WCAG, and settlements and court orders commonly use WCAG 2.1 AA as the measure of an accessible website.
Public Sector Deadlines Are Now Fixed
The DOJ's Title II rule sets binding WCAG 2.1 AA deadlines: April 26, 2027 for state and local governments serving 50,000 or more residents, and April 26, 2028 for smaller governments and special districts.
Federal Contractors Must Meet Section 508
Federal agencies and the contractors who build for them must meet Section 508, which aligns with WCAG 2.0 AA through the 2017 Section 508 Refresh — a routine requirement in federal procurement.
Most Cases Start With A Letter, Not A Warning
The typical ADA web accessibility case begins with a demand letter or lawsuit, not a government inspection. Testing before that letter arrives is consistently cheaper than defending a claim after it does.
What is included
Websites
Corporate websites, marketing sites, government websites, university websites, healthcare websites, ecommerce journeys, landing pages, blogs, resource libraries, and multilingual content experiences.
Web Applications
Customer portals, admin dashboards, CRMs, internal software, enterprise workflows, complex forms, authenticated user journeys, data tables, reports, notifications, and role-based interfaces.
SaaS Products
B2B platforms, cloud software, analytics dashboards, AI applications, product onboarding flows, account settings, billing workflows, and feature-rich application screens.
Mobile Applications
Native iOS, native Android, hybrid applications, progressive web apps, orientation changes, touch targets, gestures, screen reader flows, zoom behavior, and mobile form interactions.
Digital Documents
PDFs, Word documents, PowerPoint files, forms, reports, policy documents, financial statements, healthcare documents, education resources, and procurement documentation.
Design Systems
Reusable components, UI libraries, pattern libraries, design tokens, Figma components, interaction patterns, and documentation that affects many pages or product screens.
Who it is for
Public-facing teams
Marketing, ecommerce, healthcare, government, education, nonprofit, and service organizations use accessibility audits to make essential public content available to more people.
Product and SaaS teams
Product teams use audits to validate complex workflows, reduce accessibility debt, improve component libraries, and prepare for enterprise accessibility reviews.
Procurement and compliance teams
Legal, compliance, procurement, and sales teams use audit evidence to answer buyer questions, support VPAT work, and document remediation commitments.
What it covers
Website Accessibility Audits
Evaluate public websites against WCAG 2.2 AA using manual testing, automated scanning, keyboard-only navigation, and assistive technologies.
Web Application Accessibility Audits
Review authenticated user journeys, dashboards, complex forms, data tables, notifications, custom widgets, and enterprise workflows.
Mobile Accessibility Audits
Test native and hybrid applications using VoiceOver, TalkBack, keyboard alternatives, zoom, orientation changes, touch target review, and gesture accessibility checks.
PDF And Document Accessibility Audits
Assess PDFs and office documents for tagging, reading order, alternative text, bookmarks, form fields, headings, tables, and screen reader compatibility.
Accessibility Design Reviews
Identify accessibility issues in Figma files, design systems, and component specs before development begins, reducing rework and improving handoff quality.
VPAT And Procurement Reviews
Evaluate products and prepare accessibility documentation that supports enterprise and government procurement conversations.
Missing Alternative Text
Missing or inaccurate alternative text prevents screen reader users from understanding meaningful images, icons, charts, infographics, product photos, and linked graphics. We identify images that need concise alternatives, images that should be marked decorative, and complex visuals that need longer explanations.
Keyboard Accessibility
Many users navigate with a keyboard, switch device, voice control, or assistive technology that relies on keyboard behavior. We test focus order, skip links, menus, modals, tabs, accordions, custom widgets, and form flows without a mouse.
Color Contrast
Low contrast can make text, buttons, icons, form controls, and charts difficult or impossible to perceive. We evaluate contrast for normal text, large text, UI components, focus indicators, disabled states, links, and error messages.
Forms
Forms often block users when labels, instructions, required indicators, validation messages, and error handling are not accessible. We test forms with keyboard navigation and screen readers to confirm users can complete and submit successfully.
Headings And Structure
Headings, lists, landmarks, tables, and reading order help assistive technology users understand a page quickly. We identify skipped heading levels, missing landmarks, and reading-order mismatches.
Dynamic Content
Modern applications often update content without refreshing the page. We test status messages, ARIA live regions, notifications, and single-page app transitions to confirm important changes are announced correctly.
| Feature |
Automated Testing |
Manual Testing |
| Speed |
Fast (minutes) |
Slower (days) |
| Cost |
Low |
Higher, but more accurate |
| Manual WCAG Review |
cancelNo |
check_circleYes |
| Keyboard Navigation |
Limited |
Complete |
| Screen Reader Compatibility |
cancelNo |
check_circleYes |
| Logical Reading Order |
cancelNo |
check_circleYes |
| Meaningful Alternative Text |
cancelNo |
check_circleYes |
| Form Usability |
remove_circlePartial |
check_circleYes |
| Overall User Experience |
cancelNo |
check_circleYes |
Helpful Statistics
-
1 in 6 people The World Health Organization estimates that roughly 1 in 6 people globally live with a significant disability, a substantial share of any organization's customers, patients, students, or employees.
WHO Disability Fact Sheet →
-
WCAG is the international technical baseline. WCAG is the international technical baseline. Regulations and procurement processes worldwide reference WCAG directly or indirectly when defining accessibility requirements.
W3C WCAG →
-
56.1 errors per page The WebAIM Million report has found detectable WCAG failures on the large majority of home pages tested every year since the study began, most commonly low-contrast text, missing alternative text, empty links, and missing form labels.
WebAIM Million →
Choose This Service If You Need
- ADA Title II risk review for government sites
- ADA Title III lawsuit-risk review for private sites
- Section 508 and VPAT procurement readiness
- WCAG 2.1 and 2.2 AA gap analysis
- Accessibility lawsuit and demand-letter response
- Developer-ready remediation roadmap
-
01
1. Discovery & Scoping
We review your platform, page count, workflows, and target standard (WCAG 2.1 AA for ADA Title II/Section 508, or WCAG 2.2 AA) to define audit scope and timeline.
-
02
2. Automated Scanning
We run automated tools across the defined scope to catch code-level issues quickly, giving us a baseline before manual review begins.
-
03
3. Manual Expert Testing
Certified specialists manually test keyboard navigation, focus order, forms, headings, and interactive components against WCAG success criteria.
-
04
4. Assistive Technology Testing
We test with screen readers (NVDA, JAWS, VoiceOver, TalkBack), voice control, and switch access to confirm real-world usability, not just code compliance.
-
05
5. Reporting & Prioritization
Findings are documented with severity, standard references, screenshots, and reproduction steps, then organized into a prioritized remediation roadmap.
-
06
6. Retest & Validation
After your team implements fixes, we retest affected pages or flows to confirm issues are resolved and no new barriers were introduced.
Assistive technologies
NVDA
JAWS
VoiceOver
TalkBack
Keyboard-only navigation
Browser zoom
Voice Control
Switch Control
Tools
Axe
ARC Toolkit
WAVE
Accessibility Insights
Chrome DevTools
Safari
Firefox
React
Next.js
Angular
Vue
WordPress
Drupal
Shopify
Magento
WooCommerce
Laravel
ASP.NET
Java
Flutter
React Native
Executive Summary
A clear summary of audit scope, key risks, priority themes, and recommended next steps for stakeholders.
Accessibility Score
A practical status snapshot that helps teams understand current accessibility maturity and remediation priorities.
Detailed Issue Report
Issue-by-issue findings with screenshots, affected URLs or screens, severity ratings, standard references, and reproduction steps.
Developer Recommendations
Practical remediation guidance, code-level notes, component recommendations, and examples your developers can act on.
Compliance-Ready Documentation
Findings organized to support accessibility statements, VPAT and ACR documentation, and procurement or legal review.
Optional Retest Report
Validation evidence after remediation, showing which issues were fixed and what remains open.
Industries
Healthcare
Accessibility audits for patient portals, provider websites, medical forms, telehealth journeys, and healthcare documents.
Government
Audits for public services, citizen portals, forms, documents, and procurement requirements.
Banking
Audits for financial journeys, statements, account dashboards, authentication flows, reports, and high-risk transactional experiences.
SaaS
Audits for B2B products, dashboards, analytics, onboarding, admin settings, and enterprise procurement readiness.
Education
Audits for university websites, LMS experiences, EdTech platforms, digital documents, admissions journeys, and student services.
Retail
Audits for ecommerce product pages, carts, checkout, filters, account flows, promotions, and customer support journeys.
Proof points
Certified Accessibility Expertise
HalfAccessible brings CPWA, CPACC, and WAS accessibility expertise to audits, remediation support, documentation, and product guidance.
Developer-Friendly Reporting
Reports are written for action. Developers receive clear reproduction steps, expected behavior, affected users, standard mapping, and remediation guidance.
Cross-Border Experience
We support businesses operating across multiple regulatory regions with a single audit benchmarked to the highest applicable standard.
Practical Turnaround
Audit scope is tailored to your product and priorities so your team receives useful findings without unnecessary reporting overhead.
- Page title is unique and descriptive
- Headings follow a logical structure
- Landmarks identify major page regions
- Keyboard users can reach every interactive element
- Focus order matches the visual and logical order
- Visible focus indicators are clear
- No keyboard traps are present
- Links and buttons have meaningful accessible names
- Images have appropriate alternative text
- Text and UI components meet contrast requirements
- Forms have labels, instructions, and accessible error handling
- Dialogs, menus, tabs, and accordions expose state correctly
- Tables include appropriate headers
- Media includes captions or transcripts
- PDFs include tags and a logical reading order
- Mobile screens support zoom, orientation, and large touch targets
- Authentication flows are accessible
- Reports include standard references and remediation guidance
Ready to Reduce ADA and Section 508 Risk?
Whether you are a government agency facing the Title II deadline, a federal contractor preparing a VPAT, or a private business that received a demand letter, our certified specialists will identify every real accessibility barrier and hand your team a prioritized, developer-ready roadmap. Quick audits start at $500, complete audits at $2,000.
Request an Accessibility Audit