This is a sample report. The business, website, findings and dates are made up to show the format of an Accesslio audit. They aren't a real client's results.

Accesslio · Sample report

Accessibility audit

Website
Northside Family Dental (example), northsidedental.example
Standard
WCAG 2.2 Level AA
Tested
2 to 4 March 2026; retested 6 March 2026

Summary

  • 5findings in the tested scope, 3 of them high severity
  • 4fixed and verified on retest
  • 1still open, waiting on a third-party vendor

Result: within the tested scope, one WCAG 2.2 Level AA failure remains open (finding 5), so the tested pages don't yet fully meet WCAG 2.2 Level AA. A temporary alternative is in place while the vendor fixes it.

What we tested

Pages

  • Home
  • Services
  • Book an appointment
  • New patients
  • Insurance
  • Contact

Customer journeys

  • Request an appointment
  • Download and complete the new-patient form

Not included

  • The patient portal, which is run by a third-party vendor

Methods

  • Keyboard-only testing in Chrome and Firefox
  • NVDA with Firefox on Windows
  • VoiceOver with Safari on macOS and iOS
  • Zoom to 200% and 400%, and reflow at 320 pixels wide
  • Automated checks with axe DevTools and Lighthouse
  • Color contrast measured with a contrast analyzer

Findings

Severity: High

Finding 1: Appointment form fields have no labels

Where
Book an appointment: First name, Phone and Preferred date fields
Who it affects
Screen reader users hear “edit text” with no name, so they can't tell which field is which. Voice control users can't say the field's name to select it.
Evidence
The fields use placeholder text only. There is no label element and no accessible name. The placeholder disappears as soon as someone starts typing.
WCAG criteria
  • 1.3.1 Info and Relationships (Level A)
  • 3.3.2 Labels or Instructions (Level A)
  • 4.1.2 Name, Role, Value (Level A)
Recommendation
Add a visible label for each field and connect it with the for attribute. Keep placeholders, if any, as examples only.
Retest status
Fixed and verified with NVDA and VoiceOver on 6 March 2026
Before
<input type="text" name="first_name" placeholder="First name">
After
<label for="first-name">First name</label>
<input type="text" id="first-name" name="first_name" autocomplete="given-name">
Severity: High

Finding 2: The “Book now” button can't be reached with a keyboard

Where
Home and Services: the main “Book now” call to action
Who it affects
People who use a keyboard, switch device or other alternative to a mouse can't start a booking.
Evidence
The button is a div element with a click handler. It isn't in the tab order and doesn't respond to Enter or Space.
WCAG criteria
  • 2.1.1 Keyboard (Level A)
  • 4.1.2 Name, Role, Value (Level A)
Recommendation
Use a link to the booking page instead of a div. Native links and buttons work with a keyboard automatically.
Retest status
Fixed and verified with keyboard and NVDA on 6 March 2026
Before
<div class="btn" onclick="openBooking()">Book now</div>
After
<a class="btn" href="/book-an-appointment/">Book now</a>
Severity: Medium

Finding 3: Keyboard focus is hidden behind the menu

Where
All pages: links and buttons just below the sticky header
Who it affects
Keyboard users lose track of where they are on the page when the focused item slides under the menu.
Evidence
When tabbing down the page, focused links scroll under the 96-pixel sticky header and are fully covered.
WCAG criteria
  • 2.4.11 Focus Not Obscured (Minimum) (Level AA, new in WCAG 2.2)
Recommendation
Add scroll padding equal to the header height so focused items always stop below the menu.
Retest status
Fixed and verified in Chrome, Firefox and Safari on 6 March 2026
Fix
html { scroll-padding-top: 7rem; }
Severity: Medium

Finding 4: Insurance list text has low contrast

Where
Insurance: the list of accepted plans
Who it affects
People with low vision, and anyone reading on a phone in bright light, struggle to read the plans.
Evidence
Light gray text (#9A9A9A) on white measures 2.8:1. Normal-size text needs at least 4.5:1.
WCAG criteria
  • 1.4.3 Contrast (Minimum) (Level AA)
Recommendation
Darken the text to #595959 or darker, which measures 7.0:1 on white.
Retest status
Fixed and verified on 6 March 2026 (7.0:1)
Severity: High

Finding 5: The booking widget traps keyboard focus

Where
Book an appointment: the vendor's date picker dialog
Who it affects
Keyboard and screen reader users can't leave the dialog, so they're stuck and can't finish or cancel the booking.
Evidence
Once the dialog opens, Tab cycles inside it and Escape doesn't close it. There is no keyboard-reachable close button.
WCAG criteria
  • 2.1.2 No Keyboard Trap (Level A)
Recommendation
The widget is run by the booking vendor, so the fix is theirs. We sent them the steps to reproduce it. In the meantime, add a phone and email option next to the widget.
Retest status
Open: reported to the vendor on 4 March 2026. The phone and email alternative was added and verified.

Limitations

We tested the pages and journeys listed above, with the browsers and assistive technologies listed, on the dates shown. Other pages, content added later and third-party systems outside the scope weren't tested.

This report records what we found, what was fixed and how we checked it. It isn't a legal opinion or a certificate that the website complies with the ADA.

Want a report like this for your website?

Start with the free homepage scan, or book a complimentary 15-minute review and we'll walk you through what we find.