Sample fix pack

What your web person gets

Your report comes with a fix pack for whoever builds or looks after your website. If your pages use another company's tool, such as online booking or chat, you also get a letter to send that company. This page shows both, from the same demo audit as the sample report, with the practice's name taken out.

If your web person wants to see the work before you order, send them this page.

  • 40 fixes, one for each problem in the report
  • 161 changes to the page code, listed page by page
  • 55 of 55 browser steps passed when software tried the new menus, buttons and forms on the fixed copy

Who gets what

  • Your web person

    Your web designer or web company, or someone in your office who uses your platform's settings. They get the fix pack and a cover letter from you that says what to change and in what order.

  • The company behind each tool on your pages

    Online booking, a patient portal, chat or bill pay. We don't test inside another company's tool, so each one gets a letter asking for its own accessibility report, with anything we found in its part of your page.

  • You

    The report itself, a draft accessibility statement and the few decisions that are yours to make. See the sample report

1. The cover letter to your web person

It goes out in your name, because it's your website, and you can change anything in it. This is the demo's letter with the practice's name, address and theme names taken out. Its steps are written for the platform the site runs on, here WordPress.

Letter to the website vendor

[Date]

To: [your web designer or web company]
Subject: Accessibility fixes for [your website]

We had three pages of our website (home, appointments and contact) evaluated against WCAG 2.1 Level AA by Northshelf LLC. The report found 40 problems in the theme, its scripts and our form settings, and comes with the code for each fix, tested on a copy of the site. Please apply the fix pack to the live site:

  1. The stylesheet a11y-fixes.css: add it to the child theme (style.css, or a separate file enqueued from functions.php).
  2. The script a11y-fixes.js: enqueue it from the child theme's functions.php in the footer, with defer. Where the report says a template change is better (for example the menu buttons, printed by a nav walker), please make it in a child-theme copy of the template.
  3. The page markup changes (161, listed by page in the fix pack), made in the templates, the menu settings or the form plugin as each finding says, so they survive updates.
  4. Remove the theme rules that the fixes replace, as noted for each finding (for example :focus{outline:0} in the child theme's style.css, and the footer script that deletes the quick contact form's labels).
  5. Clear the caching plugin's cache, then check the three pages with the keyboard: every control shows a ring, the menus open with their arrow buttons, Esc closes them, and the pause buttons work.

None of the changes needs access to form entries or other patient information. They touch the theme, the menu and the form settings only. Please take a backup first, and tell us when the changes are live so Northshelf can recheck the pages.

For technical questions about the fixes, call Northshelf LLC at (586) 217-0032.

Thank you,
[Name], [Practice name]

2. What's in the fix pack

A folder of files that comes with the report. Every pack has the fix list and the read-me. When we test the fixes on a saved copy of your pages, as we did for all 40 in this demo, the pack also holds the tested stylesheet, script and page changes.

  • README.txt

    Where each file goes, and our phone number for questions.

    Read it first

  • fixes.html

    Every fix by finding, in the report's order: where the problem is, where to fix it on your platform, and the code.

    Read it next

  • a11y-fixes.css

    The stylesheet. Each block names the finding it fixes.

    Goes in the child theme

  • a11y-fixes.js

    The script for the menu buttons, the pause buttons and keyboard focus.

    Goes in the child theme, loaded in the footer

  • page-edits.html

    The 161 changes to the page code, page by page, in the order we made them.

    Made in the templates, the menu and the form settings

3. One fix, the way the fix list shows it

Each fix has the same parts: plain words for you, then where it is, how we found it, where it goes on your platform and the code. In this demo, testing software and an AI model ran the checks, driving the browser and reading the page code and the pictures. We've shortened a few lines and put file names in plain words.

MOT-01. The home page background video loops with no way to pause it Serious

Pages
Home
Criteria
2.2.2 Pause, Stop, Hide (Level A)
Controlled by
The practice's own site (theme, plugins or form settings)
Impact on patients
High

The video at the top of the home page plays in an endless loop behind the main heading and the appointment button, and there's no button to stop it. Visitors with attention or reading difficulties, or who feel unwell from motion, can't switch it off. The fix adds a Pause / Play button just above the hero text, in the site's own dark blue.

Where: The home page hero: the video behind the main heading and the "Request An Appointment Today!" button (autoplay, loop, muted, no controls). Nothing on the page pauses it, and the movement is decorative, so the "essential" exception doesn't apply.

How found: the browser check of moving content found no pause control. IBM's checker can't decide video controls on its own, and the page code and the page pictures confirmed the problem.

Where to fix it in WordPress: The theme template that prints the home page hero, in the child theme. Add the button inside the caption, after the appointment link, and add the script to the child theme (for example a small file loaded from functions.php). Then clear the caching plugin's cache.

Page markup, 1 edit, on Home:

Before

<a href="/appointments/" class="btn fadeInUp wow"> Request An Appointment Today! </a>

After

<a href="/appointments/" class="btn fadeInUp wow"> Request An Appointment Today! </a>
<button type="button" class="a11y-video-toggle"
        data-a11y-what="background video">Pause background video</button>
Show the stylesheet and script for this fix

CSS (in a11y-fixes.css), shortened

/* MOT-01 (2.2.2): Pause / Play button for the home page background video.
   White text on #0040a3 is 9.28:1. */
.video_holder .carousel-caption .a11y-video-toggle {
  display: block;
  margin: 14px auto 0;
  padding: 7px 14px;
  border: 2px solid #fff;
  border-radius: 999px;
  background: #0040a3;
  color: #fff;
  cursor: pointer;
}

Script (in a11y-fixes.js), slightly simplified

/* MOT-01 (2.2.2): the button's label and action follow the video's
   real state, so they stay right when a browser blocks autoplay. */
function fixMot01() {
  var video = document.querySelector('.video_holder video');
  var btn = document.querySelector('.a11y-video-toggle');
  if (!video || !btn) { return; }
  var what = btn.getAttribute('data-a11y-what') || 'video';
  function show() { btn.textContent = (video.paused ? 'Play ' : 'Pause ') + what; }
  btn.addEventListener('click', function () {
    if (video.paused) { video.play(); } else { video.pause(); }
    show();
  });
  video.addEventListener('play', show);
  video.addEventListener('pause', show);
}

Fixed in the demo copy. Afterwards the checks found nothing on the three pages that moves without a pause button.

For three more findings in the same layout, see the sample report.

4. Who controls each fix, and what to do first

The report says which part of the site each problem is in, so the right person gets it. From the demo, with the plugin and theme names taken out. One finding can sit in more than one part.

Who can change each part of the demo site, and how many findings are in it
Part of the siteWho can change itFindings
Theme stylesheet and templatesThe practice, through whoever maintains the site38
The two forms' settingsThe practice, in WordPress5
The cookie notice pluginThe practice for its settings, the plugin's maker for its code5
Google MapsThe practice for the frame's title and the text beside it. Everything inside the map is Google's1
Patient portal, online booking, bill payThe companies that provide themNone linked from these pages
Anything added through Google Tag ManagerWhoever manages the practice's Tag Manager accountNot loaded in our scans

Then the order of work, most important first. Fixes to the shared header, menu and footer change every page at once.

  1. Level A problems that block keyboard and screen reader users (12 in the demo)
  2. Serious Level AA problems with focus and contrast (4)
  3. Moderate problems (16)
  4. Minor problems (8)
  5. Changes we recommend beyond WCAG 2.1 AA, if there's time

5. The letter to a tool's company

The demo's three pages had no booking, portal or payment tool, so its report had no letter like this. This is the letter our reports use, with its blanks left in. An accessibility conformance report (often called a VPAT or ACR) is the company's own account of how its product measures up to WCAG.

Letter to a tool's company

[Date]

To: [the company behind your online booking]
Subject: Accessibility of [the booking tool] on [your website]

We use [the booking tool] on our website. Federal rules for organizations that receive HHS funding ask our website to meet WCAG 2.1 Level AA, and that includes the parts that come from you. Please send us your accessibility conformance report (a VPAT or ACR) for [the booking tool], and tell us your plans for anything in it that does not yet meet WCAG 2.1 AA.

An evaluation of our pages on [date] found these problems in the part of our pages that your tool provides: [each problem, with its number and title].

Thank you,
[Name], [Practice name]

When we found nothing in a tool's part of the page, the second paragraph says our evaluation didn't test inside the tool and asks only for the company's own report.

6. After the fixes go in

  • Your web person tells us when the changes are live. For 90 days after your report, we recheck the same pages free, as often as you ask. Each updated report comes within 5 business days.
  • If a fix we gave you was wrong, we correct it and recheck it free, any time.
  • Your web person can call us with questions at (586) 217-0032, 8 AM to 6 PM Eastern, seven days a week.
  • We never log in to your website and never need patient information. Your web person makes the changes, after taking a backup.

Get a report and fix pack for your own website

$500, paid once, for every page of your site, up to 50. Your report and fix pack arrive within 5 business days, and we recheck the same pages free for 90 days while your web person works through the fixes.

No one to make these changes? With the $1,500 widget service, which includes the audit, we write the fixes as one file your web person adds with one line of code. The packages side by side

Got an email from us? You can also just reply "yes" to it. Whether the HHS rule covers your practice is a question for your attorney; nothing here is legal advice.