Level AA 2.4.11
Focus not hidden
Focus indicators remain visible and not hidden behind other content.
Website accessibility scanning
Website accessibility scanning for your organization
Scans run on a schedule to find measurable barriers and help you track ADA website compliance progress.
Scheduled WCAG scans
Understand your current website barriers
CloudCentric scans your website on a schedule against WCAG. Problems come back as a list ordered by priority, showing changes since your last scan.
Scheduled WCAG scans
Scans run on a schedule to check your website against WCAG standards.
Priority list of problems
Problems arrive as an ordered priority list, placing major items first.
Record of changes
Each scan details exactly what changed since your previous check.
Organizations checking for accessibility barriers
Different websites have specific pages to scan first for barriers listed by Department of Justice and W3C.
Select your organization type
Pages to scan first
Common website accessibility barriers
Department of Justice guidance lists common website barriers. Scans check for specific structural issues.
0:1
Scan
Who it stops
Examples drawn for this page. Names, text and values shown are an example.
Color contrast checker
Check your color contrast
WCAG asks 4.5:1 for normal text, 3:1 for large text, and 3:1 for control boundaries and key graphics.
Open daily
Courtyard seating, 11 to 9. Reserve a table.
1.0:1
Passes WCAG contrast
Fails WCAG contrast
Your scheduled website accessibility scan cycle
Scans run on a schedule to track progress. Results show up as an organized list.
Scan your website
Automated systems scan your pages for known accessibility barriers.
Review priority list
Results arrive in an ordered list, putting serious problems first.
Fix major issues
Address top priority items on your website before moving down.
Scan again
Next scheduled check shows exactly what changed since your last scan.
Example scan report
ADA website compliance guidelines
Department of Justice and W3C statements provided below serve as general information about website accessibility standards, not as legal advice.
Compliance dates
- April 26, 202750,000 or more people
- April 26, 2028Fewer than 50,000 people, and special district governments
Federal Register published an interim final rule on April 20, 2026, moving Title II dates back one year.
No set technical standard. The Department of Justice points to WCAG and Section 508 as helpful guidance.
Additions in WCAG 2.2
WCAG 2.2 is a W3C Recommendation adding nine success criteria to version 2.1 and removing obsolete 4.1.1 parsing rules.
Level AA 2.5.7
Alternative to dragging
Interfaces provide an alternative to dragging movements for essential actions.
Level AA 2.5.8
Target size
Click and tap targets require a minimum size of 24 by 24 CSS pixels.
Level AA 3.3.8
Sign-in without puzzles
Authentication does not depend on remembering information or solving a puzzle.
Level A 3.2.6
Help in same place
Help links remain in consistent locations across multiple pages.
Level A 3.3.7
No repeated entry
Forms avoid asking for previously entered information twice in one process.
Limits of automated accessibility scanning
W3C says some accessibility checks cannot be automated and require manual review. Automated tools serve as a starting point, as they sometimes give inaccurate results.
Automated checks find problems
Scans identify many structural barriers like missing alt text and poor color contrast.
Manual review remains necessary
W3C notes certain accessibility checks cannot be automated and require human testing.
Federal Trade Commission order
April 2025 final FTC order required a million dollar payment and barred one vendor from claiming automated products make websites WCAG compliant.
Frequently asked questions
- Does a scan make my website compliant?
Scans serve as a starting point to find measurable barriers. W3C states some checks require manual review and cannot be automated. Call us to discuss your accessibility goals.
- Which businesses and governments does the ADA reach?
Title III covers businesses open to the public. Title II covers state and local governments, plus their contractors. Population counts rely on 2020 Census data.
- Which WCAG version do rules use?
Title II rules specify WCAG 2.1 Level AA. WCAG 2.2 became a W3C Recommendation on October 5, 2023. Call to discuss scanning options.
- What does an accessibility scan find?
Scans find measurable barriers like low color contrast, missing image descriptions, unlabeled forms, and missing video captions.
- Does CloudCentric fix the problems found?
Details about fixing problems are not stated here. Call our team to discuss remediation steps after your scan.
- How often do scans run?
Schedule frequency is not stated here. Call us to book a walkthrough and discuss scanning timelines.
- What is an accessibility statement?
Information about statements is not stated here. Call our office to discuss your website needs.
Start tracking your website accessibility
Call our team or book a walkthrough to discuss your scheduled scans.
CharlestonMount PleasantNorth CharlestonIsle of PalmsFolly BeachKiawahBeaufortBlufftonHilton HeadSavannah