Veridian Health’s 2026 ADA Blind Spot Revealed

When I first started my consulting firm, I believed my mission was to help companies build beautiful, functional digital products. What I quickly learned, however, is that “functional” isn’t truly functional if it excludes a significant portion of your user base. This realization hit me hard when working with a promising Atlanta startup, Veridian Health, whose innovative patient portal was about to launch but was anything but accessible. How could a health-tech platform designed to empower patients inadvertently create barriers for those who needed it most?

Veridian Health’s Blind Spot: A Case Study in Missed Accessibility

Veridian Health, located just off Peachtree Road in Buckhead, was developing a groundbreaking patient management portal. Their vision was admirable: a single platform where patients could schedule appointments, view lab results, communicate with doctors, and manage prescriptions. The initial designs were sleek, the backend robust, and the team, led by CEO Sarah Chen, was passionate. They’d invested millions into development, hiring top-tier talent from Georgia Tech’s computing school.

Their initial user testing, however, was a disaster. Not for the reasons you might expect – the core functionality worked fine for a typical user. The problem arose when they brought in a diverse group for a beta test, including individuals with visual impairments, motor disabilities, and cognitive differences. That’s when the cracks started to show.

I remember Sarah calling me, her voice tinged with panic. “Mark,” she said, “we’ve got a huge problem. Our portal is completely unusable for some of our testers. One woman, who uses a screen reader, couldn’t even log in. Another couldn’t navigate the calendar without a mouse. We’re facing potential lawsuits, and frankly, it’s just not right.”

The Technical Debt of Exclusion

My team and I immediately dove in. What we found was sadly common: an oversight, not malice. The developers had focused on visual appeal and core functionality, unintentionally neglecting the underlying code that makes a platform navigable for assistive technology. For instance, images lacked descriptive alt text, forms had no proper labels, and keyboard navigation was non-existent. The color contrast ratios were abysmal, making text unreadable for users with low vision.

“This isn’t just a ‘nice-to-have’ anymore, Sarah,” I explained during our first strategy session. “The Americans with Disabilities Act (ADA) applies to digital spaces, and courts are increasingly ruling that websites and applications must be accessible. Beyond legal compliance, you’re alienating a massive market segment. According to the CDC, 1 in 4 adults in the US has some type of disability. That’s a quarter of your potential users.”

This is where I often see companies stumble. They view accessibility as an add-on, a feature to be bolted on later, rather than an integral part of the design and development lifecycle. It’s like building a house and then trying to add a ramp and wider doorways after the concrete has cured – far more expensive and less effective than planning for it from the start.

Rebuilding with Intent: A Phased Approach to Inclusive Design

Our first step with Veridian was a comprehensive accessibility audit. We used a combination of automated tools and manual testing. Automated tools like WebAIM’s WAVE Evaluation Tool and Deque’s axe DevTools are fantastic for catching about 30-40% of common issues quickly. They can flag missing alt text, poor contrast, and structural errors. However, they’re only a starting point.

“You can’t automate empathy,” I often tell my clients. For the remaining 60-70% of issues, you need human testers. We brought in a team of accessibility specialists, some of whom had disabilities themselves, to navigate the portal using screen readers like NVDA (NonVisual Desktop Access) and JAWS, switch devices, and speech-to-text software. This manual testing phase was eye-opening for the Veridian team. They saw firsthand how their design choices created roadblocks.

Expert Insight: The Power of Semantic HTML and ARIA

One of the biggest hurdles for Veridian was their reliance on non-semantic HTML and custom JavaScript components without proper WAI-ARIA (Web Accessibility Initiative – Accessible Rich Internet Applications) attributes. Semantic HTML gives meaning to content; a `` element inherently tells assistive technologies it’s an interactive control, whereas a `

` styled to look like a button does not.

“Look, team,” I explained during a developer workshop at Veridian’s office in Midtown Atlanta, “your `

` elements might look like buttons, but to a screen reader, they’re just generic containers. We need to use native HTML elements wherever possible. When that’s not feasible, we use ARIA roles, states, and properties to provide that crucial semantic information.” For example, adding `role=”button”` and `aria-label=”Submit Form”` to a custom `

` can transform it into an accessible interactive element. This was a non-negotiable for us.

We also focused heavily on keyboard navigation. Many users with motor disabilities or visual impairments rely solely on a keyboard to interact with websites. Ensuring that all interactive elements are reachable and operable via the Tab key, and that focus indicators are clear, is fundamental. Veridian’s initial portal often trapped keyboard users in modal windows or skipped crucial navigation links entirely.

Implementing Change: A Culture Shift and Continuous Improvement

The technical fixes were just one part of the equation. We needed to instill a culture of accessibility within Veridian. This meant:

1. Developer Training: We ran a series of workshops for their engineering team, focusing on WCAG 2.2 Level AA guidelines. This isn’t just about passing automated tests; it’s about understanding the “why” behind each guideline.
2. Designer Empowerment: Their UI/UX designers learned about color contrast ratios, clear typography, intuitive focus order, and designing accessible forms. We integrated tools like Adobe XD plugins for contrast checking directly into their workflow.
3. Content Creator Education: Even marketing and content teams received training on writing descriptive alt text, creating accessible headings, and ensuring video content had accurate captions and transcripts.

One anecdote really cemented this shift. I had a client last year, a large e-commerce platform, who insisted their “developers already knew accessibility.” Six months later, after a significant legal challenge, they brought me in. Their developers knew of accessibility, yes, but they didn’t know how to build for it consistently. The difference is profound. Knowing a concept exists versus having the practical skills to implement it are two entirely different things.

Veridian committed to integrating accessibility into every sprint. They added accessibility user stories to their JIRA board, just like any other feature. They established an “accessibility champion” on each team, responsible for reviewing pull requests for accessibility compliance. This wasn’t a suggestion; it was an organizational mandate from Sarah herself.

The Outcome: A Truly Inclusive Platform

After nearly eight months of intensive work, Veridian Health relaunched their patient portal. The difference was night and day. Automated audit scores soared from a dismal 35% to over 95%. More importantly, their manual testing with users with disabilities yielded overwhelmingly positive feedback. The woman who couldn’t log in before was now scheduling appointments independently. The user who relied on keyboard navigation could move through the entire application with ease.

The financial impact was significant too. Veridian avoided costly lawsuits and, perhaps more importantly, expanded their user base. Their patient satisfaction scores, particularly among older adults and individuals with disabilities, saw a marked improvement. This wasn’t just about compliance; it was about good business and ethical product development.

“It was the hardest eight months of my professional life,” Sarah admitted to me after the successful relaunch, “but it was also the most rewarding. We built something truly for everyone. It completely changed how we approach product development now. Accessibility isn’t a checkbox; it’s a foundational principle.”

My experience with Veridian Health taught me that building truly impactful accessible technology isn’t just about fixing code; it’s about fostering a mindset. It requires leadership buy-in, continuous education, and a genuine commitment to inclusivity from the very beginning of a project. It’s about understanding that diverse users bring diverse needs, and catering to those needs isn’t a burden – it’s an opportunity. If you’re not designing for everyone, you’re designing for no one.

What is the most common accessibility mistake companies make?

The most common mistake is treating accessibility as an afterthought or a “feature” to be added later, rather than integrating it into the initial design and development phases. This leads to costly retrofitting and often results in a less effective solution.

Are automated accessibility tools sufficient for ensuring compliance?

No, automated tools are a great starting point, catching about 30-40% of common issues. However, they cannot assess usability for all disabilities or verify semantic correctness in complex components. Manual testing with assistive technologies and diverse users is essential for comprehensive accessibility.

What are WCAG 2.2 Level AA standards and why are they important?

WCAG (Web Content Accessibility Guidelines) 2.2 Level AA are internationally recognized guidelines for making web content more accessible. They are crucial because they provide a framework for inclusive design, and many legal frameworks, including the ADA, reference them as the benchmark for digital accessibility.

How can I convince my leadership to invest in accessibility?

Focus on the business case: legal compliance (avoiding lawsuits), market expansion (reaching a wider audience), improved brand reputation, and enhanced user experience for all. Frame it as risk mitigation and a growth opportunity, not just an expense.

What is the role of ARIA attributes in accessibility?

WAI-ARIA (Accessible Rich Internet Applications) attributes provide additional semantic information to assistive technologies for dynamic or custom user interface components that native HTML elements might not adequately describe. They help screen readers and other tools understand the purpose, state, and properties of interactive elements, ensuring a more navigable experience.

Share: Facebook Twitter Pinterest LinkedIn

Copy Link