The short answer
Pick WCAG 2.2 Level AA as the target for every office site. Fix the shared template once, because a fix to the menu, forms, or booking button reaches every office page. Then check what each office adds: photos, bios, colors, videos, and forms.
Test by hand with the keyboard and browser zoom, and check every office color pair for contrast.
Automated tools help, but they cannot check everything. Ask booking and form vendors for an accessibility conformance report, and give patients a way to report a problem.
Template or office page
Many group sites build every office page from the same parts. That splits the work in two.
Fix once
In the shared template
- Menus, skip link, and heading order
- A visible focus outline on every link and button
- The sticky call or book bar, and the cookie banner
- Button and link sizes on phones
- Form labels, required fields, and error messages
- Base text, link, and button colors
Check each time
On each office page
- Alt text on office, team, and before-and-after photos
- Headings on provider bios and office news
- Directions in text next to the map
- New patient forms posted as PDFs
- An office accent color or co-branded logo
- Captions on office tour and provider videos
After an acquisition, the new office often arrives with its own old site. Check it the same way before you move its pages into the group template. The page layout for each office is in multi-office location pages.
Quick checks by hand
The W3C's Easy Checks are a good first pass. They are quick and need only a browser. Run them on each page type: home, an office page, a provider page, a treatment page, and the booking flow.
Page title
Each office page has its own title that names the office and the town, not the same title on every page.
Images
Photos that carry meaning have alt text that says what they show. Decorative images have empty alt text.
Headings
One main heading, then sections in order. A screen reader user can jump from heading to heading.
Color contrast
Text, buttons, and icons stand out from what is behind them. Use the check below for brand colors.
Zoom to 200%
At 200% browser zoom, text still fits and nothing overlaps or disappears.
Keyboard only
With the Tab key alone you can reach the menu, the call link, and the booking button, and you can always see where you are.
Forms
Every field has a visible label, required fields say so, and errors say what to fix.
Video
Office tour and provider videos have captions.
The W3C says these checks cover a few issues and are quick rather than complete. A full review by someone who tests accessibility goes further.
Brand colors and contrast
Groups often give each office or acquired brand its own accent color. Soft teals, golds, and light grays look calm, but they can fail contrast as button or link colors on white.
- Regular text: 4.5:1. Body copy, links, and button labels.
- Large text: 3:1. At least 18 point, or 14 point bold, such as big headings.
- Icons and controls: 3:1. Form field borders, focus outlines, and icons that carry meaning, against the colors next to them.
- Logos: no requirement. Text that is part of a logo or brand name is exempt.
Brand color contrast check
List each office color pair and what it is used for. The check works out the ratio with the WCAG formula and, for a pair that fails, suggests the nearest text or background shade that passes.
Sticky bars and banners
Call and book bars that stay on screen help patients on phones. WCAG 2.2 added a rule for them: when a link or button gets keyboard focus, it must not be entirely hidden by content the site added, such as a sticky header, a sticky footer, or a cookie banner.
To test, open an office page with the bar showing and press Tab through the whole page. If the focus outline ever disappears behind the bar, add space at the bottom of the page or let focused items scroll clear of it. Button size matters too: WCAG 2.2 asks for pointer targets of at least 24 by 24 CSS pixels, or enough space around smaller ones. Bar layouts that work on phones are in navigation and sticky calls to action.
Booking and form tools
Online booking, web forms, chat, and review widgets usually come from vendors and appear on every office page. One problem in a widget repeats across the whole group.
- Ask for a conformance report. A vendor may document accessibility with a VPAT. Once filled in with test results, it is called an Accessibility Conformance Report (ACR).
- Test it yourself anyway. Book a test visit with the keyboard alone, at 200% zoom, on a phone.
- Keep a phone path. Put the office phone number next to every booking widget, so no patient is stuck if the tool fails.
How booking links point to the right office is in online booking links for dental groups.
What automated tools miss
Automated scanners are useful for catching missing labels, missing alt text, and low contrast across many pages at once. Run one on every page type after each template change.
They are not the whole job. The W3C says tools cannot check all accessibility aspects automatically, and some checks need a person. Chrome's documentation says the Lighthouse accessibility score is a weighted average of automated audits, and manual audits do not affect it. A score of 100 means the automated checks passed, not that the page is easy to use.
Accessibility statement
An accessibility statement tells patients what to expect and how to reach you if something does not work. The W3C suggests it include at least:
- A commitment to accessibility for people with disabilities.
- The standard you apply, such as WCAG 2.2.
- Contact details for people who run into a problem.
It also suggests listing known limits and the steps you take. The W3C offers a free generator. For a group, one statement for the whole site works, with a contact that reaches someone who can fix pages for any office.
When to check
Every template change
Run the automated scan and a keyboard pass on each page type before the change goes live.
Every office launch
New and acquired offices get the quick checks, the color check, and a test booking before launch.
Every quarter
Pick a few office pages at random, run the quick checks, and read any problems patients reported.
Red flags
Scores as the finish line
A full automated score covers only what tools can test. Keyboard, focus, and reading order still need a person.
One-line fixes
Be wary of any product that says one script makes a site fully conformant. W3C says tools cannot check every part of accessibility.
Office colors picked by eye
A soft accent color can fail contrast on white. Check every office color pair before it ships.
A booking tool nobody tested
If the booking widget traps keyboard focus, every office page that uses it has the same problem.
PDF-only forms
A scanned new patient form is hard to use with a screen reader. Offer a web form or an accessible PDF.
No way to report a problem
If a patient cannot use the site, they need a phone number or email to reach someone.
Checklist
Accessibility checklist
0 of 12 done
Related guides
Page speed matters to every patient too; see Core Web Vitals for a practice website. Provider pages that read well are in provider pages for dental groups.
The map of the other group jobs is marketing a multi-location practice or DSO.
For a multi-office group
DDS Web Solutions builds websites and runs search, ads, and reporting for dental practices. Our team has been building websites since 2014, we have served 100+ practices, and our offices are in Sacramento and San Mateo.
For a group, we can review the shared template, test office pages and the booking flow by keyboard, and check office colors before a launch. We do not promise a score or a page with no issues.
FAQ
Which accessibility standard should a dental group follow?
WCAG 2.2 Level AA from the W3C is a sound target. It covers text alternatives, keyboard use, contrast, forms, and more. Questions about which laws apply to your offices belong with your counsel.
Do we have to check every office page?
Check each shared template once, then check what each office adds: photos, bios, colors, videos, and forms. On a shared template, a fix to the menu or the booking button reaches every office page at once.
What contrast ratio does text need?
WCAG 2.2 asks for at least 4.5:1 for regular text and 3:1 for large text, which is at least 18 point, or 14 point bold. Icons, form field borders, and focus outlines need 3:1 against what is next to them. Text in a logo has no contrast requirement.
Is a 100 Lighthouse accessibility score enough?
No. Chrome's documentation says the score is a weighted average of automated audits, and manual audits do not affect it. A page can score 100 and still be hard to use by keyboard.
How big should buttons be on phones?
WCAG 2.2 asks for pointer targets of at least 24 by 24 CSS pixels, or enough space around smaller ones, with a few exceptions such as links inside a sentence.
What should an accessibility statement include?
The W3C lists at least a commitment to accessibility, the standard you apply, such as WCAG 2.2, and contact details for people who run into problems. It also suggests listing known limits and how you test.
Sources
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2
- W3C WAI: Understanding Contrast (Minimum)
- W3C WAI: Understanding Non-text Contrast
- W3C WAI: Understanding Focus Not Obscured (Minimum)
- W3C WAI: Understanding Target Size (Minimum)
- W3C WAI: Easy Checks, a first review of web accessibility
- W3C WAI: Selecting web accessibility evaluation tools
- W3C WAI: Developing an accessibility statement
- ITI: Voluntary Product Accessibility Template (VPAT)
- Chrome for Developers: Lighthouse accessibility score