Accessibility & WCAG

Accessibility assessment and remediation for websites, forms and essential user journeys.

Let’s discuss your project

THE CHALLENGE

Access.
For more people.

Low contrast, unclear fields and keyboard barriers exclude users. Automated tools can only identify part of the accessibility picture.

WHAT IS INCLUDED

A clear scope.
A clear handover.

We combine automated checks with manual reviews across representative pages and interface states. We remediate code and content, document findings and verify the agreed fixes.

  • WCAG 2.2 AA-oriented audits
  • Keyboard & focus testing
  • Screen reader checks
  • Forms, errors & modal remediation
  • Contrast, reflow & motion reviews
  • Accessible component guidance

FROM PLAN TO PRACTICE

The right decisions.
At every stage.

Assess real tasks and interface states

We define a representative sample of templates and essential functions, including navigation, search, forms, dialogs and purchasing where applicable. Assessment covers errors, success messages and loading states as well as the initial screen. Automated findings are combined with keyboard interaction, enlargement and selected screen-reader checks. Scope and conditions are documented so conclusions remain specific and verifiable, rather than implying that one successful scan covers every experience.

Fix the source of the barrier

Remediation addresses semantic structure, accessible names, visible focus and a logical interaction sequence. Fields are connected to instructions and understandable error messages, while dialogs manage initial focus and its return correctly. Contrast, narrow-screen reflow and reduced-motion preferences are reviewed together. Shared-component improvements are preferred where they can also protect future pages, helping the development team maintain accessibility through normal implementation patterns.

Keep accessibility part of ongoing publishing

Handover includes findings, priorities, recommended fixes and retest status. Editors receive guidance on headings, image descriptions, links and media. New components and significant changes need further review because accessibility evolves with the website. Work can support WCAG 2.2 AA objectives within the agreed scope, but an automated score is not a certification, and a scoped technical review does not replace a complete assessment or advice on applicable legal obligations.

HOW WE CHECK THE RESULT

Working is the start.
It has to work for you.

Findings identify the page, reproduction steps, user impact and recommended fix. Agreed remediation is retested with keyboard input, a representative screen reader, magnification and relevant automated tools. Forms, errors, focus and content reflow are reviewed within the agreed journeys. Results describe the documented sample and test conditions, not a general legal certification.

TECHNOLOGY IN CONTEXT

Semantic HTMLARIAaxe-coreScreen readersWCAG 2.2

FREQUENT QUESTIONS

Answers.
Clear from the start.

What working together involves, and what you need to know before we begin.

Does a good automated score mean full compliance?

No. Manual testing, content review and an explicitly defined assessment scope are necessary. An automated result is not a certification of the complete platform.

Must the whole website be rebuilt?

Not always. We assess severity and reach, then recommend targeted fixes or shared component changes that can improve many pages at once.

Does the assessment cover every page, PDF and external website tool?

Only the agreed scope. We define a sample covering essential templates and complete critical processes, with PDFs and third-party tools explicitly identified. Access restrictions and exclusions are documented. New content or external changes may require additional checks rather than inheriting an earlier assessment result.

How are cost and timeline determined?

Scope, the state of your existing platform, dependencies and required checks. Before work begins, a specific proposal records deliverables, prerequisites and approval stages. Software licences, third-party charges and recurring services are separated so you understand what the engagement includes and what affects a later change.

What support will we have after handover?

We hand over the documentation and instructions included in the agreed scope. Responsibilities for daily operation, issue reporting and future requirements are defined. Ongoing support, updates and monitoring have an explicit, separately agreed scope rather than relying on an assumption that someone will take care of them.