CrestVisor · Accessibility report · WCAG 2.1 / 2.2 AA · $149 — free for you

Maple Heights Dental

www.maple-heights-dental.com · Scanned Sep 25, 2026 · 10 pages checked

Hi Sample Prospect,

Your automated accessibility check against WCAG 2.1 and 2.2 Level AA — the W3C standard (ISO/IEC 40500) — summarized first, with every detail below.

61
out of 100
Accessibility: Needs work

Image descriptions and form labels are in good shape. The top priority: some text is too faint to read.
3
Confirmed issues
157 places to fix, each counted once even if it repeats on every page.
1
Needs a person to check
Things a machine can't judge reliably. Not in the score.
12
Not counted
Items inside embedded video, map or chat widgets — that code belongs to the provider.
Top 3 fixes, in order
1
Some text is too faint to read
Low-contrast text is hard to read for people with low vision and on phones in sunlight. Usually a color change in one stylesheet.
SERIOUS · 107 places · 10 pages · WCAG 2.1 AA
2
Links a screen reader can't name
Icon or image links with no text — a blind visitor just hears “link”. A short label on each fixes it.
SERIOUS · 43 places · 10 pages · WCAG 2.1 AA
3
Links that rely on color alone
Links inside paragraphs look like normal text to color-blind visitors. An underline solves it.
SERIOUS · 7 places · 2 pages · WCAG 2.1 AA
Already working well
✓ Image descriptions✓ Form labels✓ Button names✓ Page language set✓ Page titles✓ Zoom allowed✓ Tap targets big enough✓ Embedded content titled✓ Skip-to-content link
Want these fixed for you?
Most of these are fixable without rebuilding your site.
Book a free 30-minute call Call or text (571) 200-3338
Details for your web developer
Every finding with code examples, WCAG references and page-by-page results (10 pages checked).
Scope of this scan: automated checks catch a subset of WCAG 2.1 / 2.2 AA issues — the ones a machine can detect reliably (color contrast, alt-text presence, ARIA usage, form labels, heading hierarchy, keyboard navigation, reflow at 320px, semantic structure). Many criteria need a person: testing with real screen readers (NVDA, VoiceOver) and judging items like alt-text quality, focus-order meaning, and dynamic content — see “Needs manual review” below. This scan is not, by itself, a guarantee of legal compliance. Not counted: 12 items inside embedded third-party content (maps, videos, booking or chat widgets) — that code belongs to the provider.

Barriers the DOJ specifically names

The U.S. Department of Justice's guidance on web accessibility and the ADA calls out these specific barriers. Here's what our scan found on your site.
✕
Poor color contrast
Low-contrast text (e.g. light gray on white).
 Found — 114 items
?
Using color alone to convey information
e.g. red text as the only marker of a required field.
 Needs manual review
✓
Missing image alt text
Images without a text alternative for screen readers.
 No issues detected
✓
No video/audio captions
Media without captions for deaf/hard-of-hearing users.
 No issues detected
✓
Inaccessible online forms
Missing labels, unclear instructions, or unflagged errors.
 No issues detected
✕
Keyboard access issues
Focus traps, missing skip/bypass, or no visible focus on some controls.
 Found — 2 items

WCAG violations by severity (WCAG 2.1 / 2.2 AA)

Critical
0
Serious
3
Moderate
0
Minor
0
3 unique violation types affecting 157 elements in total. Plus 14 structural findings (landmarks, headings, keyboard) — listed below.

Findings by WCAG principle

WCAG organizes every requirement under four principles — content must be Perceivable, Operable, Understandable, and Robust (“POUR”). Count of distinct issue types under each:
Perceivable Information must be presentable in ways users can perceive (contrast, alt text, captions). 4
Operable Interface and navigation must be operable (keyboard, focus, enough time, no traps). 3
Understandable Content and operation must be understandable (labels, language, predictable behavior). 0
Robust Content must be robust enough for assistive technologies (valid ARIA, name/role/value). 0

Top issues to fix

  • 1. Elements must meet minimum color contrast ratio thresholds
    SERIOUS
    Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds
    Affects 107 elements across 10 pages. WCAG: wcag2aa, wcag143.
    Example: .logo-contact-row > .contact-details > .call-contact-wrapper > .header-area-contact-info > p > a[href="tel:(555) 010-2040"]
    <a href="tel:(555) 010-2040">(555) 010-2040</a>
  • 2. Links must have discernible text
    SERIOUS
    Ensure links have discernible text
    Affects 43 elements across 10 pages. WCAG: wcag2a, wcag244, wcag412.
    Example: .navbar-brand
    <a class="navbar-brand" href="https://maple-heights-dental.com/" aria-label="">
  • 3. Links must be distinguishable without relying on color
    SERIOUS
    Ensure links are distinguished from surrounding text in a way that does not rely on color
    Affects 7 elements across 2 pages. WCAG: wcag2a, wcag141.
    Example: .elementId-8-12
    <a class="builder-editable-elements elementId-8-12" style="color: #337ab7;" href="http://www.guysandstthomas.nhs.uk/our-services/dental/overview.aspx" target="_blank" rel="noopener" aria-label="Guy’s Dental Hospital This link opens in a new
Plus structural findings (heuristic, not formal WCAG rule violations):
  • Content doesn't reflow at 320px — sideways scrolling (WCAG 1.4.10)
    serious
    Affects 1 page.
  • Missing landmarks (banner / main / contentinfo)
    moderate
    Affects 1 page.
  • Interactive elements missing visible focus indicators
    moderate
    Affects 2 pages.
  • Heading hierarchy issues (missing h1 / skipped levels)
    minor
    Affects 10 pages.

What we checked

9 categories passed cleanly · 5 need attention. Categories with no applicable elements on this site are hidden.
✕
Color contrast
Text and meaningful graphics meet WCAG AA contrast ratios.
 2 issues found on 10 pages
✓
Images & alt text
Images, SVGs, and icons expose meaning to screen readers.
 1 check passed
✓
Forms & labels
Form controls are programmatically labeled and use valid autocomplete.
 4 checks passed
✓
ARIA usage
ARIA roles, states, and properties are valid and complete.
 10 checks passed
✕
Link & button names
Every link and button has a discernible accessible name.
 1 issue found on 10 pages
✕
Heading structure
Headings are present, non-empty, and follow a logical hierarchy.
 1 issue found on 10 pages
✕
Landmarks & page structure
Page exposes banner, main, and contentinfo landmarks for screen-reader navigation.
 1 issue found on 1 page
✕
Skip links & keyboard
Tab order is sensible, focus indicators are visible, and a skip-to-main link is present.
 1 issue found on 2 pages
✓
Touch targets (WCAG 2.2)
Tap targets meet the 24×24 px minimum.
 1 check passed
✓
Document language & title
Each page declares a valid <html lang> and has a unique title.
 5 checks passed
✓
Frames & embedded content
iframes have titles, embedded objects expose accessible content.
 2 checks passed
✓
Lists & tables
List markup and data-table markup is structurally correct.
 2 checks passed
✓
Viewport & zoom
Viewport allows pinch-zoom and text resize up to 200%.
 2 checks passed
✓
Multimedia & misc
Captions on audio/video, no duplicate IDs, no server-side image maps.
 1 check passed

Needs manual review

WCAG conformance requires automated testing plus human evaluation. Our scanner flagged these items as inconclusive — a person needs to confirm them (for example, contrast over a background image, or whether color alone carries meaning). They're not counted in the score.
  • Elements must meet minimum color contrast ratio thresholds — 123 elements on 10 pages

Page structure (landmarks)

  • /blogs/ — missing landmark: main
Landmarks let screen-reader users jump between major sections. Missing ones force them to read top-to-bottom every time.

Heading hierarchy

  • / — heading issues: missing_h1, skipped_levels:1
  • /about-us/ — heading issues: missing_h1
  • /contact/ — heading issues: missing_h1
  • /request-an-appointment/ — heading issues: missing_h1
  • /meet-the-doctor/ — heading issues: missing_h1
  • /meet-the-team/ — heading issues: missing_h1

Keyboard navigation

  • /contact/ — 2 element(s) missing visible focus indicator
  • /request-an-appointment/ — 1 element(s) missing visible focus indicator
Visitors using a keyboard (or speech control) need every interactive element reachable, every focus state visible, and a clean Tab order.
What this score is — and isn't. This score is a remediation-priority heuristic, not a conformance verdict. Under WCAG, conformance is all-or-nothing per success criterion and applies to whole pages and complete processes (e.g. an entire booking flow). A genuine “WCAG 2.2 AA” conformance claim is something a site owner self-certifies — W3C does not verify claims — and it must state the date, the scope of pages, the WCAG version and level, and the technologies relied upon. Getting there takes the automated findings above plus the manual review items and human assistive-technology testing.
Why this matters legally: The U.S. Department of Justice has, since 1996, taken the position that the ADA applies to web content — both for state & local government (Title II) and for businesses open to the public (Title III). Businesses have flexibility in how they comply, but the content still has to be accessible; DOJ has enforced this through settlement agreements with companies like Rite Aid, H&R Block, and Peapod. (For state & local government, DOJ's 2024 Title II rule sets WCAG 2.1 AA as the required standard, with federal deadlines: April 26, 2027 for jurisdictions serving 50,000+ people, and April 26, 2028 for smaller jurisdictions and special districts such as school and transit districts.) This is general information, not legal advice.

About this report. This report is generated automatically and reflects what our checks could see on Sep 25, 2026. Automated checks catch only part of WCAG; many criteria need a person to review. Results can vary with your site's technology, hosting and settings, and how federal rules apply depends on your situation. It's general information — not legal or compliance advice, and not a guarantee of compliance.

10 of 10 pages checked.

Tested against WCAG 2.1 / 2.2 Level AA (ISO/IEC 40500) · Generated by CrestVisor · crestvisor.com