UX and UI design
Accessible component patterns, focus states, contrast, error messages and simpler journeys.
Services / Remediation
From report to repair.
We help turn audit results into working solutions: we design UX fixes, support the front-end, tidy up content and documents, and verify the outcome with a retest.
Accessibility goal
Areas of support
We fix things where the barrier begins.
Every barrier from the report goes to the right area — from interface design to a PDF document.
Front-end
Semantic HTML, ARIA, keyboard support and focus management in your stack.
Content and editing
Headings, links, text alternatives, plain language and guidelines for CMS editors.
PDF documents
Tagging, reading order, metadata and accessible alternative versions of documents.
How we work
You implement, or we do it for you.
Choose the model that fits your team's resources. Both end with a retest and sign-off.
We support your team
We hand over the backlog, advise on solutions and review changes. The know-how stays in your organisation.
We implement the fixes
We deliver changes within the agreed scope, in your repository and release process.
Process
Step by step to sign-off.
We consider a task closed only when a retest confirms the fix.
Barrier analysis
We group problems by component and root cause, so one fix removes many occurrences.
Plan and priorities
We set the order of work based on severity, user impact and your release plan.
Fix design
We prepare UX solutions, component patterns and guidelines for editors.
Implementation and review
Your team or we make the changes; we review each one for accessibility.
Retest
We check the fixes on the specified version of the service, in agreed browsers and assistive technologies.
Sign-off
We summarise what was fixed, what needs further work and what was out of scope.
Retest and verification
A fix is done when it passes the retest.
Merging a pull request is not enough. A retest names specific barriers, the service version, the date, testers and browsers, and each outcome gets one of the statuses below.
Fixed
The barrier has been removed — confirmed by testing.
Still failing
The problem was not removed or the fix does not work.
Partially fixed
Improvement is visible, but some occurrences remain.
Untestable
No access or environment to run the test.
Regression
The change caused a new problem — we record it as a separate barrier.
Out of scope
The item was not included in this retest round.
FAQ / Remediation
Questions about remediation.
Only if we implement the fixes ourselves. We work with agreed permissions and without access to production secrets. We can also support your team with consultations and code review.
Let's turn the report into fixes.
Tell us where your team is today and we will propose a support model.