We’ve introduced automated accessibility testing for ASP Frontend components.

Accessibility is not an “extra” for us. It is part of providing a reliable, respectful service to the public which includes people who use assistive technologies, have different access needs, or are working in challenging situations.

As the Frontend library grows, we need a dependable way to spot regressions early. Automated accessibility testing gives us a consistent safety net that helps us identify issues before they reach production.

Why we’ve done this

When we make changes to components (markup, behaviour, or styling), it is easy for small changes to have unexpected impacts. Automated checks help us to:

• Protect users by catching common accessibility issues early.
• Keep experiences consistent across products and sites that use the library.
• Support faster delivery by providing confidence during change.
• Build accessibility in as part of everyday development, not as a last-minute check.

What this means for users

This change helps us maintain components that are easier to use with:

• screen readers
• keyboard-only navigation
• zoom and reflow
• a range of devices and browsers

Automated testing cannot guarantee accessibility on its own, but it helps ensure we are continually checking the basics as the system evolves.

Our commitment

We will continue to:

• design and build with accessibility as a core part of how we work
• test changes during development (automated and manual)
• respond to findings and improve patterns over time

Automated accessibility testing helps us be more consistent and more confident as we improve and expand ASP Frontend. It strengthens our day-to-day practice, supports better outcomes for users, and reinforces our ongoing commitment to building services that people can use, whatever their needs or circumstances.