A real report, not a sanitised one
Most suppliers show a sample with the failures taken out, which tells you nothing about whether they would find yours. This is the evaluation we ran on our own product, published as it came out — and then the re-test after we fixed what it found.
What it found
The product is CertMyTranslation, our own certified translation service. Ten templates, all fifty WCAG 2.1 Level A and AA criteria.
| Conformance level | Before | After |
|---|---|---|
| Supports | 23 | 30 |
| Partially Supports | 9 | 7 |
| Does Not Support | 5 | 0 |
| Not Applicable | 13 | 13 |
The one that mattered
The file upload control — the only way to place an order — was hidden with
display:none and the clickable container around it could not take focus. Eighty
consecutive Tab presses never reached it.
Nobody using a keyboard, a screen reader or a switch device could buy anything from us. We had shipped that and not noticed. It took twenty lines to fix.
Read the report — before remediation
Read the report — after remediation
Read the second one carefully
The re-test still shows seven criteria at Partially Supports, and they are named
rather than quietly dropped: three were outside the scope of that day’s fixes, three cannot be
exercised without completing a live payment, and one covers foreign-language phrases carrying no
lang attribute.
That is what a real report looks like after remediation. If a supplier shows you an after-report with a clean sheet, ask what they stopped counting.
Every difference between the two documents corresponds to something that was actually changed that day. We checked that line by line before publishing, because two reports on one product that disagree for unexplained reasons would be worse than publishing neither.
- What a report like this costsPublished prices, and what the rest of the market charges.
- Start one for your productSend the URL and the deadline you are working to.