top of page

Accessibility Regression Testing: How Routine Website Updates Can Create Hidden Barriers

Writer: Anna Williams
Anna Williams
6 days ago
5 min read

Why website redesigns can unintentionally break keyboard navigation, screen-reader support and essential user journeys. 

 

Accessibility Regression Testing

A website update can improve its appearance, introduce new features and make navigation more convenient. But what happens when the same update makes the website harder for certain users to access? 


A redesigned menu might no longer work with keyboard navigation. A form might display an error without communicating it to a screen reader. A previously visible focus indicator might disappear after a CSS update. 


The website continues functioning, but some users can no longer complete basic tasks. 


This highlights an important issue in software development: an update that improves functionality does not necessarily preserve accessibility. 


This is known as an accessibility regression, and it is a problem that development teams should address through structured testing. 


The Difference Between Functional Testing and Accessibility Testing 


Functional testing checks whether an application performs its intended tasks. 


For example, a website may successfully allow users to register, submit forms, navigate between pages and complete transactions. 


Accessibility testing evaluates whether users with different abilities can perform those same tasks. 


These are separate testing requirements. 


Consider a registration form that successfully creates an account. A functional test may pass because the submission process works correctly. 


However, an accessibility review may identify that: 

  • The input fields do not have properly associated labels. 

  • Keyboard users cannot reach the Submit button. 

  • Error messages are not communicated to assistive technologies. 

  • The visual focus indicator is missing. 


The feature works technically, but the experience remains inaccessible to certain users. 


This is why accessibility should be included in software quality assurance rather than treated as a final design adjustment. 


Where Accessibility Regressions Commonly Occur 


Accessibility problems can emerge from relatively small interface modifications. 


1. Navigation Components 


Custom dropdowns and interactive menus may lose keyboard functionality when developers modify their behaviour without preserving appropriate focus management and keyboard interaction. 


2. Forms and Validation 


Changes to form layouts can break label associations, instructions and error-message communication. Users may struggle to understand which information is required or how to correct an error. 


3. Visual Design Changes 


Updated colours, typography and interface elements can introduce contrast problems or remove visible focus indicators. 


4. Interactive Elements 


Custom buttons, pop-ups and expandable components may become difficult to operate when their accessible names, roles, states or keyboard behaviour are not properly implemented. 


These issues can remain unnoticed when testing focuses primarily on visual appearance and mouse-based interaction. 


Consider a Practical Example 


Imagine a business website with a navigation menu used across several pages. 

Initially, users can access the menu using a mouse or keyboard. 


The development team introduces a redesigned dropdown menu to improve the website's appearance. 


After implementation, the menu works correctly when clicked with a mouse. However, keyboard users cannot move through all the available options. 


Because the component is shared across the website, the same problem affects multiple pages. 


The development team may not identify the issue through conventional functional testing because the menu appears to work normally during a mouse-based review. 


This illustrates why testing should examine not only the updated component but also how the change affects existing user interactions. 


What Should Organizations Check After a Website Update? 


The Web Content Accessibility Guidelines (WCAG) 2.2 provide a recognised framework for evaluating website accessibility. 


Development teams should pay particular attention to the following requirements when reviewing interface changes. 


1. Keyboard Accessibility 


WCAG 2.2 Success Criterion 2.1.1 (Level A) requires functionality to be operable through a keyboard interface. 


Check whether users can navigate menus, operate buttons and complete important website tasks without a mouse. 


2. Focus Visibility 


Success Criterion 2.4.7 (Level AA) requires keyboard focus indicators to be visible. 


Check whether users can identify the currently selected interface element. 


3. Focus Not Obscured 


Success Criterion 2.4.11 (Level AA) requires a focused interface component not to be entirely hidden by content created by the website. 


Pay attention to sticky headers, footers, pop-ups and other overlapping elements. 


4. Colour and Contrast 


Success Criterion 1.4.1 (Level A) states that colour should not be the only means of communicating information. 


Success Criterion 1.4.3 (Level AA) specifies minimum contrast requirements for text and images of text. 


Check whether important information remains understandable and readable after visual changes. 


5. Form Labels and Instructions 


Success Criterion 3.3.2 (Level A) requires labels or instructions when content requires user input. 


Review whether form fields, instructions and validation messages remain understandable and properly associated with their respective controls. 


These are selected WCAG requirements relevant to common website updates, not a complete accessibility compliance checklist. 


A Practical Accessibility Testing Scorecard 

 

Practical Accessibility Testing Scorecard 

Organizations can use the following framework to assess whether website updates preserve important accessibility requirements. 

Testing area 

What it reveals 

Question to ask 

Keyboard navigation 

Accessibility without a mouse 

Can users complete essential tasks using a keyboard? 

Focus visibility 

Visibility of selected elements 

Can users identify their current position? 

Form accessibility 

Labels and error communication 

Can users understand and correct form errors? 

Colour and contrast 

Visual information accessibility 

Is information understandable without relying on colour alone? 

Screen reader compatibility 

Assistive technology interaction 

Are important elements and instructions communicated correctly? 

Regression coverage 

Impact of new updates 

Have previously tested interactions been checked again? 

The objective is not to generate more testing reports. It is to identify barriers that could prevent users from completing important activities. 


Turning Accessibility Findings Into Release Controls 


Identifying accessibility issues is only the first step. Organizations need a repeatable process for preventing them from appearing in future releases. 


A practical approach includes five steps: 


Define Accessibility Requirements 


Establish the relevant WCAG criteria during the design and development stages. Include accessibility expectations when creating reusable interface components.

 

Combine Automated and Manual Testing 


Automated tools can identify certain issues, but they cannot determine accessibility on their own. Manual checks are still necessary to evaluate keyboard behaviour, screen-reader output and complete user journeys. 



Test Relevant Browser and Assistive Technology Combinations 


Test representative combinations based on the environments supported by the application. 


For example, teams may evaluate NVDA with Chrome or Firefox on Windows, VoiceOver with Safari on Apple devices, and TalkBack with Chrome on Android. 


Document and Prioritise Defects 


Record the affected component, the accessibility requirement involved, the impact on users and the required correction. Prioritise barriers that prevent users from completing essential tasks. 


Include Accessibility in Release Reviews 


Retest affected components after modifications and verify that resolved issues have not returned before deployment. 


These steps help make accessibility a recurring quality control activity rather than an occasional review. 


Final Thoughts 


Website accessibility is not a one-time development requirement. 


Applications continuously evolve through redesigns, feature additions, software updates and changes to interactive components. 


Without regular evaluation, these changes can unintentionally introduce barriers that affect how users access and interact with digital services. 


Combining automated testing, manual evaluation, assistive technology testing and structured regression checks helps organizations make accessibility part of their software quality process. 


Ultimately, the objective is not simply to release an improved website. It is to ensure that improvements do not come at the expense of users who depend on accessible digital experiences. 


The NewVision Advantage: Supporting Reliable Technology Operations 

 

Supporting Reliable Technology Operations 

Effective IT management requires more than maintaining systems after problems occur. It also involves regular maintenance, proactive issue resolution and technology practices that support business continuity. 


NewVision Management Solutions offers IT Support & Maintenance, cybersecurity, proactive issue resolution, regular updates and patching, cloud solutions and IT consulting. 


These services support businesses in maintaining their technology environments and managing changing operational requirements. 


For organizations reviewing their digital accessibility practices, a useful starting point is to include accessibility requirements in website change reviews, define testing responsibilities and evaluate whether important user journeys remain accessible after updates. 


Accessibility-specific evaluations should be conducted against the applicable standards using appropriate technical and human testing methods. 

 

NewVision Management Solutions 


 
 
 

Comments


bottom of page