Sample report with fictional data. Real reports cover your own public pages and PDFs. Request your free check · Back to AccessReady Health
AccessReady Health · Public accessibility snapshot
Riverside Community Health Center (fictional example)
Automated check of 4 public pages on example.org and 6 linked PDFs · October 31, 2026
Why this matters now. HHS's 2024 Section 504 rule requires organizations that receive HHS funding to make their websites, online forms and mobile apps conform to WCAG 2.1 Level AA. After the May 2026 interim final rule, the deadline is May 11, 2027 for organizations with 15 or more employees (May 10, 2028 for smaller ones).
Accessibility widget detected: UserWay
Overlay widgets do not make a website conform to WCAG. In 2025 the FTC finalized an order requiring one overlay vendor (accessiBe) to pay $1 million and stop claiming its tool makes sites compliant. The issues listed below were found with the widget active.
What patients using assistive technology run into
| Issue | Elements | Severity | Pages |
|---|---|---|---|
| Images have no text alternative, so screen-reader users get nothing (or a file name). axe rule image-alt · wcag2a, wcag111 |
4 | critical | / |
| Form fields have no label, so screen-reader users do not know what to type. axe rule label · wcag2a, wcag412 |
3 | critical | /new-patients/ |
| Zooming is disabled on mobile, which blocks patients who need to enlarge text. axe rule meta-viewport · wcag2aa, wcag144 |
1 | critical | /locations/ |
| Text is too light against its background, so patients with low vision cannot read it. axe rule color-contrast · wcag2aa, wcag143 |
40 | serious | / /new-patients/ |
| Links have no readable name; a screen reader just says "link" with no destination. axe rule link-name · wcag2a, wcag244, wcag412 |
12 | serious | / |
| Links inside text are only distinguishable by color. axe rule link-in-text-block · wcag2a, wcag141 |
6 | serious | /billing/sliding-fee/ |
| Embedded frames (maps, videos, booking widgets) have no title. axe rule frame-title · wcag2a, wcag412 |
2 | serious | /locations/ |
Linked PDFs (patient forms, policies, notices)
| File | Pages | Tagged | Language set | Title shown | Text layer | Unlabeled form fields |
|---|---|---|---|---|---|---|
| New-Patient-Registration.pdf | 3 | No | No | No | Has text | 46 of 46 |
| Sliding-Fee-Application-2026.pdf | 2 | No | No | No | Has text | 17 of 22 |
| Consent-to-Treat.pdf | 1 | Yes | Yes | Yes | Has text | — |
| Notice-of-Privacy-Practices.pdf | 6 | Yes | Yes | Yes | Has text | — |
| Release-of-Information.pdf | 1 | No | No | No | Likely image-only | — |
| Dental-History-Form.pdf | 2 | No | No | No | Has text | 30 of 30 |
An untagged PDF has no structure for a screen reader (no headings, reading order or table structure). Image-only PDFs cannot be read at all without OCR.
What this snapshot does not cover
Automated tools find only part of WCAG failures. Keyboard-only navigation, screen-reader testing (NVDA/VoiceOver), patient portals and scheduling tools from vendors, videos and mobile apps all need manual review, plus documentation of results and remediation dates — which is what the HHS guidance and health center associations recommend keeping on file.
Suggested next step
A fixed-price readiness package: inventory of every patient-facing digital tool, manual WCAG 2.1 AA testing, a prioritized remediation plan your web vendor can execute, remediation of your patient-facing PDF forms, vendor ACR/VPAT requests, and an evidence file with retest dates. Reply to the email this came with, or write to ahmed@accessready.health.