Accessibility Remediation

Accessibility issues rarely sit in one place. Some can be resolved through content changes. Others require design updates or development work. In many cases, the same underlying problem appears across several pages because it comes from a shared template or component.

Remediation work can include:

• improving colour contrast
• correcting heading structures
• improving keyboard navigation
• updating focus states
• fixing form labels and validation
• improving link and button text
• adding or correcting image alternatives
• improving navigation and menus
• resolving screen reader issues
• improving tables and structured content
• updating interactive components
• improving responsive and zoom behaviour
• addressing multimedia accessibility
• correcting markup and semantic structure

We review each issue in context so the fix improves the experience without creating new usability or technical problems elsewhere.

Where the issue affects a reusable component, we generally prefer to fix the component itself rather than patching individual pages.

Not every issue needs to be addressed in the same order. A barrier that prevents someone from completing a key task deserves more attention than a minor issue on a low-priority page. Site-wide problems may also warrant early attention because one change can improve accessibility across many parts of the experience.

We help teams prioritise work based on factors such as:

• severity of the issue
• frequency across the site
• importance of the affected journey
• number of users likely to be impacted
• technical complexity
• whether the issue affects a shared component
• dependencies on other design or development work

This is particularly useful for larger platforms where remediation may need to happen progressively.

The output can be structured into an implementation backlog, with clear recommendations for content, design and development teams.

Where accessibility targets are tied to WCAG, remediation can be mapped against the relevant success criteria. This gives teams a clearer way to track progress and understand which issues affect compliance.

The work may involve:

• addressing failures identified through automated testing
• resolving issues found through manual review
• retesting keyboard behaviour
• reviewing screen reader output
• checking zoom and responsive behaviour
• validating form interactions
• confirming improvements to shared components
• reviewing new content or templates introduced during remediation

Automated tools can support this process, but they cannot confirm every accessibility requirement. Manual testing remains important, particularly for interaction, structure and context.

For more complex experiences, remediation may also be followed by another round of review or targeted user testing to confirm that key journeys are working as intended.

Accessibility remediation should also look at why problems appeared in the first place. If the same issues are likely to return whenever new content, pages or features are added, fixing the current site only solves part of the problem.

We can help teams identify where accessibility needs to be built into ongoing processes, including:

• content publishing
• user interface design
• component development
• quality assurance
• design reviews
• development standards
• CMS configuration
• staff guidance
• future website enhancements

For organisations using a design system, accessibility improvements can also be incorporated into shared components so new experiences inherit better patterns by default.

This gives internal teams clearer standards to work from and makes accessibility easier to maintain as the website or platform continues to evolve.