Day 1: Pin down exactly what they asked for
Before anyone opens a template, reply to the buyer and confirm three things:
- Which standard. WCAG 2.1 or 2.2, Section 508, or EN 301 549. If they just say “a VPAT,” ask whether WCAG 2.1 AA or 2.2 AA is acceptable. Most software buyers will say yes to either. (Not sure which? See WCAG 2.2 vs. 2.1.)
- Which product and version. If you sell several modules, agree on what’s in scope: the web app, the mobile apps, the admin console, the help center.
- Whether self-reported is acceptable. Some buyers require third-party testing. Find out now, not after you send.
It’s also fine to tell them when to expect it. “We’ll have an updated ACR to you by Friday” buys goodwill and sets a deadline your team will respect.
Day 2: Find the people who know the product
The answers are already in your team’s heads. You need about an hour each from two or three people: a front-end engineer, a designer, and whoever owns QA. Ask them where they know the product falls short. They usually know about the unlabeled icon buttons, the chart with no text alternative, and the date picker that doesn’t work with a keyboard.
Write down everything they say in plain language. Those notes become your remarks.
Day 3: Check the product, criterion by criterion
Go through each WCAG success criterion and decide what you can honestly say. You don’t need a full audit to write a credible report, but you should actually try the product. A few checks catch most issues:
- Keyboard only. Unplug the mouse and complete your main workflow with Tab, Shift+Tab, Enter, Space and the arrow keys. Can you see where focus is at all times? Can you get out of every dialog?
- Screen reader. Try the same workflow with VoiceOver (Mac and iOS), NVDA (Windows) or TalkBack (Android). Are buttons and form fields announced with sensible names?
- Zoom and reflow. Zoom the browser to 200% and then 400%. Does anything get cut off or require scrolling in two directions?
- Contrast. Check text and key controls with any contrast checker. Light gray placeholder text is a common miss.
- Automated scan. A free browser extension will flag missing labels and contrast problems. Treat it as a starting point; automated tools catch only part of what WCAG covers.
Our plain-language WCAG 2.2 checklist turns every criterion into a question your team can answer.
Day 4: Write the report
Fill in each row with a conformance level and a remark. Be specific about what doesn’t work and where, and leave out promises you can’t keep. If you haven’t checked something, don’t guess: mark it clearly as not yet evaluated and come back to it.
The details matter here: how to fill out a VPAT, row by row and how to choose conformance levels.
VPAT Draft Desk walks you through every criterion with a plain-language question, then sets your answers into a finished PDF and Word report.
Start your VPATDay 5: Review and send
- Have one person read every remark from a buyer’s point of view. Is anything vague, defensive or overstated?
- Check the product name, version and report date on the cover.
- Make sure the contact email works and someone is watching it.
- Send the PDF. Keep the editable copy for the next release.
After the deal
Put the report on a calendar. Update it when a release changes the interface, and at least once a year. Your partial and unsupported rows are also a ready-made accessibility backlog for your engineering team, and a good brief for an independent audit when you’re ready for one.