Accessibility Archives /Tag

Is WCAG Certification Possible?
Many businesses are on the hunt for something called “WCAG certification”—a stamp of approval to show their site is accessible. But is that even a real thing?

The Web Content Accessibility Guidelines (WCAG) are the widely accepted standard for creating accessible digital content. These guidelines help ensure websites, apps, and digital tools work for everyone—including people with disabilities. But here’s the catch: there’s no such thing as official WCAG certification. That doesn’t mean you’re out of luck, though.

In this article, we’ll unpack what WCAG really is, why it matters, and what practical steps you can take to prove your accessibility commitment—without chasing a non-existent certificate.

What Is WCAG — and Why It Matters

WCAG is a set of accessibility guidelines created by a group called the World Wide Web Consortium (W3C). It’s been updated over the years—versions 2.0, 2.1, and 2.2 are already in use, and a new draft version (WCAG 3.0) is in the works.

The guidelines are built on four main principles:
- Perceivable: Can people see, hear, or otherwise access your content?
- Operable: Can users interact with it, like using a keyboard or voice commands?
- Understandable: Is your site’s content and layout easy to follow?
- Robust: Will your site work across different devices, browsers, and assistive tech?
These principles help you build a better experience for everyone. And with around 1 in 4 Americans living with a disability, accessibility isn’t a niche issue—it’s a core part of serving your audience.

Can You Get WCAG Certified? (No — and Here’s Why)

Let’s make it simple: WCAG certification does not exist in any official form. The W3C—the organization behind WCAG—doesn’t issue certificates to websites or developers. So if someone tells you they can give you a WCAG certificate, that’s a red flag.

Here’s what does exist:
- WCAG Conformance: This means your website meets specific WCAG success criteria.
- Audit Reports: Accessibility experts can review your site and document its strengths and weaknesses.
- Professional Credentials: Individuals can take training and exams to show they understand accessibility standards.
What you can’t get is an “official” WCAG certification from any governing body. The W3C has actually decided not to create a certification program at all, stating that a formal seal could do more harm than good. So any so-called “WCAG certificate” should be treated carefully—think of it more as “we followed WCAG and have evidence” rather than a license or badge.

Why the Idea of Certification Still Matters

Even though WCAG certification isn’t real, the need to show good faith—especially during legal challenges—is very real.

If your site faces an ADA accessibility complaint, a detailed audit report or a public accessibility statement can help. It won’t guarantee immunity, but it may:
- Shorten legal negotiations
- Lower settlement demands
- Show that you’re actively working on improvements
Most lawsuits under the Americans with Disabilities Act (ADA) focus on fixing the problem (not financial damages at the federal level), but state laws like California’s Unruh Act can make things much more expensive. In some cases, businesses may face penalties of $4,000 per violation—per user session.

Many businesses choose to settle accessibility lawsuits rather than fight in court, with settlements typically ranging from $5,000 to $20,000, and sometimes far more. Proactively documenting your WCAG conformance can reduce those risks and costs.

What You Can Get Instead: Real Accessibility Certifications

While your website can’t be WCAG certified, you or your team can earn credentials that demonstrate knowledge of WCAG and broader accessibility concepts. These are well-respected in the field:
- CPACC – Certified Professional in Accessibility Core Competencies
  Great for content creators, marketers, and generalists. Covers topics like disability types, legal basics, and WCAG principles.
- WAS – Web Accessibility Specialist
  Tailored for developers and UX designers. Dives deep into the technical side: semantic HTML, ARIA, testing practices.
- CPWA – Certified Professional in Web Accessibility
  Combines both CPACC and WAS certifications. Ideal for accessibility leads or those overseeing compliance efforts.
These certifications don’t claim to be WCAG certification, but they do show your commitment to accessibility expertise.

Real Accessibility Is About Practical Action

Certifications help—but they’re not a shortcut. To build and maintain an accessible site, focus on practical, ongoing steps that create real impact.

Run Regular Accessibility Audits

You can use tools like WAVE or Lighthouse, but manual testing is essential too. Look for issues like missing labels, broken keyboard navigation, or poor heading structure. Save your reports as documentation in case questions arise later.

Fix High-Impact Issues First

Some problems—like missing alt text or contrast issues—pose bigger risks than others. Prioritize known trouble spots.

Bake Accessibility Into Development

Make accessibility part of your everyday workflow, not something you tackle at the end. Small habits make a big difference.

Publish a Public Statement

Adding an accessibility statement to your website builds trust and shows you’re being transparent and proactive.

Train Your Content Team

Every upload matters. A well-meaning update can unintentionally introduce accessibility problems—so make sure everyone’s equipped to do their part.

Should You Be Chasing WCAG Certification?

Not exactly. The smarter question is: how do you prove that your site meets WCAG standards?

Here’s how to show your work:
- Encourage team members to earn real accessibility credentials like CPACC or WAS.
- Hire an expert to audit your site and issue a detailed report.
- Post an accessibility statement on your site that outlines your efforts and future plans.
- Monitor your site and run regular checks to ensure improvements are sustained.
And remember: legal risk is growing. Thousands of lawsuits were filed in the past year alone over inaccessible websites. Many target websites that lack basic WCAG conformance.

Accessibility Partners Can Make the Difference

Trying to juggle deadlines, legacy code, and legal exposure? Outside help can give you the lift you need. Experienced accessibility partners don’t just run audits—they help you build a sustainable, legally defensible program.

What expert partners can offer:
- Full audits, including real-user testing
- Help fixing accessibility issues
- Ongoing monitoring to catch new problems
- Role-specific training for devs, designers, and content teams
And a key difference? The right partner will never promise fake WCAG certification. They’ll help you build real results.

You Don’t Need a WCAG Certificate—You Need a Plan

The idea of WCAG certification sounds comforting—but it’s not real. What is real? Earning your users’ trust by making your site work for everyone.

When you show that you’ve taken the right steps—training, audits, public transparency—you don’t need a certificate. You’ve already proven your commitment.

Ready to show your commitment to accessibility the right way?
Schedule an ADA accessibility briefing with 216digital and see how we help teams maintain long-term WCAG conformance and build more inclusive digital experiences.
Greg McNeil

May 14, 2025

Web Accessibility Training

Accessibility, WCAG, WCAG Certification, WCAG Compliance, Web Accessibility, web developers, web development
Don’t Be Fooled by False Positives in Accessibility
Imagine you’re scanning through an accessibility report when it flags a purely decorative image for missing alt text. You pause and double-check the code—aria-hidden= "true" is clearly set—yet the tool insists it’s an issue. In moments like these, you’re dealing with false positives.

When left unchecked, false positives can waste hours of development time, drain your budget, and leave real accessibility problems hidden beneath noise. For developers who regularly rely on automated accessibility testing, learning to recognize and reduce these inaccuracies is as essential as fixing actual accessibility barriers.

What a False Positive Really Is

Simply put, false positives occur when a testing tool incorrectly marks compliant content as inaccessible, even though it aligns perfectly with standards like WCAG. These mistaken alerts often create confusion and lead teams to fix things that aren’t broken—sometimes at the expense of overlooking real issues.

So, why do they happen? Usually, false positives stem from three common causes:
- Limited context: Automated tools understand code but not intent. Elements involving dynamic JavaScript or custom user settings can confuse them, triggering inaccurate alerts. For example, a modal loaded via JavaScript might be marked as inaccessible until it’s fully rendered, even if it meets all WCAG requirements when interactive.
- Overly cautious rules: Some tools are intentionally strict, flagging anything remotely questionable to avoid missing genuine issues. While well-intentioned, this can lead to excessive alerts. Developers end up treating these tools like overprotective smoke alarms—loud, constant, and sometimes hard to trust.
- Varied coding practices: Custom components or unconventional markup patterns, common in modern front-end workflows, often mislead algorithms expecting textbook HTML. Accessibility implemented through ARIA roles or JavaScript event handlers may trip up tools that expect static HTML structures.
Most developers have encountered these scenarios in practice: decorative icons labeled as “critical issues,” contrast alerts ignoring user-selected dark modes, or dynamic form elements incorrectly flagged for missing labels. Each instance represents the broader problem—tools missing the bigger picture.

The Hidden Costs of False Positives

When false positives become part of your day-to-day workflow, the cost isn’t just inconvenience—it’s real impact on time, trust, and outcomes.

Time and Budget Drain

Chasing down false positives can quickly become a costly distraction. Imagine your team spends hours rewriting alt text for images that never needed it. Those same resources could have resolved genuine issues or shipped new features, improving your product instead of spinning its wheels. For larger teams or enterprise projects, these hours quickly compound into days—adding up to measurable delays in delivery and inflated budgets.

This resource drain can be particularly painful during audits or compliance deadlines when teams are working under pressure. Every misfire takes attention away from what truly matters: building inclusive digital experiences for real users.

Erosion of Trust in Tools

Repeated inaccurate alerts erode confidence in accessibility tools. Developers may grow skeptical, dismissing genuine issues as “probably another false positive.” This skepticism can cause real accessibility problems to slip through unnoticed, undermining the very purpose of using these tools.

Once the trust is gone, so is the motivation to use these tools proactively. Instead of integrating accessibility checks early and often, teams may push them off to the final stages—or abandon them altogether. That’s a slippery slope that compromises both compliance and user experience.

Legal and Reputational Risks

Perhaps most serious of all, excessive false positives can mask true accessibility problems. If your team assumes a website is compliant based on misleading tool reports, users could face unexpected barriers. That scenario leaves your organization vulnerable to lawsuits, fines, and damage to brand reputation.

It’s a dangerous combination: a dashboard showing 100% compliance while screen reader users struggle to navigate key interactions. In the worst-case scenario, this could lead to legal action under ADA, Section 508, or similar laws depending on your location or industry.

Practical Steps to Minimize False Positives

It’s not about choosing between automation and accuracy—it’s about striking a balance. Here are a few strategies that can help:

Choose Tools Carefully

Accuracy is crucial. Opt for tools known to minimize false positives—look at reviews, user communities, and real-world feedback. Tools that offer detailed explanations for each issue help developers evaluate the context instead of blindly applying changes. Bonus points for tools that integrate smoothly into your CI/CD pipeline or Git workflows, allowing developers to spot and triage issues earlier in the process.

Combine Automated Testing with Manual Checks

Automation is valuable, but humans bring the necessary context. Regular manual reviews, particularly with real assistive technologies like screen readers or keyboard-only navigation, confirm whether flagged issues are real or simply more false positives. This human element provides critical insights into actual user experiences that no machine can replicate on its own.

Pairing automated scans with periodic expert reviews ensures you don’t end up trusting the scanner more than the people you’re building for.

Educate and Empower Your Team

Providing training ensures everyone knows what a genuine accessibility issue looks like. Regular team briefings, quick reference guides, or lunch-and-learn sessions can equip developers and QA specialists to confidently distinguish true issues from false positives during daily workflows.

It also helps to document commonly misflagged elements in your internal dev wiki or design system docs. That way, developers don’t waste time rediscovering the same conclusions again and again.

Shift Accessibility Testing Left

Accessibility testing should be a routine practice, integrated into every development phase—right alongside linting, unit testing, and code reviews. Early checks catch issues and limit the spread of false positives throughout your codebase.

This shift-left approach reduces last-minute panic before launches and promotes a culture where accessibility is part of the conversation from the start. Teams that embed these habits often find they’re able to respond to flagged issues faster and with greater confidence.

Engage Accessibility Specialists

Sometimes, complex implementations or large-scale projects need specialized insight. Accessibility experts can fine-tune automated testing parameters, spot challenging edge cases, and provide tailored recommendations. Their guidance helps reduce false positives and sets your project on a sustainable path forward.

Even a short-term partnership or audit can clarify which alerts deserve attention and which are tool-generated noise. Think of it like calling in an electrician to check wiring behind the walls—some things are better seen with trained eyes.

A True Positive Path Forward

False positives in accessibility testing aren’t just minor annoyances—they cost valuable resources, erode trust, and potentially expose your site to compliance risks. Left unchecked, they can derail good intentions and cause more confusion than clarity. But with the right balance of tools, process, and people, they don’t have to.

Start by picking better tools, pairing them with manual validation, and investing in your team’s knowledge. Make accessibility part of your workflow—not just a checkbox at the end. And when needed, bring in expert support to cut through the noise.

Want to take your accessibility efforts to the next level? Schedule an ADA briefing with 216digital. Our team will help you build a sustainable, practical strategy for achieving real-world accessibility and staying ahead of compliance requirements.
Greg McNeil

May 13, 2025

Testing & Remediation

Accessibility, Accessibility Remediation, false positives, Web Accessibility Remediation, web developers, web development, Website Accessibility
Celebrate GAAD: 6 Ways to Support Inclusion
On Thursday, May 15, 2025, workplaces, campuses, and whole communities will hit “pause” to celebrate Global Accessibility Awareness Day (GAAD)—a grassroots holiday that shines a bright spotlight on digital inclusion.

GAAD sprang from a single, compelling truth: when more people think about accessibility, more people build with accessibility in mind. The numbers speak for themselves—over one billion people around the globe live with a disability, and all of them interact with the web. Boosting access lifts the experience for everyone, from keyboard-only power users to friends scrolling on cracked phone screens. That’s why GAAD isn’t just a tech-industry affair; it’s a call-out that accessibility fuels brand trust, search performance, and legal peace of mind across every sector.

If building an inclusive business matters to you, GAAD is your moment to turn good intentions into forward-motion.

How GAAD Began: A Blog Post That Sparked a Global Movement

Flash back to 2011. Los Angeles developer Joe Devon dashed off a late-night blog post urging his peers to make accessibility “mainstream.” Toronto-based accessibility champion Jennison Asuncion retweeted it, and the duo launched the first GAAD in 2012.

Their concept was delightfully simple: one day each May devoted to thinking and talking about accessibility. No required format, no corporate sponsor—just open-source energy. It stuck. Fourteen years later, GAAD events stretch across every continent, from campus demos to enterprise-scale product sprints. The big takeaway? Progress catches fire the moment developers and designers decide today’s the day to try something new.

Why GAAD Still Matters in 2025

A decade of lawsuits, legislation, and public advocacy has pushed web accessibility onto mainstream project plans. Plenty of U.S. businesses now bake WCAG success criteria into design systems. Yet snag points remain—untagged PDF order forms, checkout flows that lose focus, videos whose auto-captions garble half the words.

GAAD serves as a structured pause to ask three energizing questions:
1. What has improved? Celebrate resolved tickets, fresh color palettes, and alt-text workflows that finally stick.
2. Where do gaps remain? Surface those pesky “parking-lot” issues that never seem to reach sprint planning.
3. How can we raise the bar? Turn wish-list ideas into measurable road-map line items.
Skip this reflection and accessibility efforts stall. Embrace it and teams rediscover energy, secure budget, and align with website-legal-compliance goals.

What’s In It for Business: Real-World Upside
- Highlight Your Commitment: Show your accessibility timeline—audit dates, remediation milestones, and future targets—to build trust with customers, regulators, and stakeholders.
- Strengthen Your Brand: Values-driven shoppers vote with their wallets. Visibility on GAAD proves inclusion is in your brand DNA, not a post-litigation scramble. Expect positive press, boosted employee pride, and a leg up in crowded markets.
- Engage Your Community: Accessibility stories humanize metrics. A quick screen-reader demo or a customer testimonial about smoother checkout turns policy into empathy—and empathy drives adoption far beyond the dev team.
Six Meaningful Ways to Celebrate GAAD 2025

Tip: Pick one or two ideas this year—depth beats volume. Next May, build on what worked.

Share Your Story

Craft a LinkedIn post, blog article, or internal memo chronicling your journey—from first spark (maybe an ADA letter, maybe a passionate employee) to key lessons and next goals. Authentic reflection invites peers to chime in with candid feedback.

Post on Social Media

Bite-sized content travels farther than white papers. Try a 60-second clip of your new color-contrast fix, a carousel of screen-reader shortcuts, or a punchy stat (“Only 3.1 % of home pages meet basic WCAG color contrast.”) with #GAAD and #AccessibilityMatters. Real, raw, and shareable wins every time.

Host an Internal Accessibility Chat

Swap formal workshops for a relaxed brown-bag session. Demo a color-blindness simulator, read sample alt text aloud, or show leadership how one missing label blocks checkout in two keystrokes. Thirty minutes can uncover easy fixes hiding in plain sight.

Educate Your Team

Use GAAD as a micro-learning catalyst. Share a five-minute video on ARIA landmarks, drop a Slack thread with a contrast-ratio calculator, or challenge designers to run a screen-reader audit on your top landing page. Small feats build big confidence.

Start an Accessibility Goals List

Turn “we should” into “we will.” Pick three goals to nail before GAAD 2026—mandatory alt-text fields in your CMS, automated axe-linter checks in pull requests, or a third-party manual audit every year. Publish the list where product owners can’t miss it.

Update Your Accessibility Statement

Keep your public pledge current. Swap vague promises for concrete dates and standards (“As of April 2025, we meet WCAG 2.2 AA on all primary templates”), add a feedback channel straight to your accessibility lead, and spotlight recent wins like reduced-motion options and crisper captions.

Looking Ahead: Building Daily Culture

GAAD is the spark, not the whole fire. Long-term inclusion thrives in daily processes, not one-day celebrations:
- Design sprints: Invite a user with assistive tech into prototype tests.
- Code reviews: Add a check for semantic HTML and keyboard flow.
- Content workflows: Make alt-text and caption columns non-optional.
- Customer support: Train agents to log and escalate accessibility barriers reported by users.
Celebrate your internal champions—developers who relish accessibility puzzles, marketers who write crystal-clear link text. Recognition programs, dedicated Slack channels, or monthly “a11y show-and-tell” sessions keep the momentum humming even when deadlines loom.

Your Invitation to Take the Next Step

GAAD 2025 marks progress, not the finish line. Whether you’re fresh off your first audit or refining mature design systems, there’s always another barrier to remove, another user to welcome. Use the day to celebrate wins, spotlight gaps, and commit to tangible goals.

Need a roadmap? 216digital offers concise ADA-compliance briefings that turn audits into actionable plans, marrying web-accessibility best practices with website-legal-compliance strategies. Schedule a session and walk away with clear next steps, realistic timelines, and renewed confidence that your site greets every visitor with open arms.

Let’s turn one Thursday into twelve months of better digital experiences—because inclusion, like code, gets better with every iterate-and-improve cycle.

Happy GAAD—and happy building!
Greg McNeil

May 12, 2025

Web Accessibility Remediation

Accessibility, ADA Website Compliance, GAAD, Global Accessibility Awareness Day, Web Accessibility, Website Accessibility
aria-label vs aria-labelledby: When and How to Use Each
As developers, we know every interactive element—buttons, dialogs, inputs—needs an accessible name. Good semantic HTML handles this automatically. But let’s face it, our apps get complicated. Sometimes, buttons only show icons, dialogs pull their titles from external components, or complex widgets break the neat semantic model. That’s where ARIA attributes come in. Specifically, aria-label and aria-labelledby help us provide clear,

screen-reader-friendly names. But they aren’t interchangeable. Knowing when to use each can save you debugging headaches down the line.

The Common Ground

First off, let’s review their similarities. Both aria-label and aria-labelledby override native labels provided by HTML. Both directly influence what assistive technologies like screen readers announce. Ideally, though, these ARIA attributes should be your fallback, not the go-to solution—semantic HTML labels are always best.

Quick side note: If you’re ever curious about the details, check out the Accessible Name Computation Algorithm.

Using aria-label: Direct and Hidden

aria-label lets you set an accessible name directly with a string—no extra DOM needed. Here’s a simple example you’ve probably seen before:
```
<button aria-label="Search">
  <svg aria-hidden="true" focusable="false">...</svg>
</button>
```
Perfect for icon buttons or elements that don’t have visible labels. But there’s a catch:
- It’s invisible to sighted users. If your visual UI doesn’t clearly indicate the button’s purpose, this can confuse people.
- It’s static and won’t automatically update with dynamic content changes.
- Localization is manual—you need to integrate these labels into your internationalization setup.
Use aria-label when simplicity outweighs these drawbacks—like icon-only buttons that stay consistent across languages.

aria-labelledby: Harness Visible Content

aria-labelledby points directly to visible content already on the page to build the accessible name. This is super helpful for complex widgets or dialogs:
```
<div role="dialog" aria-labelledby="dialog-title">
  <h2 id="dialog-title">Settings</h2>
  
</div>
```
This is great because:
- Updates to referenced elements automatically update the accessible name—handy for localization or dynamic UI changes.
- You can reference multiple IDs to build richer, descriptive names.
The downside? It requires stable IDs. Reference a missing ID, and your screen reader users will hear nothing—a silent fail you won’t catch easily without testing.

Picking the Right Attribute

Choosing between these two attributes boils down to visibility and localization:
- Visible text already on screen? Use aria-labelledby.
- Icon-only or hidden label? Use aria-label.
- Multiple languages or dynamic content? Lean heavily towards aria-labelledby.
Following these simple guidelines can help keep your UI accessible and your codebase clean.

Common Mistakes (And How to Dodge Them)

Let’s get real: we’ve all made these mistakes:
1. Using both attributes at once: Screen readers only honor aria-labelledby. The leftover aria-label just confuses whoever touches your code next.
2. Referencing IDs that don’t exist: Silent errors are the worst. Double-check your references with automated tools like axe-core.
3. Static English aria-labels on multilingual sites: Always leverage your translation pipeline or use aria-labelledby with translated DOM elements.
Quick example: Imagine a delete button labeled with aria-label="Delete" in English. When your app gets translated into Spanish, this button label stays stuck in English. Switching to aria-labelledby referencing a translated element solves it instantly.

Performance and Maintenance Tips

In frameworks like React or Vue, manage your DOM carefully. Always ensure referenced elements exist in the DOM before referencing components mount. Add automated accessibility checks (like Lighthouse) into your CI/CD setup. They’ll quickly catch misconfigured labels and help you maintain consistent accessibility.

Advanced Label Composition

Need more detail? Stack IDs with aria-labelledby:
```
<span id="action">Confirm</span>
<span id="item">your subscription</span>
<button aria-labelledby="action item">...</button>
```
Now the screen reader clearly announces, “Confirm your subscription.”

Dynamic content? Even simpler:
```
const statusLabel = document.getElementById("status");
statusLabel.textContent = isExpired ? "Expired" : "Active";
// aria-labelledby references statusLabel automatically
```
This dynamic updating is invaluable for reactive or state-driven UI.

Testing Your Accessible Names

Don’t skip manual checks. Fire up VoiceOver, NVDA, or even JAWS and tab through your components the way real users do. Navigate end‑to‑end, listen for odd announcements, and confirm the focus order feels right. Then pair those spot checks with automated tools in CI so labeling issues get fixed long before code ships.

Wrapping Up: Making Strategic Choices

Understanding when to use aria-label versus aria-labelledby might seem minor, but it significantly impacts users’ experience. Choose aria-label for simplicity and directness, especially on icon-driven interfaces. Go with aria-labelledby when leveraging visible, dynamic, or localized content.

Remember, accessibility is about making your interfaces clear for everyone, not just users relying on assistive tech. The strategic use of these attributes ensures your app feels polished and intuitive.

Need a quick gut‑check? Schedule an ADA briefing with 216digital. We’ll walk through your codebase together and make sure every label—and the rest of your accessibility stack—hits the mark.
Greg McNeil

May 9, 2025

How-to Guides

Accessibility, ARIA, aria-label, Web Accessibility, web developers, web development

Accessible Accordion vs Disclosure: Dev Best Practices

Disclosures and accordions show up all over the place—FAQs, menus, settings panels—you name it. They seem simple enough, right? But making sure they actually work for everyone takes more than just toggling some content and calling it a day.

If you’ve ever wondered when to use <details> versus building an accordion with buttons and ARIA, or how to keep screen reader users from getting lost in a sea of hidden panels, you’re not alone. This guide breaks it all down—what to use, when to use it, and how to build a truly accessible accordion without overcomplicating the code.

What Are Disclosure and Accordion Widgets?

Disclosure Widgets: Simple, Native, and Often Overlooked

Disclosures—also known as show/hide widgets—are ideal for toggling a single section of content. Think expandable FAQs or inline help that doesn’t clutter the UI by default.

Here’s a basic example using semantic HTML:

<details>
  <summary>Need more info?</summary>
  <p>Here are more details you might find useful.</p>
</details>

This pattern is fully native and built into the browser, which means it comes with keyboard support and screen reader compatibility right out of the box. You also get the open attribute, which allows you to control whether the content is expanded by default.

The main advantage here is simplicity—no JavaScript needed, and fewer chances to introduce accessibility issues.

Accordion Widgets: More Complex, More Control

An accessible accordion expands on the idea of disclosure by managing multiple content panels. In most implementations, only one section is open at a time, helping users stay focused and reducing cognitive overload.

You can build an accordion using multiple <details> elements, but if you want to control behavior more precisely—like closing other panels when one opens—you’ll need JavaScript.

Here’s what a minimal HTML-only version might look like:

<details name="accordion">
  <summary>Step 1</summary>
  <p>Instructions for step one.</p>
</details>

But to meet WCAG standards for a true accessible accordion, you’ll need to manage keyboard navigation, state indicators, and focus behavior—topics we’ll cover next.

Accessibility Considerations Developers Must Prioritize

Keyboard Navigation That Works for Everyone

An accessible accordion must support meaningful keyboard interactions. Here’s what users expect:

Tab and Shift + Tab to move between interactive elements.
Enter or Space to toggle a section open or closed.
Arrow Up/Down or Home/End to move between accordion headers in more advanced versions.

Missing any of these can make your component unusable for keyboard users. The WAI-ARIA Authoring Practices offer detailed guidance on accordion interaction patterns—worth bookmarking for reference.

Use Semantic Elements—Always

If there’s one golden rule, it’s this: never sacrifice semantics for styling.

That means:

Use <button> for interactive triggers—not <div>, <span>, or anchor tags without href.
If you’re toggling visibility, it’s a button, not a link.
Ensure that elements behave as users (and assistive technologies) expect.

Using semantic elements is one of the most effective ways to ensure your accessible accordion behaves predictably across screen readers and input types.

Add ARIA Where Needed, Not Everywhere

ARIA should enhance native HTML—not replace it. But when you’re building a custom accordion in JavaScript, ARIA becomes essential for communicating component state.

Here’s a basic implementation:

<button aria-expanded="false" aria-controls="info">More Info</button>
<div id="info" hidden>
  <p>Here’s the additional info.</p>
</div>

const btn = document.querySelector('button');
const content = document.getElementById('info');
btn.addEventListener('click', () => {
  const expanded = btn.getAttribute('aria-expanded') === 'true';
  btn.setAttribute('aria-expanded', String(!expanded));
  content.hidden = expanded;
});

This ensures screen readers can track whether content is visible or hidden, creating a seamless experience for all users.

Common Accessibility Mistakes (and How to Fix Them)

Even seasoned devs slip up. Here are a few common issues that can break accessibility—and how to address them:

Mistake	Problem	Solution
Non-focusable triggers	`<div>`s with `onclick` don’t work for keyboard users	Use `<button>` or add `tabindex="0"`
Links used instead of buttons	`<a>` without `href` doesn’t convey intent	Replace with semantic `<button>`
Missing state feedback	Screen readers can’t detect if content is expanded	Dynamically update aria-expanded
Focusable elements in hidden content	Users tab into content they can’t see	Use hidden or display: none correctly

Most of these issues stem from skipping semantic HTML or relying too heavily on JavaScript without proper state management. An accessible accordion avoids these pitfalls by focusing on clarity, intent, and interaction feedback.

Best Practices for Developers

Building an accessible accordion that holds up in the real world means going beyond code snippets. Here’s what to keep in mind:

Start with Progressive Enhancement

Whenever possible, begin with HTML <details> and <summary>. They’re accessible by default and supported in all major browsers. Use JavaScript only when additional behavior—like limiting panels to one open at a time—is truly needed.

Prioritize Focus Visibility

An accordion is only as accessible as its focus states. Make sure every interactive element has a visible focus indicator, and don’t override :focus-visible in your CSS. This isn’t just a WCAG 2.2 requirement—it’s also just good UX.

Avoid Overengineering with ARIA

Don’t reach for ARIA unless you need to. Native HTML tends to be more robust across assistive technologies, and using ARIA incorrectly can make things worse. When in doubt, simplify.

Test Like a User

If you’re not testing with a keyboard, you’re flying blind. Add screen reader testing with NVDA, JAWS, or VoiceOver into your QA flow. Run Lighthouse and WAVE scans, but don’t rely on them alone—they won’t catch everything an actual user would encounter.

Real-World Application: From Good to Great

Let’s say you’re rebuilding a legacy FAQ section. It uses JavaScript to toggle open answers, but it’s riddled with <div>s and missing ARIA.

Start by replacing the markup with semantic HTML:

<details>
  <summary>What’s your return policy?</summary>
  <p>You can return items within 30 days.</p>
</details>

Then, enhance with JavaScript if you want only one section open at a time. Layer in ARIA attributes to improve screen reader support. Suddenly, you’ve turned a clunky widget into a polished, accessible accordion that works for everyone.

Wrapping It Up

Disclosures and accordions might seem interchangeable, but the differences matter—especially when accessibility is on the line. Whether you’re working on a quick FAQ or building a fully dynamic interface, an accessible accordion ensures users with different abilities can navigate and interact with your content.

At the end of the day, accessibility isn’t about checking boxes—it’s about building better interfaces for everyone.

Need help auditing your components?

216digital offers in-depth accessibility support. Schedule an ADA compliance consultation to review your current implementation and ensure everything meets WCAG standards—without compromising design or performance.

Greg McNeil

May 8, 2025

How-to Guides

Accessibility, accessible accordion, Disclosure, How-to, HTML, semantic HTML, web developers, web development

ADA Settlements: Risks, Costs, and Legal Outcomes

When a business is hit with an ADA website accessibility lawsuit, the costs can be more than just financial—they can ripple through development timelines, legal budgets, and brand reputation. And with digital accessibility lawsuits rising yearly, more developers, designers, and product teams are being pulled into legal remediation efforts they didn’t see coming.

But here’s the truth: Not every site needs to achieve 100% WCAG conformance overnight to avoid legal trouble. Smart, risk-aware development teams know how to focus on what matters most—protecting users and reducing legal exposure—without getting bogged down in unnecessary technical perfection.

This article breaks down what ADA settlements typically involve, how to assess legal risk in accessibility work, and when to prioritize critical fixes versus deeper WCAG alignment. Whether you’re retrofitting an existing website or launching something new, understanding the difference between technical and practical compliance can help you make more strategic choices.

What Are ADA Settlements and Why Do They Matter?

An ADA settlement is a legal agreement made outside of court after someone files a complaint or lawsuit under the Americans with Disabilities Act, usually regarding a website or app that isn’t accessible to people with disabilities. These agreements typically include:

A financial payment to the plaintiff (often $5,000–$50,000)
A commitment to fix specific accessibility barriers
A timeline for remediation and reporting requirements
A stipulation to train internal teams on accessibility best practices

Most companies settle because litigation is expensive, time-consuming, and unpredictable. Settling often avoids further public exposure or escalating legal fees—but it still requires swift technical action and long-term accountability.

The Real Costs of ADA Settlements

The direct cost of an ADA settlement can vary, but here’s a realistic breakdown for small to midsize organizations:

Settlement payout: $5,000–$30,000 (on average)
Attorney fees (your side): $5,000–$20,000+
Attorney fees (plaintiff’s side, often paid by you): $5,000–$50,000
Remediation costs: $5,000–$50,000 depending on site size and complexity
Training and monitoring costs: Ongoing

Beyond dollars, there’s the cost of dev time, stakeholder panic, potential press coverage, and damage to brand reputation. It’s no wonder more companies are starting to take accessibility seriously before a lawsuit lands on their desk.

The Technical vs. Practical Accessibility Approach

Let’s be clear—full WCAG 2.1 AA conformance is a great long-term goal. But when lawsuits or legal demands hit, the more strategic question becomes: What do we fix first to reduce the most risk, fastest?

Technical Approach

The technical approach focuses on achieving full conformance with WCAG criteria, including:

Semantic structure (landmarks, headings, ARIA roles)
Keyboard access for all functionality
Color contrast and visual design
Error prevention and accessible forms
Text alternatives for images, media, and interactive elements

While comprehensive, this approach can be time-consuming and expensive, especially if your site wasn’t built with accessibility in mind.

Practical Approach

The practical approach focuses on real-world usage and risk mitigation, emphasizing:

High-risk issues likely to appear in a lawsuit (keyboard traps, unlabeled buttons, inaccessible forms)
Fixes that enable blind, low-vision, and mobility-impaired users to navigate, read, and transact
Remediating issues cited by popular screen readers (e.g., NVDA, VoiceOver) and automated tools (e.g., Google Lighthouse, WAVE)

This approach doesn’t replace full compliance—it prioritizes it. For many developers under pressure, this is the smarter path in the short term.

How to Identify High-Risk Accessibility Issues

You don’t need to fix every single WCAG failure at once. Start by focusing on the most common issues that trigger ADA lawsuits:

Issue Type	Description
Keyboard Traps	Can’t tab out of a modal or menu
Missing Button Labels	Screen readers announce “button” with no context
Inaccessible Forms	Fields lack labels, or error messages aren’t announced
Poor Color Contrast	Text is unreadable for people with low vision
Broken Skip Links	Users can’t bypass repetitive navigation
Inconsistent Heading Use	Screen readers can’t navigate efficiently
Missing Alt Text	Images lack descriptions for screen reader users

Each of these can significantly affect usability—and is a frequent target in lawsuits.

Real-World ADA Settlement Outcomes

To understand how this plays out in the wild, here are three simplified examples:

1. Small Retailer Settles for $15K + Fixes

A small e-commerce business received a demand letter after their cart and checkout were found to be inaccessible to keyboard users. They settled for $15,000 and committed to a 90-day remediation plan targeting key transactional flows.

2. Nonprofit Faces Multiple Complaints

A regional nonprofit was hit with three nearly identical lawsuits within six months. They paid over $60,000 total in settlements, then hired an accessibility partner to run audits, update templates, and add ongoing monitoring.

3. Enterprise Brand Chooses Full Compliance

After receiving a lawsuit, a national retailer chose to settle and invest in full WCAG 2.1 AA remediation. The effort took over 9 months but allowed them to build a sustainable accessibility program and avoid future litigation.

How to Strengthen Accessibility and Reduce Legal Risk

Navigating ADA compliance doesn’t require perfection—it requires prioritization. While no one expects your team to fix everything overnight, there are key actions you can take right now to reduce your legal exposure and improve user access:

Get Grounded in WCAG

You don’t need to memorize the entire spec, but your team should understand the fundamentals. Focus on guidelines related to navigation, labeling, and readable text—areas most often cited in ADA settlements.

Run an Audit—Then Act

Automated scans won’t catch everything, but they’re a fast way to surface high-risk gaps like missing alt text or poor contrast. Follow with targeted manual testing or bring in a specialist like 216digital to validate findings and prioritize fixes.

Train the Right Teams

Developers aren’t the only ones who touch your site. Marketing, design, and content teams need basic accessibility training so issues aren’t reintroduced after remediation. This step is often required as part of ADA settlements and signals long-term commitment.

Monitor Continuously

Accessibility is not a “set it and forget it” process. With 216digital’s a11y.Radar, teams can catch regressions early and stay ahead of future lawsuits.

Stay Adaptive

Standards evolve. So should your strategy. Track changes to WCAG and be ready to update design systems, templates, and workflows to maintain long-term compliance.

Final Thoughts: Don’t Wait for a Lawsuit

ADA settlements are a growing risk—but they’re also preventable. Developers and site owners don’t have to boil the ocean to protect themselves. By taking a practical, high-impact approach to accessibility and knowing what issues matter most in legal outcomes, you can avoid major pitfalls while creating better digital experiences for everyone.

The key is to start. Run a scan, fix a few common issues, and build from there. If you’re unsure where to begin, partnering with an accessibility expert like 216digital can guide you through smart remediation strategies that work—before a lawsuit forces your hand.

Need help navigating accessibility risks?

Schedule a free 15-minute ADA briefing with 216digital. We’ll review your site and talk strategy and help you take the first step toward compliance and peace of mind.

Greg McNeil

May 7, 2025

Legal Compliance, Uncategorized

Accessibility, ADA Lawsuit, ADA Lawsuits, ADA settlements, Web Accessibility

How Digital Accessibility Training Reduces Legal Risk
You’ve already put in the work. Your site has been remediated, the big accessibility issues are behind you, and things are finally in a good place. That’s huge. But here’s the thing—accessibility doesn’t stay fixed on its own.

Websites evolve fast. New content gets published. Layouts shift. Design trends change. And unless your internal team knows how to keep accessibility in place, even small updates can knock you out of compliance before you realize it.

This is where digital accessibility training becomes your secret weapon. It’s not about starting over—it’s about staying in control, protecting your investment, and building confidence across your team.

Why Accessibility Isn’t “One and Done”

If you’ve ever updated a button style or added an image without checking the alt text, you already get it: accessibility issues can sneak in easily.

Every time your team touches the website—whether it’s a blog post, a product update, or a code tweak—they’re either maintaining compliance… or breaking it.

Remediation isn’t the finish line. It’s the starting point for sustainable accessibility. And without digital accessibility training, your team is basically driving without a map. One wrong turn, and you’re back in legal territory.

The Legal Stakes: Second-Time Lawsuits Are Surging

Here’s a stat that should stick: 41% of accessibility lawsuits last year were filed against companies that had already been sued before. That’s not a coincidence. It’s a sign.

Fixing things once doesn’t mean you’re covered forever. If issues come back—especially the same ones—courts notice. And they’re less patient the second time around.

Digital accessibility training helps your team catch issues early, long before they show up in a legal complaint. It’s the difference between being reactive and being resilient.

Training Makes You Proactive, Not Dependent

When your team is trained, they can:
- Spot accessibility problems in real-time
- Design and code with accessibility in mind from the start
- Review content before it goes live—not after complaints roll in
Instead of waiting for a vendor audit (and the invoice that comes with it), you can handle it in-house. That means fewer delays, fewer emergencies, and fewer costs.

Digital accessibility training empowers your team to do accessibility right—the first time.

It’s Not Just the ADA Anymore

If your organization works with government agencies, serves international users, or plans to expand globally, accessibility compliance means more than just the ADA.

You’ve got:
- Section 508 in the U.S.
- EN 301 549 in the EU
- AODA in Ontario, Canada
- And, of course, WCAG, which ties it all together
Training helps your team navigate all of it. No guessing. No scrambling. Just smart, informed decisions that keep you compliant across borders.

Why Training Costs Less (and Does More) Than You Think

Hiring outside help every time something breaks? That adds up—fast.
- Emergency audits
- Last-minute fixes
- Legal consultations
- Brand damage
Now compare that to the cost of training your internal team once—and watching them catch and prevent those issues every day.

Digital accessibility training is a one-time investment that keeps paying off. It saves time, reduces legal risk, and builds real, lasting confidence across departments.

What 216digital’s Training Really Looks Like

At 216digital, we don’t do cookie-cutter courses. Your team isn’t generic—and your training shouldn’t be either.

Here’s what our digital accessibility training includes:
- Custom learning paths based on your CMS, platform, and team roles
- Modules for designers, developers, content creators, and PMs
- Real examples from your own website
- Practical tips that match the tools you already use
- Built-in support for the remediation work you’ve already completed
This isn’t about teaching theory. It’s about building confidence and making sure your site stays accessible.

Who Needs to Be Trained?

Short answer: anyone who touches your website. Because accessibility isn’t just a dev thing. It’s not just a design thing. It’s a whole team thing.
- Developers learn to code accessibly from the ground up
- Content creators learn how to format text, links, and images the right way
- Designers learn how to make inclusive choices from the start
- QA testers learn what to look for before pushing updates live
When the whole team is on the same page, accessibility becomes second nature—not an afterthought.

A Human Approach That Actually Sticks

At 216digital, we live this stuff. We’re developers, writers, testers, and designers just like you. We’ve seen how frustrating accessibility can be when it feels like a mystery—and we’re here to make it feel manageable.

Our digital accessibility training is:
- Practical – You’ll use what you learn right away
- Approachable – No jargon, no lectures, just real conversations
- Supportive – We’re here to help, not to judge
Accessibility is about people. So is training.

The Bottom Line: Keep What You’ve Built

You’ve already made a big investment in accessibility. Don’t let it fade over time.

Digital accessibility training is how you protect that work, reduce legal risk, and give your team the tools to move forward with confidence.

Let’s make sure your website stays inclusive—for everyone who needs it.

Ready to empower your team? Learn more and schedule a custom session at 216digital.com/216digit-training
Greg McNeil

April 30, 2025

Web Accessibility Training

Accessibility, Accessibility Training, Marketing, Web Accessibility, Web Accessibility Training, web development, Website Accessibility
How to Comply with the Accessible Canada Act (ACA)
More than 8 million Canadians aged 15 and older—about 22% of the population—live with a disability. For many Canadians, participating in everyday life isn’t as simple as it should be. Whether it’s trying to book a train ticket online or reading government services on a mobile device, too many still face digital and physical barriers.

The Accessible Canada Act (ACA) was created to help change that. It’s a law designed to make Canada more accessible for everyone, including online spaces. This guide breaks down what the ACA means, who needs to follow it, and how you can make your website more accessible—without needing to be a tech expert.

Understanding the Accessible Canada Act (ACA)

The ACA was introduced in 2018 and became law in 2019. It’s part of Canada’s big-picture goal to be barrier-free by 2040. That means removing obstacles across seven key areas:
- Jobs and workplaces
- Physical spaces
- Digital content and tech (like websites and apps)
- Communications
- Buying goods and services
- Public programs
- Transportation
What makes the ACA especially strong is that it was shaped by people with disabilities, organizations, and community leaders. It’s not just a set of rules—it’s a promise to include all Canadians in every part of life.

Who Needs to Comply with the ACA?

The ACA applies to federally regulated organizations. This includes:
- Government departments and agencies
- Crown corporations (like Canada Post or CBC)
- Banks and federal financial institutions
- Telecom companies (like phone and internet providers)
- Airlines, railways, and ferries
- Parliament (Senate and House of Commons)
If you fall into one of these categories, you must follow the ACA. But even if you don’t—say you run a private business or work under a provincial law—following the ACA is still a smart move. It can reduce legal risk, build trust with customers, and improve everyone’s experience with your website.

The Real-World Impact of Web Accessibility

Yes, the ACA is a law. But it’s also about something much deeper: inclusion.

When your website is accessible, it’s easier for everyone to use—not just people with disabilities. Think about clear navigation, readable fonts, and keyboard-friendly features. These help:
- Older adults
- People using screen readers
- Those with low vision or color blindness
- Anyone using voice commands or assistive devices
Accessible sites also rank better on search engines, reach wider audiences, and show you care about being fair and welcoming. That’s good for business and even better for community trust.

ACA Web Accessibility Standards and Guidelines

To follow the ACA, many organizations use a standard called WCAG 2.1 Level AA (Web Content Accessibility Guidelines). While the ACA doesn’t make this mandatory, it’s the most recognized guide for creating accessible websites.

WCAG helps you cover:
- Text alternatives for images (like alt text)
- Keyboard access for people who can’t use a mouse
- Readable color contrast and font sizes
- Clear layout and structure
Another tool is EN 301 549, a European standard adopted in Canada. It adds more guidance for software, hardware, and mobile apps.

Using WCAG and EN 301 549 shows you’re serious about accessibility—and helps prove ACA compliance if questions ever come up.

Who Enforces the ACA—and What Happens If You Don’t Comply?

Different agencies oversee different sectors:
- Accessibility Commissioner: Reviews complaints and enforces penalties
- Canadian Transportation Agency: Handles transport issues
- CRTC: Monitors telecom and broadcasting
- FPSLREB: Focuses on federal workplace issues
If you break the rules under the ACA, you could face:
- Fines up to $250,000 per violation
- Compliance orders or warnings
- Corrective action agreements
It’s much easier—and smarter—to stay ahead of the curve.

How to Meet Web Accessibility Requirements

Start With an Audit

Use automated tools, but don’t stop there. Pair them with real human testing—especially from people with disabilities.

Design with accessibility in mind:
- Add text descriptions to images
- Make sure all parts of your site work with a keyboard
- Use simple, readable fonts
- Keep contrast between text and background strong
Get Feedback From User

People with lived experience can help you spot issues you may have missed.

Test Everything

Don’t forget about PDFs, videos, and mobile apps—they all need to meet ACA goals, too.

ACA Reporting and Documentation

If you’re federally regulated, the ACA says you must publish:
- An Accessibility Plan: This outlines how you’ll find and remove barriers, and must include input from people with disabilities.
- Progress Reports: Regular updates that show what’s been done and what’s next.
These aren’t just paperwork. They’re proof that you’re doing the work—and thinking long-term.

How to File an ACA Complaint

If someone feels a business or organization is breaking the ACA, they can file a complaint. The steps include:
1. Find the right agency (such as the Accessibility Commissioner or CTA)
2. Submit the complaint online or in another accessible way
3. Take part in any follow-up investigations
This system helps ensure people have a voice and that organizations stay accountable.

Other Accessibility Laws in Canada

Even if the ACA doesn’t apply to your business, provincial laws might. Here are some examples:
- AODA – Ontario
- AMA – Manitoba
- Nova Scotia Accessibility Act
- Accessible British Columbia Act
- Newfoundland and Labrador Accessibility Act
Many of these laws include WCAG requirements and share similar goals with the ACA: to make sure everyone, regardless of ability, can fully participate in society.

Helpful Tools and Support

You don’t have to do this alone. Many resources can help:
- CASDO (Canadian Accessibility Standards Development Organization): Creates national accessibility standards
- W3C (World Wide Web Consortium): Offers WCAG guidelines and support
- Testing tools: Use screen readers, color contrast checkers, and simulators to evaluate your site
- Ongoing training: Keep your team up to date with the latest best practices
Make Accessibility a Core Part of What You Do

Complying with the ACA isn’t about checking boxes. It’s about helping all people feel seen, heard, and included—online and beyond.

You don’t need to get everything perfect overnight. But you do need to start. The ACA sets a strong foundation, and taking action now puts you on the right path.

At 216digital, we understand the technical side of accessibility—and the human side, too. Whether you need an audit, a plan, or long-term strategy, we’re ready to help.

Let’s work together to make the web a better place for everyone.

Schedule your free consultation today and take the first step toward ACA compliance.
Greg McNeil

April 29, 2025

Legal Compliance

ACA, Accessibility, ADA Website Compliance, Canada, International Accessibility Laws, Website Accessibility
How Often Should You Audit Your Website for Accessibility?
You’ve already put in the effort to make your website accessible—and that’s no small thing. But accessibility isn’t something you fix once and forget. As your site evolves, even small changes can introduce new issues. That’s where regular check-ins come in. A web accessibility audit helps you catch problems early, stay aligned with current standards, and keep your site working for everyone.

So how often should you audit your site to maintain that progress? The answer depends on what’s changing—and when. In this article, we’ll break down the key moments when an audit makes sense, the risks of letting things slide, and how ongoing monitoring can help you stay ahead.

Why Web Accessibility Audits Are Critical

A web accessibility audit reviews your website’s design, code, and content to identify barriers that could make it hard—or even impossible—for people with disabilities to use your site. These audits typically test against the Web Content Accessibility Guidelines (WCAG) standards, the ADA (Americans with Disabilities Act), and other regulations.

The risks of not auditing regularly are real for small to midsize businesses. Over the past few years, digital accessibility lawsuits have skyrocketed. In 2024 alone, more than 4,000 web accessibility lawsuits were filed under the ADA—and many of those targeted businesses that were unaware they had an issue.

The cost of defending even a small ADA lawsuit can easily reach tens of thousands of dollars, not to mention the damage to your brand’s reputation. Proactive audits help you spot and fix issues early, keeping your business protected and your customers happy.

When Should You Audit Your Website for Accessibility?

While accessibility should be baked into your website maintenance plan, certain milestones require a full web accessibility audit.

1. After a Website Redesign or Major Update

If you’ve recently rebranded, relaunched, or significantly redesigned your site, it’s critical to schedule a full accessibility audit. Even small navigation, layout, or feature changes can unintentionally introduce new barriers. Testing right after major updates ensures you catch and fix issues before customers encounter them—and before a potential lawsuit arises.

2. Before Launching New Features or Products

Rolling out a new e-commerce section? Adding a chatbot? Introducing video content or online booking? Before new features go live, a web accessibility audit should be part of your quality assurance checklist.

New code, third-party integrations, and interactive tools can create accessibility gaps. Testing pre-launch helps ensure all users can interact with the new elements, no matter what device or assistive technology they’re using.

3. Annually (at Minimum)

Even if your site hasn’t changed much, accessibility standards, best practices, and legal expectations evolve over time. Conducting a comprehensive web accessibility audit at least once a year ensures your site complies with current WCAG standards (currently WCAG 2.1 and moving toward 2.2) and applicable regulations.

Think of it like an annual checkup for your digital presence: it’s much easier and cheaper to maintain accessibility than to fix major problems down the road.

4. After User Feedback or Complaints

If a customer or visitor flags an accessibility issue, that’s a signal to audit right away—not just the problem area but the entire site. User feedback is invaluable because it often reveals real-world issues automated scans might miss. Addressing concerns quickly shows that your business takes accessibility seriously and is committed to serving all users.

5. When Laws or Guidelines Change

New accessibility laws, updates to WCAG standards, or changes in court interpretations can raise the bar for compliance. For instance, the Department of Justice recently released new guidance for web accessibility under Title II of the ADA. When legal standards shift, a fresh audit can make sure you’re aligned with the latest requirements.

Why Ongoing Monitoring Matters

While annual or event-based audits are critical, they’re not enough. Websites are dynamic—they grow, change, and update constantly. New products, marketing campaigns, and blog posts can all introduce accessibility problems over time.

That’s where ongoing accessibility monitoring comes in.

At 216digital, we developed a11y.Radar, a proactive monitoring service that continuously scans your site for accessibility issues. a11y.Radar doesn’t replace manual audits (human expertise is still key!), but it acts as an early warning system—catching errors before they snowball into bigger problems.

With a11y.Radar, you can:
- Receive real-time alerts about accessibility regressions
- Track ongoing improvements
- Maintain continuous WCAG compliance
- Reduce your risk of surprise lawsuits
This approach helps you move from a reactive stance (“fix it after a lawsuit”) to a proactive one (“prevent lawsuits by staying accessible”).

The Cost of Skipping Regular Web Accessibility Audits

Many small to midsize businesses skip regular accessibility audits because of perceived costs or time commitments. But the truth is, not auditing can cost far more.

Ignoring accessibility can lead to:
- ADA lawsuits and expensive legal settlements
- Court-ordered website remediation under tight (and expensive) deadlines
- Loss of customers who can’t use your site
- Negative publicity and damage to your brand’s reputation
- Higher remediation costs later, compared to maintaining accessibility from the start
Investing in regular audits and monitoring is like insurance for your website—and your business future.

How 216digital Can Help You Stay Compliant

At 216digital, we specialize in helping businesses of all sizes navigate the world of web accessibility with confidence. Our phased approach includes:
- Risk Mitigation Audits: A focused first-pass audit to quickly catch and fix high-risk issues.
- Real World Accessibility Audits: Deep manual testing with screen readers, keyboard-only navigation, and assistive technologies to find real-world barriers.
- Ongoing Monitoring with a11y.Radar: Continuous scanning and reporting to help you maintain compliance and stay ahead of risks.
We believe accessibility isn’t a one-time project—it’s an ongoing commitment. That’s why our services are designed to be flexible, scalable, and tailored to your business needs.

Whether starting from scratch, redesigning your website, or needing help managing compliance over time, 216digital can help you build and maintain a site that works for everyone—and protects your business simultaneously.

Keep Progress on Track with Confidence

Accessibility is never truly finished—but that’s a good thing. It means you have an opportunity to keep improving, keep welcoming, and keep your business open to everyone. Staying compliant isn’t about chasing checklists—it’s about maintaining the trust you’ve already worked hard to earn.If you’re wondering whether now is the right time for your next audit, it probably is. A quick conversation can help clarify where you stand and what steps make sense next. Schedule a free ADA accessibility briefing with 216digital, and let’s keep your site moving forward—securely, inclusively, and confidently.
Greg McNeil

April 28, 2025

Testing & Remediation

Accessibility, Accessibility Audit, Accessibility testing, automated testing, manual audit, Manual Testing, Website Accessibility
8 Must-Know Real World Accessibility Facts
Imagine your online store is polished, your marketing campaigns are humming, and the checkout button is ready for clicks—yet one out of every four visitors can’t complete a purchase because the site trips them up. They might rely on a screen reader that can’t parse your menus, or a keyboard that gets trapped in a popup. Multiply that frustration by 70 million Americans with disabilities, and the gap becomes impossible to ignore.

That gap is what we call real world accessibility—the difference between a site that merely exists and one that truly works for everyone. If you’re a busy business owner or marketing lead, you don’t need another technical lecture. You need clear facts, plain language, and a practical path forward.

The eight statistics ahead will show why accessibility isn’t optional anymore—it’s a smart move for growth, trust, and peace of mind.

1. 70 Million Adults in the U.S. Live With a Disability

Let’s start with the big one: 1 in 4 adults in the U.S. has a disability. That includes people with mobility challenges, vision or hearing loss, cognitive differences like ADHD or dyslexia, and more.

This isn’t just about permanent conditions either. Temporary disabilities—like recovering from surgery—or situational ones—like trying to use a website on a cracked phone screen—also affect how people experience your site.

Real world accessibility means your website should work for everyone, right out of the gate. If 25% of your market couldn’t open your front door, you’d fix it. The same should apply to your digital front door.

2. People With Disabilities Influence Over $7 Trillion in Spending Power

According to the Global Economics of Disability Report, people with disabilities hold $1.3 trillion in direct disposable income. When you include their families and friends who often shop with their needs in mind, that number jumps to over $7 trillion.

This isn’t a small segment. It’s a major market force.

If you’re not prioritizing real world accessibility, you’re leaving money on the table. Businesses that bake inclusion into their design often win lifelong customers—not just because it’s the right thing to do, but because it’s also smart business.

3. Accessibility Impacts Buying Decisions for the Majority of Users

Here’s something every eCommerce business should know:
- 83% of users with access needs limit their shopping to websites they know are accessible.
- 71% leave a site entirely if it’s hard to use.
Most won’t leave feedback. They’ll just disappear.

That means your site could be working against you—and you might not even realize it. Real world accessibility is tied directly to conversion rates, customer loyalty, and user trust. If your checkout form isn’t keyboard-friendly or your product descriptions aren’t screen reader accessible, you could be quietly losing sales.

4. WCAG-Compliant Sites Outperform by 50%

Websites that follow WCAG (Web Content Accessibility Guidelines) outperform competitors by up to 50%. Why? Because accessible sites are cleaner, easier to navigate, mobile-friendly, and better for SEO.

These improvements benefit everyone—not just people with disabilities. Faster load times, simpler layouts, and more intuitive design aren’t just accessibility wins—they’re usability wins.

When you take real world accessibility seriously, you’re not just avoiding issues. You’re building a stronger, more future-ready digital presence.

5. 94.8% of Homepages Are Inaccessible in 2025

WebAIM’s 2025 report found that nearly 95% of websites fail basic accessibility checks. That’s almost every homepage on the internet.

What does “inaccessible” look like in the real world?
- Buttons that don’t work with a keyboard
- Low contrast text that’s hard to read
- Forms without labels that screen readers can’t interpret
Real world accessibility problems aren’t always obvious—but they’re frustrating for users and damaging to your brand. Fixing them means fewer bounce rates, better user engagement, and a more welcoming experience for everyone.

6. eCommerce Sites Have Some of the Worst Accessibility Scores

If you’re running an online store, this one’s for you. WebAIM found these average issue counts per homepage:
- Shopify: 69.6
- WooCommerce: 75.6
- Magento: 85.4
That’s a lot of potential roadblocks for customers trying to shop.

Even popular platforms have major flaws. Real world accessibility isn’t baked into every theme or plugin—and adding new features can sometimes make things worse. The more customized your site is, the more important it is to audit for accessibility regularly.

7. Over 4,000 ADA Website Accessibility Lawsuits Were Filed in 2024

Accessibility isn’t just about user experience—it’s about legal risk, too. In 2024:
- 2,400 lawsuits were filed in federal court
- 1,600 in state courts
- 961 involved repeat defendants
That last stat is key: businesses that don’t fix issues after being sued are getting hit again.

Real world accessibility helps you stay out of the courtroom and focus on serving your customers. A proactive strategy can save you time, money, and major headaches.

8. ADA Title III Lawsuits Aren’t Slowing Down in 2025

This year, accessibility lawsuits are expected to rise. Why?
- The law currently favors plaintiffs.
- The federal government is rolling back new regulations.
- “Serial litigation” is becoming more common.
Waiting for clear rules before acting is risky. Businesses that put accessibility off are more likely to become targets. Investing in real world accessibility now protects you in the long run—and shows customers you care.

Accessibility Is a Smart Business Strategy

Let’s be honest—this stuff can feel overwhelming. You’ve got a million things on your plate already. But here’s the good news: real world accessibility doesn’t have to be perfect from day one. It just has to be in motion.

Start by learning. Then take action—small steps, big impact.

At 216digital, we believe accessibility is more than a checkbox—it’s a competitive edge. Our team combines human expertise with tools like a11y.Radar to help you identify, fix, and monitor accessibility issues—before they turn into lost sales or legal risk.

Want help getting started?
Schedule your free ADA Accessibility Briefing today, and let’s build a better web—one that works for everyone.
Greg McNeil

April 24, 2025

The Benefits of Web Accessibility, Web Accessibility Remediation

Accessibility, real world accessibility, Web Accessibility, WebAIM, Website Accessibility

What Is WCAG — and Why It Matters

Can You Get WCAG Certified? (No — and Here’s Why)

Why the Idea of Certification Still Matters

What You Can Get Instead: Real Accessibility Certifications

Real Accessibility Is About Practical Action

Run Regular Accessibility Audits

Fix High-Impact Issues First

Bake Accessibility Into Development

Publish a Public Statement

Train Your Content Team

Should You Be Chasing WCAG Certification?

Accessibility Partners Can Make the Difference

You Don’t Need a WCAG Certificate—You Need a Plan

What a False Positive Really Is

The Hidden Costs of False Positives

Time and Budget Drain

Erosion of Trust in Tools

Legal and Reputational Risks

Practical Steps to Minimize False Positives

Choose Tools Carefully

Combine Automated Testing with Manual Checks

Educate and Empower Your Team

Shift Accessibility Testing Left

Engage Accessibility Specialists

A True Positive Path Forward

How GAAD Began: A Blog Post That Sparked a Global Movement

Why GAAD Still Matters in 2025

What’s In It for Business: Real-World Upside

Six Meaningful Ways to Celebrate GAAD 2025

Share Your Story

Post on Social Media

Host an Internal Accessibility Chat

Educate Your Team

Start an Accessibility Goals List

Update Your Accessibility Statement

Looking Ahead: Building Daily Culture

Your Invitation to Take the Next Step

The Common Ground

Using aria-label: Direct and Hidden

aria-labelledby: Harness Visible Content

Picking the Right Attribute

Common Mistakes (And How to Dodge Them)

Performance and Maintenance Tips

Advanced Label Composition

Testing Your Accessible Names

Wrapping Up: Making Strategic Choices