Why Fixing HTML Accessibility Issues at the Source Matters

In today’s digital age, web accessibility has emerged as a crucial element for ensuring that individuals of all abilities can engage with online content seamlessly. With the internet playing an integral role in everything from education and employment to shopping and socializing, businesses must design their websites to be accessible to all. Unfortunately, many companies rely on third-party accessibility overlay tools like UserWay, AccessiBe, and Level Access to address accessibility issues, believing these tools can offer a quick fix.

While these tools can provide some immediate relief, they often fail to address the root cause of accessibility problems and can create additional challenges for users. Fixing accessibility issues directly within the website’s HTML code is essential to ensure a truly inclusive experience. This approach not only helps users with disabilities but also improves overall user experience, site performance, and search engine optimization (SEO).

Understanding Web Accessibility: Why It’s Critical

Web accessibility refers to the practice of designing websites and digital content so that people with disabilities can perceive, understand, navigate, and interact with them. Disabilities can affect how individuals engage with websites in a wide range of ways, including:

• Visual impairments: This includes blindness, low vision, and color blindness.
• Auditory impairments: Users with hearing impairments may require text alternatives to audio content.
• Physical disabilities: Conditions such as cerebral palsy or muscular dystrophy can make using a standard mouse or keyboard difficult.
• Cognitive disabilities: Conditions like dyslexia, autism, or ADHD can make navigating complex websites more challenging.

According to the World Health Organization, around 15% of the global population has some form of disability, which underscores the importance of web accessibility. In many countries, accessibility is not just a best practice but a legal requirement. In the United States, for example, websites must comply with the Americans with Disabilities Act (ADA) and the Web Content Accessibility Guidelines (WCAG). Failing to meet these standards can result in lawsuits, reputational damage, and exclusion of a significant portion of the population from digital services.

Legal Requirements and Consequences

In recent years, there has been an increase in lawsuits against businesses with inaccessible websites. Under the ADA, companies can face substantial fines and be required to pay damages if their websites do not accommodate individuals with disabilities.

WCAG is the globally recognized standard for web accessibility, and businesses are expected to align their websites with its guidelines to avoid legal risks. WCAG sets out specific success criteria in areas such as perceivability, operability, understandability, and robustness, which businesses must follow to ensure that their sites are accessible to all users.

Beyond legal consequences, non-compliance with accessibility guidelines can also lead to poor user experiences for a considerable segment of the population, damaging brand reputation and limiting market reach.

The Pitfalls of Accessibility Overlay Tools

Third-party accessibility tools, often referred to as “overlay” tools, are frequently marketed as easy solutions to fix accessibility problems. These tools work by injecting scripts into web pages that adjust certain aspects of the site in real-time to address issues like color contrast, alternative text for images, and keyboard navigation. Popular tools like UserWay, AccessiBe, and Level Access are widely used by companies that want to achieve quick compliance with accessibility standards.

However, overlays come with significant limitations. They provide only surface-level fixes, failing to address the deeper structural problems in the website’s code. As a result, accessibility issues can resurface or worsen over time. Additionally, these tools may interfere with assistive technologies like screen readers, creating confusing or redundant experiences for users.

Accessiblü Blog: Dangers of Overlays Separating Fact from Fiction

Case Study: San Antonio Spurs News Webpage and UserWay

An analysis of AirAlamo.com a website dedicated to the San Antonio Spurs which relies on UserWay, revealed significant accessibility shortcomings. Rick Flores, Lead Auditor at Accessiblü, tested the site using the JAWS screen reader and encountered several issues illustrating the limitations of overlay tools.

The article titles were poorly labeled, making it difficult for JAWS to read the content correctly. Instead of reading the article names, the screen reader announced generic information like “Air Alamo.” While Rick could access accompanying data such as author names and timestamps, the overall navigation experience remained cumbersome.

Rick further noted that the UserWay tool did not fix these labeling issues. The overlay did not correct the underlying HTML coding problems, meaning the same accessibility barriers persisted even after the tool was activated. This highlights a major flaw in relying on overlays—they do not resolve the root issues within the code itself, which is necessary for creating a truly accessible experience.

Additionally, many of the features offered by UserWay, such as color contrast adjustments and text resizing, can already be handled natively through Windows’ built-in accessibility settings. The UserWay screen reader was especially problematic—it acted more like a basic text-to-speech tool rather than a full-fledged screen reader, limiting interaction with the site’s content.

Fixing Accessibility at the Source

The key problem with overlays like UserWay is that they do not address the root causes of accessibility issues. These tools provide superficial fixes by dynamically altering the website’s front-end display without improving the underlying structure. Fixing accessibility issues at the source—within the website’s HTML code—ensures that content is accessible regardless of whether an overlay is applied.

Fixing accessibility at the source involves:

• Proper Labeling: Ensuring that article titles and headings are correctly tagged with ARIA attributes or semantic HTML so that screen readers like JAWS can navigate and relay information accurately.
• Semantic HTML: Using proper HTML elements for headings, lists, and navigation ensures that screen readers can present content logically, improving the overall experience for users with disabilities.
• Keyboard Navigation: Building keyboard navigation directly into the code allows users to navigate the site efficiently without needing overlays or widgets.

By addressing these issues at the source, websites can avoid the delays, conflicts, and limitations that overlay tools often introduce.

Key Findings from the Case Study

• Labeling Issues: Article titles on the site were poorly labeled for screen readers, and these issues persisted despite the activation of the UserWay overlay.
• Redundant Features: Many accessibility features provided by UserWay, such as text resizing and contrast adjustments, could be handled natively by Windows’ built-in features.
• Screen Reader Deficiency: The UserWay screen reader was a basic text-to-speech tool that did not allow the same level of interaction with page content as more sophisticated screen readers like JAWS.
• Code-Level Fixes Are Essential: The accessibility issues Rick encountered could not be fully addressed by UserWay. Fixing the HTML code directly would ensure a better experience for users relying on assistive technologies.

The Long-Term Benefits of Fixing Accessibility at the Source

Fixing accessibility at the source is not only more effective but also more cost-efficient in the long run. By ensuring that a website’s code adheres to accessibility standards, businesses can eliminate the need for ongoing overlay maintenance and reduce the risk of legal action.

Additionally, accessible websites often rank higher in search engine results, as many SEO best practices align with WCAG guidelines. Properly labeled images, descriptive headings, and faster page load times can all contribute to improved SEO performance, leading to increased organic traffic and higher revenue.

Moreover, a truly accessible website provides a better user experience for everyone, regardless of their abilities. By creating an inclusive experience, companies can reach a broader audience and demonstrate their commitment to social responsibility.

Conclusion: True Accessibility Empowers Users

Web accessibility is about empowering users to interact with digital content in a way that suits their needs. Overlay tools may offer temporary relief, but they often introduce new barriers, particularly for users of assistive technologies like JAWS. The best solution is to fix accessibility issues directly within the website’s code.

When addressing accessibility at the source, businesses ensure compatibility with a wide range of tools, respect user autonomy, and create a more inclusive digital experience. True accessibility means meeting users where they are and allowing them to navigate websites in a way that works best for them—without relying on clunky, temporary fixes.

Shannon Nix is a senior Accessibility Conformance Specialist at Accessiblü