Expertise

Accessibility and usability, built in from the start.

Audits, design guidance and build support aimed at WCAG 2.2 AA, so more people can use what you make.

Start the conversation How we work

01 / The problem

Problems we address

Barriers you cannot see

Interfaces that look fine can still fail with a keyboard, a screen reader, zoom or a small screen.

Requests for evidence

Customers, partners or procurement teams may ask you to show how accessible your product is.

Reports nobody can act on

Audit results full of jargon and no priorities are easy to file and forget.

Forms and flows that lose people

Unclear labels, confusing errors and heavy interactions send people away before they finish.

02 / Audience

Who this is for

  • Product teams who want accessibility built into design and development.
  • Organisations with public-facing sites or services.
  • Designers and developers who want practical, specific guidance.
  • Teams whose customers or partners ask about accessibility.

03 / Engagement

How we engage

We can run a single audit, review designs before they are built, or support a team over time.

  1. 01

    Scope

    Choose the pages, flows and standard to assess, so the work is specific and affordable.

  2. 02

    Evaluate

    Automated scanning, manual keyboard testing and screen-reader checks, plus design and content review.

  3. 03

    Report

    Findings in plain language, mapped to WCAG, ranked by how much they affect people.

  4. 04

    Support fixes

    Guidance and code examples for your team, or fixes made by us, followed by a retest.

04 / Benefits

What changes

Clear priorities

You know which problems matter most, and why, so effort goes where it helps people.

Fewer late surprises

Issues found in design and early builds cost far less to fix than issues found after launch.

A shared standard

Designers, developers and content authors work from the same understanding of what good looks like.

05 / Deliverables

What you receive

The final list is agreed for your project.

  • Audit scope and method.
  • Findings report with severity, affected users and WCAG references.
  • Fix guidance with code and design examples.
  • Annotated designs for accessibility.
  • Retest summary after fixes.
  • Short guidance for your team on keeping standards up.

06 / Questions

Common questions

Will you certify our site as WCAG compliant?

No. We do not issue certifications. An audit is an assessment at a point in time. A statement that a site conforms to WCAG should be made by its owner, ideally backed by independent testing and evidence.

What is the difference between accessibility and usability?

Accessibility is about whether people with different abilities and tools can use something at all. Usability is about how easily and pleasantly anyone can complete their task. They overlap, and we treat them together.

Do automated tools find everything?

No. Automated checks find only a portion of issues. Manual keyboard and screen-reader testing, and human judgement about content, are needed for the rest.

Do you test with disabled users?

Testing with people who use assistive technology gives the strongest evidence. It can be added as a separate scope, and our own checks are not a substitute for it.

Which standard do you work to?

WCAG 2.2 at level AA is our default target. We can work to other requirements if you need them, and we will tell you where we are less certain.

Related

Keep exploring

Have a project in mind?

Send a few details about what you are building through the enquiry form.

Start a project