The control is a div.
It looks like a button and does not work from the keyboard.
Access is part of the release.
We design and review interfaces against WCAG 2.2 AA. That is a target, not a certificate we hand you.
Exclusion usually looks like a shortcut.
The error is only red.
Color carries the status, and the text never says what failed.
The scan was the audit.
An automated tool passed, and a person using a screen reader still cannot finish the task.
What a review covers.
Structure.
Landmarks, headings, names, and focus order.
Operation.
Keyboard paths, visible focus, touch size, and errors tied to fields.
Proof.
Automated checks plus a manual pass. A score from a tool is not the result.
How we review.
Pick the journey.
One task a customer must finish. Not every pixel.
Use the interface without the mouse.
Keyboard first. Then a screen reader on the same path.
Fix the cause.
A component repaired once is worth more than a list of page-level patches.
Limits.
No certificate.
WCAG 2.2 AA is the bar we design toward. We do not certify a product as compliant.
This website is not the case study.
Our own pages are built to that target. That is not a claim that an external audit has signed them off.
Questions we expect.
Is an automated scan enough?
No. It catches a class of failures. Keyboard and screen reader passes catch others.
Do you overlay a widget?
No. Access is in the markup and the interaction, not a panel added at the end.
Bring the constraint, not a tool list.
We will say what is in scope, what is not, and what would count as proof.