Key journeys
We select navigation, contact and other user tasks, including errors, open menus and messages.
A website should work for different people.
We assess agreed pages and journeys, combining tool checks with manual evaluation of keyboard use, forms and readability.
Let’s talk about your projectAn example of our method
Try the keyboard
Label. Order. Visible focus.
Errors need words too
Example: “Enter an address in the format name@company.com.” A red outline alone does not explain the fix.
What the work covers
Being able to read a website and complete a task is part of its quality. The audit begins with representative pages, states and agreed assessment criteria.
Manual and tool evaluation
We check keyboard use, visible focus, labels, contrast and zoom. Assistive technology coverage is agreed before testing.
Reproducible findings
We describe the location, impact, reproduction steps and recommendation. A follow-up review can be agreed after fixes.
Method reference: W3C WAI
Where we start
Page URLs, important workflows and a test account if needed. We do not use real customer data.
Let’s talk about your projectBefore we begin
Is a scanner enough for an audit?
No. Tools identify some issues, but human evaluation is also needed.
Is the report a compliance certificate?
No. It describes the assessed scope and findings. Whole-site conformance evaluation requires an explicitly agreed separate scope.