Sample Dental Practice

Executive Summary

This is a sample weekly Risk Shield report for Sample Dental Practice (anonymized dental site). We scanned the homepage and three high-intent paths from https://www.kiddodental.com using Google Lighthouse mobile lab, mapped violations to WCAG 2.1 AA criteria, and ranked fix priority for your dev team.

The HIGH ATTENTION priority index reflects 7 distinct issues weighted by severity (critical: 2, serious: 3, moderate: 2). Higher index = more friction on public booking paths. Section 5 lists each issue with the exact selector and suggested fix. Not legal advice.

Recommended sequence: address all P1 critical items within 72 hours, then P2 serious within 7 days, then P3 moderate within 14 days. We estimate this brings you to a defensible posture in < 3 weeks.

Why this matters — ADA / WCAG context

U.S. courts have repeatedly held that the ADA's Title III applies to commercial websites. The de facto standard cited in settlements is WCAG 2.1 Level AA. Plaintiffs typically file class-action suits using automated scan reports (similar in scope to this one) as primary evidence. Below are four recent settlements that directly cited issues of the type we found on your site.

Source: publicly available case dockets. This summary is technical guidance, not legal advice. Consult ADA counsel for case-specific exposure.

Per-page Lighthouse breakdown

Each page was scanned with Google PageSpeed Insights (mobile profile, USA region). Scores below 50 are highlighted red; 50-89 amber; 90+ green. Largest Contentful Paint (LCP) > 2.5s and Cumulative Layout Shift (CLS) > 0.1 directly hurt conversion in addition to WCAG.

7 WCAG findings (sorted by lawsuit-risk weight)

Each finding below maps to a specific WCAG 2.1 AA success criterion. The Affected elements sub-section shows the exact selector and DOM snippet your developer can target. The Suggested fix is ready-to-paste code (verify in your component library / CSS framework).

1. #1 CRITICAL WCAG 1.4.4 (AA) · Resize Text

   Homepage

   `[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.

   Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. [Learn more about the viewport meta tag](https://dequeuniversity.com/rules/axe/4.9/meta-viewport).

   Affected elements (top 1)

   • head > meta
     <meta name="viewport" content="width=device-width, user-scalable=0">
   Suggested fix (html)

   <!-- WCAG 1.4.4: allow zoom -->
   <meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover" />

2. #2 CRITICAL WCAG 4.1.2 (A) · Name, Role, Value

   Homepage

   ARIA attributes must conform to valid values

   Ensure all ARIA attributes have valid values

   Affected elements (top 5)

   • .cycle-pager-active
     <a href="javascript:void(0)" aria-controls="slide 1" aria-label="advance to slide 1" class="cycle-pager-active"></a>
   • a[aria-controls="slide 2"]
     <a href="javascript:void(0)" aria-controls="slide 2" aria-label="advance to slide 2"></a>
   • a[aria-controls="slide 3"]
     <a href="javascript:void(0)" aria-controls="slide 3" aria-label="advance to slide 3"></a>
   • a[aria-controls="slide 4"]
     <a href="javascript:void(0)" aria-controls="slide 4" aria-label="advance to slide 4"></a>
   • a[aria-controls="slide 5"]
     <a href="javascript:void(0)" aria-controls="slide 5" aria-label="advance to slide 5"></a>
   Suggested fix (html)

   <!-- WCAG 4.1.2: ARIA values must be valid (e.g. aria-expanded="true|false") -->
   <button aria-expanded="false" aria-controls="menu">Menu</button>

3. #3 SERIOUS WCAG 4.1.2 (A) · Name, Role, Value

   Homepage

   `[aria-*]` attributes do not have valid values

   Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. [Learn more about valid values for ARIA attributes](https://dequeuniversity.com/rules/axe/4.9/aria-valid-attr-value).

   Affected elements (top 5)

   • div.spot04 > div.mod > div.spotpager > a.cycle-pager-active
     <a href="javascript:void(0)" aria-controls="slide 1" aria-label="advance to slide 1" class="cycle-pager-active">
   • div.spot04 > div.mod > div.spotpager > a
     <a href="javascript:void(0)" aria-controls="slide 2" aria-label="advance to slide 2">
   • div.spot04 > div.mod > div.spotpager > a
     <a href="javascript:void(0)" aria-controls="slide 3" aria-label="advance to slide 3">
   • div.spot04 > div.mod > div.spotpager > a
     <a href="javascript:void(0)" aria-controls="slide 4" aria-label="advance to slide 4">
   • div.spot04 > div.mod > div.spotpager > a
     <a href="javascript:void(0)" aria-controls="slide 5" aria-label="advance to slide 5">
   Suggested fix (html)

   <!-- WCAG 4.1.2: ARIA values must be valid (e.g. aria-expanded="true|false") -->
   <button aria-expanded="false" aria-controls="menu">Menu</button>

4. #4 SERIOUS WCAG 1.4.3 (AA) · Contrast (Minimum)

   Homepage

   Background and foreground colors do not have a sufficient contrast ratio.

   Low-contrast text is difficult or impossible for many users to read. [Learn how to provide sufficient color contrast](https://dequeuniversity.com/rules/axe/4.9/color-contrast).

   Affected elements (top 5)

   • div#hd > div.container > div#utilitynav > a.appointmentrequest
     <a class="appointmentrequest" href="/appointment-request">
   • div.spotlight > div.spot01 > a.first > h2.topic
     <h2 class="topic">
   • div.spotlight > div.spot01 > a > h2.topic
     <h2 class="topic">
   • div.spotlight > div.spot01 > a.last > h2.topic
     <h2 class="topic">
   • div.spotlight > div.spot03 > a.first > h2.topic
     <h2 class="topic">
   Suggested fix (css)

   /* WCAG 1.4.3 requires 4.5:1 contrast for normal text */
   .your-class {
     color: #1f2937;
     background-color: #ffffff;
   }
   /* Verify: https://webaim.org/resources/contrastchecker/ */

5. #5 SERIOUS WCAG 1.4.3 (AA) · Contrast (Minimum)

   Homepage

   Elements must meet minimum color contrast ratio thresholds

   Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds

   Affected elements (top 5)

   • .appointmentrequest
     <a class="appointmentrequest" href="/appointment-request">
   • .first[href$="patient-forms"] > h2
     <h2 class="topic">Patient<br>Forms</h2>
   • a[href$="office-tour"] > h2
     <h2 class="topic">Office<br>Tour</h2>
   • .last[href$="what-sets-us-apart"] > h2
     <h2 class="topic">What Sets<br>Us Apart</h2>
   • .first[href$="preventive-care"] > h2
     <h2 class="topic">Preventive<br>Care</h2>
   Suggested fix (css)

   /* WCAG 1.4.3 requires 4.5:1 contrast for normal text */
   .your-class {
     color: #1f2937;
     background-color: #ffffff;
   }
   /* Verify: https://webaim.org/resources/contrastchecker/ */

6. #6 MODERATE WCAG 1.4.4 (AA) · Resize Text

   Homepage

   Zooming and scaling must not be disabled

   Ensure <meta name="viewport"> does not disable text scaling and zooming

   Affected elements (top 1)

   • meta[name="viewport"]
     <meta name="viewport" content="width=device-width, user-scalable=0">
   Suggested fix (html)

   <!-- WCAG 1.4.4: allow zoom -->
   <meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover" />

7. #7 MODERATE WCAG 1.3.1 (A) · Info and Relationships

   Homepage

   All page content should be contained by landmarks

   Ensure all page content is contained by landmarks

   Affected elements (top 5)

   • .address[href="/north-san-antonio-location"] > .cta
     <span class="cta">North San Antonio</span>
   • .phone[href="tel:210-495-6800"] > .cta
     <span class="cta">(210) 495-6800</span>
   • .phone[href="tel:210-532-3040"] > .cta
     <span class="cta">(210) 532-3040</span>
   • .address[href="/south-san-antonio-location"] > .cta
     <span class="cta">South San Antonio</span>
   • .email
     <a class="email addicon mailto" href="mailto:kiddodentalteam@gmail.com" rel="kiddodentalteam@gmail.com" title="" aria-label="email us"></a>
   Suggested fix (html)

   <!-- Wrap content in landmark roles so screen readers can navigate -->
   <header role="banner">...</header>
   <nav role="navigation">...</nav>
   <main role="main">...</main>
   <footer role="contentinfo">...</footer>

Site screenshots (Lighthouse mobile profile)

Final-frame screenshots captured during the scan. Useful as evidence in your remediation planning meeting.

ROI projection (Dental practice (new-patient appointments))

Estimates use industry-standard ranges for your segment. Plug in your actual numbers to refine — but order-of-magnitude is conservative.

Methodology: lift assumes industry baseline accessibility-related friction reduction (UX research averages 18-32% per segment). Lab/conversion data is correlative, not causal; treat as planning input.

Recommended remediation plan