Every user / accessible route

An accessibility audit and remediation proposal for an online application that disabled users cannot finish. It covers the failures found, how the audit, fixes, retests and user testing work, what is tested, a nine-week timeline, a similar client’s results and three one-time options.

Accessibility Audit and Remediation Proposal

Overview

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.2cqw,44px)">Thank you for sending the complaint</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">You want every applicant to be able to finish your online application, whatever they use to read it.</p>

<p>Hello {{CLIENT_NAME}},</p>
<p>Thank you for sharing the complaint and your scan results. An applicant who uses a screen reader could not finish your online application last month, and your partner universities now ask for WCAG 2.2 AA by September.</p>
<p>We tested the application ourselves with a keyboard, a screen reader and the page zoomed to 200%. Of its seven steps, a screen reader user can finish three. We recommend an audit of the application and the pages that lead to it, fixing the problems with your developers, and testing with disabled users before your next intake opens.</p>
<p><strong>{{SELLER_NAME}}</strong><br>Accessibility lead, {{SELLER_COMPANY}}</p>

Introduction

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.2cqw,44px)">What we found in a first check</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">A morning of manual testing on the seven application steps, plus your automated scans.</p>

Each one stops an applicant from finishing

Critical and serious failures by type

What we found

<h2 style="font-family:var(--proposal-font-accent);font-weight:500;line-height:1.14"><span style="font-size:clamp(30px,4.2cqw,52px)">We recommend fixing the 14 critical failures first, because each one stops an applicant.</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">Then the serious failures, form by form, so every release makes the application easier to complete.</p>

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.2cqw,44px)">How we work</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">Four steps, with your developers involved from the start.</p>

<p>We test 24 pages and 6 forms with a keyboard, two screen readers, zoom and automated scans, against WCAG 2.2 AA.</p>

Audit

<p>We fix the code with your developers, or write tickets they can work from, each with the exact change.</p>

<p>Every fix is retested by hand, because automated scans miss many problems.</p>

Retest

<p>Three people who use assistive technology complete the application, and we fix what they find.</p>

Test with users

Our recommendation

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.2cqw,44px)">What is included</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">Everything in the recommended option, Audit and fixes.</p>

<ul><li>24 pages, from the course list to the confirmation page</li><li>The 6 application forms, including document upload and payment</li><li>Confirmation emails and the applicant portal login</li></ul>

Pages and forms

<ul><li>Keyboard only, in Chrome and Safari</li><li>NVDA on Windows and VoiceOver on iPhone</li><li>Zoom to 200% and 400%, and high contrast mode</li></ul>

Assistive technology

<ul><li>A findings log: each failure, where it is, why it matters and how to fix it</li><li>A retest report after the fixes</li><li>An accessibility statement for your website</li></ul>

Reports

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.2cqw,44px)">Nine weeks from kickoff</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">Work starts on {{START_DATE}}.</p>

<p>Manual and automated testing of every page and form.</p>

<p>The 14 critical failures fixed and retested.</p>

Critical fixes

<p>The serious failures fixed, one form at a time.</p>

Serious fixes

<p>Three sessions with assistive technology users and a full retest.</p>

User testing and retest

<p><strong>Not included:</strong> the rest of your website beyond the 24 pages, your student records system, and legal advice. We can audit other sites afterwards.</p>

What is included

Who you will work with

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.2cqw,44px)">Results for a similar client</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">A credit union’s loan application, nine weeks after the audit.</p>

Results for a similar client

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.2cqw,44px)">Options and fees</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">Three options. We recommend Audit and fixes.</p>

Find every barrier; your developers fix them.

Audit and fixes

Plus six months of checks so new pages stay accessible.

Audit, fixes and checks

<p>Fees are in USD and exclude tax. User testing participants are paid by us. This proposal is valid until {{VALID_UNTIL}}.</p>

Options and fees

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.2cqw,44px)">Common questions</span></h2>

<p>That is the target. The retest report lists every criterion as met or not met, so you can see exactly where you stand.</p>

Will the application meet WCAG 2.2 AA?

<p>In Audit and fixes we make them in your code, with your developers reviewing. In Audit, your team works from our tickets.</p>

Do our developers have to make the fixes?

<p>People who use assistive technology every day find problems that tools and auditors miss. Three sessions show what matters most to applicants.</p>

Why test with real users?

<p>Very little. Some colours get darker for contrast, and error messages move next to their fields. We show you each change first.</p>

Will the design change?

<p>The findings log includes patterns your team can reuse. The third option adds checks before each release.</p>

What about pages we add later?

<p>A test copy of the application, a developer for code reviews, and the complaint details so we test that path first.</p>

What do you need from us?

Questions

<p style="font-size:18px;letter-spacing:.08em;text-transform:uppercase">{{SELLER_COMPANY}}</p>

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.2cqw,44px)">Next steps</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">How we start.</p>

Accessibility Audit and Remediation Proposal - Preview