July 20, 2026
DentalPresence Content Team
ADA-Compliant Website Checklist
Article Summary: A practical accessibility checklist for dental websites, with an important explanation of what ADA-compliant can and cannot mean for a private practice.
The phrase ADA-compliant website is widely used, but it can imply a simple certificate that does not exist. The U.S. Department of Justice says the ADA applies to the goods and services that public accommodations offer on the web, and it identifies medical offices among businesses open to the public. For private businesses, DOJ guidance does not set one detailed web regulation comparable to the 2024 Title II rule for state and local governments. DOJ points to technical standards such as WCAG as helpful guidance.
A practical dental practice program often uses WCAG 2.2 Level AA as a testable accessibility target while counsel evaluates applicable federal, state and local duties. Passing an automated scan alone does not establish legal compliance or usable access.
Page structure and keyboard access
□ Give every page a unique, descriptive title and one clear main heading.
□ Use headings in a logical hierarchy rather than for visual size alone.
□ Identify navigation, main content and footer with semantic landmarks.
□ Provide a skip link to bypass repeated navigation.
□ Make every menu, dialog, slider and form usable with a keyboard.
□ Keep keyboard focus visible and in a logical order.
□ Ensure no component traps focus.
□ Use descriptive link text instead of repeated click here labels.
Images, color and readable layout
□ Add useful text alternatives for informative images and empty alt text for decoration.
□ Describe the purpose of before-and-after images without exposing patient identity.
□ Meet at least 4.5:1 contrast for normal text and 3:1 for large text under WCAG Level AA.
□ Do not use color as the only way to show an error, status or before/after state.
□ Support text resize to 200% without losing content or controls.
□ Test reflow at narrow widths and high zoom.
□ Avoid images of text when real text can provide the same information.
Forms and appointment requests
□ Give each input a programmatically associated visible label.
□ Explain required formats and mark required fields in text, not color alone.
□ Identify errors in text and connect each error to its field.
□ Preserve entered information when validation fails whenever safe.
□ Announce success, failure and loading states to assistive technology.
□ Make date pickers and CAPTCHA alternatives keyboard and screen-reader usable.
□ Test the entire booking journey, including third-party widgets and confirmation pages.
□ Provide an accessible alternative contact method when a vendor limitation cannot be fixed immediately.
Video, audio and documents
□ Caption prerecorded video with synchronized, accurate captions.
□ Provide transcripts for audio-first information.
□ Add audio description or an equivalent text explanation when visual details carry meaning.
□ Avoid autoplay audio; provide pause and volume controls.
□ Audit new-patient forms, finance information and other PDFs for reading order, headings, labels and keyboard access.
□ Prefer accessible HTML for essential information rather than making a PDF the only route.
Content and interaction quality
□ Use plain language for services, preparation and next steps.
□ Explain abbreviations and avoid instructions based only on position, shape or color.
□ Keep navigation and repeated controls consistent.
□ Provide enough time for forms and warn users before a session expires.
□ Make touch targets large enough and avoid interactions that require precise dragging.
□ Respect reduced-motion preferences and avoid flashing content.
□ Keep emergency and contact information easy to find.
Testing and governance
□ Combine automated checks with keyboard-only and screen-reader testing.
□ Include people with disabilities in periodic usability review when feasible.
□ Test on representative mobile and desktop combinations.
□ Put accessibility acceptance criteria into vendor contracts and release reviews.
□ Publish an accessibility contact route and route reports to a named owner.
□ Track defects by impact and verify fixes manually.
□ Re-test templates, booking tools and important pages after material changes.
□ Do not treat an overlay badge or scanner score as proof of compliance.
Evidence and scope
DOJ guidance on web accessibility and the ADA: https://www.ada.gov/resources/web-guidance/
DOJ Title III overview: https://www.ada.gov/topics/title-iii/
W3C WCAG 2.2: https://www.w3.org/TR/WCAG22/
This checklist is educational, not legal advice. Coverage, defenses, remedies and technical obligations depend on the entity, jurisdiction and facts. Obtain legal advice for a compliance position.
Summary & Recommendation
Accessibility is continuous quality work. Set a recognized technical target, test real tasks with more than an automated tool, include third-party systems and give users a functioning way to report barriers. Documenting priorities and fixes is useful, but the outcome that matters is whether people with disabilities can obtain the same practice information and complete the same patient-facing tasks.
Next Step Initiative
Test your appointment journey using only a keyboard today, then schedule a WCAG-informed manual audit that includes your highest-use pages and vendors.