216digital.
Web Accessibility

Phase 1
Web Remediation for Lawsuit Settlement & Prevention


Phase 2
Real-World Accessibility


a11y.Radar
Ongoing Monitoring and Maintenance


Consultation & Training

Is Your Website Vulnerable to Frivolous Lawsuits?
Get a Free Web Accessibility Audit to Learn Where You Stand
Find Out Today!

Web Design & Development

Marketing

PPC Management
Google & Social Media Ads


Professional SEO
Increase Organic Search Strength

Interested in Marketing?
Speak to an Expert about marketing opportunities for your brand to cultivate support and growth online.
Contact Us

About

Blog

Contact Us
  • How to Design Accessible Icons that Users Love

    Icons are everywhere—on mobile apps, websites, dashboards, and devices. They’re small, but they do big things. Icons help us find a menu, delete a file, or save something for later. Designers love them for good reason: they’re stylish, space-saving, and often universal. But here’s the question—are they really accessible to everyone?

    It’s easy to focus on how icons look, but what about how they function for people using screen readers, people with low vision, or anyone who relies on keyboard navigation? In this article, we’ll take a closer look at the benefits and challenges of using icons, the common accessibility mistakes, and the steps designers and developers can take to create accessible icons that improve user experience without sacrificing style.

    Why Icons Matter (Beyond Aesthetics)

    Well-designed icons help users make sense of content faster. According to research aligned with WCAG guidance, familiar icons can support users with reading or cognitive challenges by serving as helpful visual cues. A simple “trash can” icon can quickly signal delete. A “magnifying glass” screams search. When paired with labels, these accessible icons create a faster and clearer experience for all users.

    Saving Space on Smaller Screens

    Icons also shine when space is tight—especially on mobile. Instead of cramming menus or actions into text links, icons can simplify the interface and reduce visual clutter. When used thoughtfully, accessible icons help you keep things clean while making the site easier to use.

    Common Accessibility Challenges with Icons

    Ambiguity: One Icon, Many Meanings

    Icons aren’t always as clear as we think. A heart icon might mean “like,” “save,” or “favorite.” Without proper labeling, users may misinterpret its purpose. WCAG requires that all non-text elements, including icons, have text alternatives that clearly explain what they do. Accessible icons must carry meaning that’s clear—both visually and programmatically.

    Decorative Icons That Get in the Way

    Not every icon needs to be “read.” Some are purely decorative—like flourishes in a logo or background design. But if these aren’t properly hidden from screen readers, they add clutter and confusion. WCAG recommends using aria-hidden= "true" or similar methods to hide decorative icons. That way, screen reader users don’t have to sift through unnecessary details.

    Size, Contrast, and Clickability

    Icons that are too small or faint are hard to see or click—especially for users with motor or vision challenges. WCAG suggests a touch target size of at least 44×44 pixels. Icons should also meet contrast guidelines (at least a 3:1 ratio against the background). And if someone’s using a keyboard to navigate, your icons must have clear focus indicators and be easy to tab to.

    Best Practices for Creating Accessible Icons

    1. Label Every Interactive Icon

    Icons that do something—like opening a menu or submitting a form—need a clear label. You can add a visible text label, a hidden <span> for screen readers, or an aria-label attribute. For example:

    <button aria-label= "Open menu">
      <svg aria-hidden="true" width="24" height="24" role="img">
        <!-- SVG path here -->
      </svg>
    </button>

    This makes sure your accessible icons work for both sighted and non-sighted users.

    2. Hide Decorative Icons Properly

    If an icon doesn’t add meaning, it shouldn’t be read by assistive technology. Use:

    <span aria-hidden="true">
      <svg><!-- Decorative SVG --></svg>
    </span>

    Or:

    <svg role="presentation"><!-- Decorative SVG --></svg>

    This keeps screen reader output clean and focused on relevant content.

    3. Pay Attention to Size, Contrast, and Focus

    Accessible icons should be big enough to click easily and bold enough to see. Stick to WCAG’s minimum target size of 44×44 px. Use color contrast of at least 3:1 for non-text icons. And don’t forget to add a visible focus style for keyboard users—like a border or shadow:

    button:focus {
      outline: 2px solid #000;
      outline-offset: 2px;
    }

    4. Stay Consistent

    Use the same icon for the same action across your site. If a magnifying glass opens search in one place, don’t use it for zoom somewhere else. Consistency helps users feel confident in what each icon means—and that’s what accessible icons are all about.

    5. Avoid Icon Fonts and Emojis

    While they may seem handy, icon fonts can confuse screen readers. Emojis can also be read out in unexpected ways. It’s safer and more predictable to use SVG icons with proper labels.

    6. Test in the Real World

    Use tools like Lighthouse, or WAVE to catch basic issues. Then test manually: try navigating with a keyboard, check screen reader output, and validate that your icons have the right labels and focus states. Real-world testing is essential to making sure your accessible icons actually work.

    A Closer Look: Two Icon Examples

    The Right Way to Do a Menu Icon

    Let’s say you’re building a mobile menu. Instead of just throwing in a hamburger icon, here’s how to make it accessible:

    <button aria-label= "Open menu">
      <svg aria-hidden="true" width="24" height="24">
        <!-- Hamburger icon SVG path -->
      </svg>
    </button>

    With proper labeling, contrast, sizing, and keyboard focus styles, this is a perfect example of accessible icons done right.

    Clarifying a Heart Icon

    Got a heart icon to save a product? Don’t leave users guessing. Add supporting text:

    <button aria-label= "Save to favorites">
      <svg aria-hidden="true" width="24" height="24">
        <!-- Heart icon path -->
      </svg>
    </button>

    This helps screen readers speak the correct action and helps all users understand what it does.

    Looking Ahead: The Future of Icon Accessibility

    Think Global

    Icons don’t always mean the same thing across cultures. Something that makes sense in the U.S. may not be clear in Japan or Brazil. When designing accessible icons, test with a global audience if your site serves one.

    Customize and Personalize

    If you’re creating custom icons for your brand, take extra care with labeling and testing. Better yet, offer users the ability to switch between icons, text, or both—especially for key actions. It’s all about giving people choices that fit their needs.

    Final Thoughts: Make Icons That Include Everyone

    Icons are powerful little tools. They help us move faster, understand more, and make the web a little smoother. But for them to work for everyone, they need to be designed with care.

    That means using accessible icons that have clear labels, hiding decorative ones, following size and contrast rules, being consistent, and testing thoroughly. These steps don’t take away from good design—they enhance it.

    At 216digital, we work with design and development teams to review their UI patterns and create accessible experiences—icons included. If you’re ready to take the next step in making your digital spaces more inclusive, let’s talk. Schedule your ADA accessibility briefing today and let us help you turn thoughtful design into inclusive action.

    Greg McNeil

    June 26, 2025
    How-to Guides
    Accessibility, Accessible Design, ADA Compliance, Graphic Designer, How-to, Website Accessibility
  • How EAA Enforcement Works Across the EU

    If you’re hearing more about the European Accessibility Act (EAA) lately, you’re not alone—and you’re right to be paying attention. With the June 28, 2025 enforcement date around the corner, many U.S. businesses are starting to wonder: Does this apply to us? Are we at risk if we’re not in compliance?

    The short answer? Not necessarily—but that doesn’t mean you should ignore it.

    The EAA is a major development in digital accessibility law for the European Union, and while it’s not a global regulation, it can impact U.S.-based companies that offer products or services to EU customers. For others, it’s simply a signal of where global accessibility expectations are headed.

    This article breaks down what the EAA actually is, who needs to comply, how enforcement works, and how to determine whether it applies to your business. No panic, no guesswork—just the facts and a clear path forward.

    Setting the Stage: What Is the EAA?

    The European Accessibility Act (EAA) is an EU directive focused on improving digital and product accessibility for people with disabilities across member states. It’s designed to standardize accessibility expectations throughout the EU, ensuring equal access to services like banking, transportation, e-commerce, and more.

    The law goes into effect on June 28, 2025, and several EU countries are already working to align their national laws accordingly. For companies operating in the EU, this is a significant compliance milestone.

    But here’s the key point: The EAA only applies to businesses that actively do business in the European Union.

    Who the EAA Applies To—and Who It Doesn’t

    The EAA’s core goal is to eliminate digital accessibility barriers. Whether someone is shopping online, checking into a flight, reading an eBook, or using a mobile banking app, the EAA ensures people with disabilities in the EU can participate fully in everyday digital life.

    Does the EAA Apply to U.S. Businesses?

    In short: Only if you’re engaging directly with EU customers.

    The EAA is not a global requirement. It’s meant for companies that:

    • Operate physically or digitally within the EU,
    • Market or sell directly to consumers in EU countries, or
    • Offer digital services like online platforms or mobile apps in the EU marketplace.

    So, if your business has no EU offices, no EU-based clientele, and no intention to serve EU consumers, the EAA doesn’t apply to you.

    What About Small Businesses?

    Even within the EU, microenterprises—those with fewer than 10 employees and less than €2 million in annual revenue—are exempt. That’s important for U.S. startups and solopreneurs wondering if having a website puts them on the hook. It doesn’t.

    What the EAA Actually Requires

    If your organization does conduct business in the EU, here’s what compliance looks like:

    Covered Products and Services

    The EAA applies to a wide range of digital goods and services, such as:

    • Online marketplaces and e-commerce platforms
    • Mobile apps and websites
    • Digital banking interfaces and ATMs
    • Public transport booking systems
    • eBooks and reading devices
    • Ticketing machines and self-service kiosks

    Accessibility Standards

    Compliance requires aligning with EN 301 549, which references WCAG 2.1 Level AA—a familiar standard in the U.S.

    That means your content and digital tools should be:

    • Perceivable: Understandable with assistive technologies
    • Operable: Usable with various input methods like keyboards
    • Understandable: Clear, predictable layouts and instructions
    • Robust: Functional across devices and platforms

    Accessibility Statements

    EAA-compliant websites and apps must also include an accessibility statement that communicates the site’s current accessibility status, outlines any known limitations, and provides a channel for users to request support or report issues.

    How EAA Enforcement Actually Works

    EAA enforcement isn’t handled at the EU level. Instead, each member state enforces the EAA independently, with its own authority, procedures, and penalty structures. That means the experience—and consequences—can vary from country to country.

    Here are a few notable examples:

    • France: Handled by Défenseur des droits, with fines up to €250,000
    • Germany: Managed by BFIT-Bund and regional bodies; penalties from €10,000 to €500,000
    • Ireland: Overseen by the National Disability Authority; up to €60,000 in fines or imprisonment in serious cases
    • Italy: Governed by AgID; fines can reach €25,000
    • Spain: Managed by OADIS and regional authorities; penalties as high as €600,000

    A Word to Multinational Businesses

    If your business spans multiple EU countries, EAA enforcement can get complex. Each jurisdiction may interpret the directive differently, making early planning essential for smooth, consistent compliance.

    What U.S. Businesses Should Actually Do

    Now that you have a clearer picture, here’s how to assess your next steps.

    1. Evaluate Your Exposure

    Ask yourself:

    • Do you sell to or serve customers in the EU?
    • Do you offer a localized site or support EU languages?
    • Are your apps available in EU-based app stores?

    If the answer is yes, EAA compliance is likely necessary. If not, you’re likely outside its scope—but staying informed is still a wise move.

    2. Take Practical (Not Panicked) Steps

    If you do engage with the EU market, now is the time to:

    • Audit digital products for WCAG 2.1 Level AA alignment
    • Fix known accessibility issues (navigation, color contrast, labeling, etc.)
    • Publish an accessibility statement
    • Document your efforts for accountability

    And if you’re unsure where to start, bring in accessibility experts. The right support can help you avoid missteps, reduce liability, and stay aligned with country-specific EAA enforcement requirements.

    3. Remember: Accessibility Is a Business Advantage

    Even if the EAA doesn’t apply to you now, accessibility is still a smart investment. It can:

    • Broaden your customer reach
    • Improve usability and search engine performance
    • Build long-term brand trust and loyalty
    • Help you stay ahead of evolving legal and market expectations

    And in the U.S., digital accessibility remains a legal risk under the ADA. Proactive improvements made today could save you from future challenges—at home and abroad.

    Looking Ahead: Stay Aware, Not Alarmed

    The European Accessibility Act represents a shift in global digital accessibility expectations—but that doesn’t mean every U.S. business needs to overhaul its operations overnight. If your company doesn’t operate in the EU or serve EU-based customers, this law likely doesn’t apply to you.

    Still, moments like this are valuable reminders. They give forward-thinking businesses a chance to pause, evaluate, and strengthen their digital experiences—not just for compliance but for the real people who rely on accessible technology every day.

    Whether you need to take immediate steps or want to stay ahead of future regulations, the smartest move is to stay informed and be proactive. Accessibility isn’t about reacting to legal threats—it’s about building resilient, inclusive digital experiences that serve everyone, everywhere.

    Need clarity on where you stand or how to move forward? Let 216digital help you navigate accessibility with confidence and purpose.

    Greg McNeil

    June 25, 2025
    Legal Compliance
    2025, Accessibility, EAA, European Accessibility Act, Legal compliance, Website Accessibility
  • Descriptive Page Titles for Better Accessibility

    If you’ve ever had 15 tabs open at once (and let’s be honest—who hasn’t?), you know how frustrating it is to click around trying to remember which one is which. When the titles are clear, you can find what you’re looking for in a second. When they’re not, it’s a guessing game.

    For users who rely on screen readers or who live with cognitive or memory challenges, vague titles aren’t just annoying. They’re a real barrier. That’s where descriptive page titles come in. They make a huge difference in helping all users navigate the web more easily, and they support your site’s overall usability and accessibility—without requiring a major overhaul.

    Best of all, it’s one of the simplest changes you can make that still packs a serious punch. A good page title improves orientation, reduces confusion, boosts your SEO rankings, and even helps reduce legal risk under the Americans with Disabilities Act (ADA). All with a few well-chosen words.

    What WCAG 2.4.2 Actually Requires

    Under WCAG 2.4.2—a Level A requirement in the Web Content Accessibility Guidelines (WCAG)—every web page must have a title that clearly describes its topic or purpose. It’s one of the most fundamental accessibility requirements, but it’s also one of the most overlooked.

    Simply having a <title> tag isn’t enough. What’s inside that tag matters. A vague or generic title—like “Home” or “Untitled”—does little to help users understand what the page is actually about. It’s a bit like labeling all your folders “Stuff”—no one can navigate that efficiently, especially not users relying on assistive technologies.

    This is especially important for screen reader users. Page titles are often read aloud as soon as a page loads or when switching between browser tabs. That brief moment of context helps them know exactly where they are. Similarly, sighted users benefit from meaningful titles when scanning through multiple open tabs or saving bookmarks for later reference.

    Who Benefits from Descriptive Page Titles?

    The short answer? Everyone. But here’s how it really plays out for different types of users:

    • Screen reader users hear the page title as their first introduction. A vague or incorrect title can throw them off or force them to dig deeper than necessary.
    • People with cognitive or memory challenges rely on titles to quickly understand whether a page is relevant. A well-written title can prevent information overload and reduce frustration.
    • Mobility-impaired users benefit because they can avoid unnecessary clicks or key presses if the title tells them they’re on the wrong page.
    • Everyone else—yes, even those without disabilities—appreciates descriptive page titles for the sheer convenience. Clear titles make it easier to navigate tabs, scan bookmarks, and share links confidently.

    When a title says exactly what a page delivers, no one has to guess. That’s good usability—and that’s what accessibility is really about.

    Common Title Mistakes (And How to Fix Them)

    Even with the best intentions, many websites still fall into title traps. Let’s look at a few common problems:

    • Too Vague: Titles like “Home” or “Blog” don’t help much when you’re trying to tell one tab from another.
    • Reused Titles: When every blog post or account page is titled the same—like “Monthly Statement”—users lose their place quickly.
    • Doesn’t Match the Page: If your title says “Pricing,” but the page is about features or FAQs, that mismatch causes confusion.
    • Overloaded for SEO: You’ve seen these: “Best Home Trim Vinyl Windows Outdoor Accessories 2025 Guide.” They’re trying to do too much and end up helping no one.

    Better Examples

    Consider replacing generic titles with more descriptive ones. For example, swap “Blog Post” with “How to Write Descriptive Page Titles.” You might also change “Services” to “Real World Accessibility | 216digital,” or “Contact” to “Contact Us – 216digital Web Team.”

    These small edits bring clarity, build trust, and boost both accessibility and SEO

    Accessibility and SEO: They Work Together

    There’s a common myth that writing for accessibility hurts SEO—but that couldn’t be further from the truth. In fact, descriptive page titles are a perfect example of how accessibility and SEO can work in harmony.

    Search engines love pages with relevant, concise, and unique titles. So do people. That means when you follow accessibility best practices, you’re also improving your site’s visibility and user engagement.

    Tips for Great Titles

    • Keep them between 30–60 characters so they don’t get cut off in search results or browser tabs.
    • Use primary keywords naturally, not awkwardly.
    • Try using a pattern like: [Page Topic] | [Brand Name].

    So, “About” becomes “About Our Team | 216digital” and “Pricing” becomes “Website Accessibility Pricing | 216digital.”

    It’s easy to see how small tweaks can have a big payoff.

    How to Improve Your Titles—Step by Step

    Here’s a quick plan to help you get your titles in shape:

    Audit Your Site

    Use automated tools to spot missing, duplicate, or unusually long titles. But don’t stop there—manual review is key to catching vague or misleading language that tools might miss.

    Apply a Simple Template

    Keep it consistent across your site: “[Page Topic] | [Brand]” works for most needs and helps build recognition.

    Loop in Your Team

    Content creators, developers, designers, and SEO specialists should all care about good descriptive page titles. Make it a shared goal—not an afterthought.

    Add it to Your Checklist

    Whether you’re launching a new blog post, updating a product page, or doing a site redesign, reviewing the title tag should be part of the process every time.

    The Risks of Getting It Wrong

    Ignoring this part of accessibility can lead to bigger problems. WCAG 2.4.2 is part of ADA compliance, and missing or misleading titles are often among the first things flagged in accessibility audits. If you’re not in compliance, you could be vulnerable to lawsuits—and nobody wants that.

    But beyond legal risk, failing to use descriptive page titles sends the wrong message. It suggests your site wasn’t built with every user in mind. And that hurts brand trust more than you might think.

    Final Thoughts: Titles That Work for Everyone

    It’s easy to overlook something as small as a page title. But when you take a step back, you’ll see that descriptive page titles affect every part of your site—from how users find you, to how they feel while browsing, to whether they come back at all.

    This one fix can make your site more usable, more discoverable, and more inclusive—without blowing up your workflow or budget. That’s what we call a smart move.

    Ready to Take Action?

    Want help reviewing your site for accessibility wins like this one? Schedule an ADA briefing with 216digital. We’ll show you how small changes like descriptive page titles can lead to big improvements in compliance, usability, and user trust—no pressure, no hard sell.

    Let’s build a web that works for everyone—starting with the title.

    Greg McNeil

    June 18, 2025
    How-to Guides
    Accessibility, How-to, Page Titles, WCAG, WCAG Compliance, Web Accessibility, web developers, web development, Website Accessibility
  • Custom Accessibility Audits: Tailored for Your Website

    Most websites aren’t trying to be inaccessible—it just kind of happens. A few plugins here, a third-party widget there, and before you know it, people using screen readers or keyboard navigation are hitting roadblocks you didn’t even know were there.

    If you’ve ever felt unsure about where your site stands or thought, “We added a tool—so we’re probably fine,” you’re not alone. But the truth is, real accessibility takes more than a one-click solution. It takes intention, testing, and a plan. And with digital accessibility lawsuits on the rise, ignoring the gaps is more of a liability than ever.

    If staying ADA-compliant is your goal, you need more than a quick fix. You need custom accessibility audits, meaningful remediation, and a partner who can help you maintain compliance long-term.

    The Real Limitations of Automation Tools

    Automated accessibility tools are everywhere, and it’s easy to see the appeal. They promise a quick scan and some instant fixes—like adding alt text, adjusting colors, or offering a text-size toggle. It feels like progress. But these tools can only go so far.

    They often miss what really matters: how someone with a disability actually uses your site. Screen readers, keyboard navigation, and cognitive-friendly layouts aren’t things most automation can truly understand or evaluate.

    What They Miss (And Why It Matters)

    Here are a few areas where automation usually falls short:

    • Screen reader experiences: Automated tools won’t tell you if your navigation makes sense when read aloud.
    • Keyboard usability: They don’t catch when menus or popups trap users who don’t use a mouse.
    • Structural clarity: Bad heading structures or mislabeled buttons often go unnoticed.
    • Interactive elements: Modals, forms, and sliders might work visually but break down when tested for accessibility.

    Even more concerning? Courts are increasingly ruling that automation alone doesn’t meet ADA requirements. In some cases, relying on overlays without fixing underlying issues can actually increase your legal risk—especially for busy sites that handle transactions. This is why custom accessibility audits remain the gold standard for identifying real, user-impacting issues.

    Why Real Testing Still Matters

    You can’t fix what you don’t experience—and that’s the heart of manual testing. It’s not just about running a tool and checking boxes. It’s about walking through your site the way someone with a disability might.

    That means:

    • Navigating with a keyboard and nothing else.
    • Using a screen reader to browse your content.
    • Testing user flows like logging in, searching, or checking out—without assuming the user can see or use a mouse.

    The Kind of Issues Manual Testing Uncovers

    This type of testing uncovers issues that automation never will:

    • Dropdowns that don’t announce themselves
    • Buttons that lack clear, descriptive labels
    • Interactive sections that lose focus or confuse navigation
    • Forms that look fine visually but are hard to use with assistive tech

    At 216digital, we don’t just skim the surface. During custom accessibility audits, we follow real user journeys—from homepage to checkout—so we can see how the experience actually holds up. It’s not about passing a test. It’s about making sure everyone can use your site smoothly.

    What Custom Accessibility Audits Really Looks Like

    Once you know what’s broken, fixing it takes more than flipping a switch. True remediation means tailoring fixes to your site’s layout, content, and functionality—not applying a generic patch.

    That’s why we focus on changes that make a measurable difference for real users. Things like:

    • Making sure users can see where their keyboard focus is at all times
    • Adding ARIA roles and labels so screen readers can understand what’s on the page
    • Improving contrast without compromising your brand’s look

    Examples of Targeted Fixes

    We also fix the kinds of problems that create the most user friction:

    • Popups and modals that trap keyboard or screen reader users
    • Sliders or videos that move too quickly without user control

    There’s no one-size-fits-all approach. Each website is different. Each problem needs a thoughtful, code-aware fix. That’s where custom remediation stands apart—it solves the right problem in the right way.

    Keeping Accessibility on Track with a11y.Radar

    Accessibility isn’t something you do once and forget about. Websites change—new content, new plugins, new designs—and with those changes come new risks.

    That’s where our ongoing monitoring tool, a11y.Radar, makes the difference.

    It acts like a digital safety net by:

    • Running regular scans to check for new or recurring issues
    • Prioritizing problems based on what’s most important to fix first
    • Providing clear reports that your team can actually understand and act on
    • Using the same scanning methods many law firms rely on before filing lawsuits

    Stay Ahead, Don’t Fall Behind

    Think of it like maintenance for your website’s health. You wouldn’t skip oil changes for your car—and keeping your site accessible works the same way. a11y.Radar helps you stay proactive so small issues don’t turn into bigger problems later. And when paired with custom accessibility audits, you gain a complete strategy for long-term digital compliance.

    Why Visibility Increases Your Risk

    The more visible your business becomes, the more pressure there is to get accessibility right.

    In just May alone, 445 new digital accessibility lawsuits were filed in the U.S.—many aimed at online retailers, especially those using Shopify or WooCommerce. These platforms offer convenience, but often rely on templates or plugins that haven’t been fully tested for accessibility.

    The Real-World Consequences

    It’s not personal—these lawsuits are often triggered by bots scanning the web for compliance issues. If your site trips a red flag, it could end up on a law firm’s radar.

    The risks are real:

    • Expensive legal battles or settlement costs
    • Strained customer trust
    • Hits to your brand reputation
    • Increased insurance premiums

    The upside? When you invest in custom accessibility audits and monitoring, you dramatically lower your risk—and build a better experience for every user.

    Beyond Legal Advice: Why You Need Technical Support

    A good legal team can help you understand where you’re exposed. But they won’t fix your navigation, rewrite your forms, or troubleshoot your ARIA labels.

    That’s where a hands-on partner makes the difference.

    What a Technical Accessibility Partner Does

    At 216digital, we’ve supported hundreds of websites—small shops and enterprise platforms alike. Our approach is practical, technical, and built around real-life use cases. We don’t just tell you what’s wrong—we fix it, explain it, and set you up to manage accessibility long-term.

    Here’s what we bring to the table:

    • Clear developer guidance tailored to your platform
    • Integrated testing and remediation that fits into your current workflow
    • Ongoing support and monitoring after the fixes are live

    It’s not about being perfect—it’s about building lasting accessibility habits. And having a partner who helps you stay on track.

    Accessibility Isn’t Obligation—It’s Opportunity

    It’s your chance to build a brand that’s genuinely inclusive, appealing to a wider audience and avoiding costly legal pitfalls. Automation tools alone won’t get you there, but custom accessibility audits, hands-on remediation, and proactive monitoring will.

    If you’re done guessing and ready to confidently say your site is accessible, reach out to us at 216digital. We’ll clearly show you where your site stands, guide you through practical improvements, and keep accessibility effortless and ongoing. Because ultimately, making your website accessible isn’t just smart—it’s the kind of thoughtful action your customers will notice and appreciate.

    Greg McNeil

    June 17, 2025
    Testing & Remediation
    Accessibility, Accessibility Remediation, Accessibility testing, automated testing, custom accessibility audits, Manual Testing, Web Accessibility, Web Accessibility Remediation, Website Accessibility
  • Web Accessibility for Retailers Under Legal Fire

    If you’re running an online retail business, digital accessibility might not be the first thing on your to-do list—but it needs to be. In today’s eCommerce landscape, accessibility for retailers isn’t just a best practice—it’s a legal requirement and a smart business move.

    Retail websites are complex, dynamic, and frequently updated, which makes them especially vulnerable to accessibility issues. And as more people rely on online shopping to meet daily needs, the stakes are higher than ever. Lawsuits are on the rise, but more importantly, so is the expectation that your site works for everyone.

    Product carousels, filters, multi-step checkout processes, popups, modals, and embedded third-party tools all add complexity and make accessibility more difficult.

    Why Web Accessibility for Retailers Matters

    Retailers have become one of the biggest targets for digital accessibility lawsuits. In fact, in 2024 alone, 77% of all web accessibility lawsuits in the U.S. targeted online retailers—making the industry the most litigated digital sector. These lawsuits aren’t just targeting Fortune 500 brands; regional and mid-market businesses are facing legal action at an increasing rate.

    There are several reasons for this:

    Retail Websites are Dynamic And Complex

    They’re filled with product carousels, filters, multi-step checkout processes, popups, modals, and embedded third-party tools—all of which can be difficult to make accessible. Without proper structure, markup, and ARIA attributes, these elements can become unusable for people relying on screen readers or keyboard navigation.

    eCommerce Sites Are Constantly Updated

    Product pages change, promotions rotate, and new features are added regularly. These updates often introduce new accessibility problems—especially when not reviewed with accessibility in mind.

    Online Shopping is Essential

    It’s no longer a luxury; it’s how millions of people access everyday goods and services. If a website prevents someone from completing a purchase due to an accessibility barrier, it becomes a civil rights issue—legally and ethically.

    Demand Letters Are Widespread

    Each year, hundreds of thousands of demand letters are sent to businesses for digital accessibility violations. These letters signal that a company is excluding people with disabilities, and the reputational damage can be immediate.

    Legal and Technical Web Accessibility for Retailers

    Title III of the Americans with Disabilities Act (ADA)requires U.S. retailers to ensure accessibility for people with disabilities in all places of public accommodation. In today’s digital world, the courts and the Department of Justice (DOJ) have made it clear: this requirement also applies to websites—especially those that sell goods and services to the public.

    Courts and plaintiffs use the Web Content Accessibility Guidelines (WCAG) as the standard for compliance in nearly all accessibility-related lawsuits. The DOJ reaffirmed this approach in 2024, solidifying WCAG as the benchmark for evaluating whether a website is accessible.

    The Four Golden Rules of Accessibility: POUR

    At the heart of WCAG are four key principles known by the acronym POUR: Perceivable, Operable, Understandable, and Robust. These form the foundation for accessible digital experiences and help ensure your website works for everyone.

    • Perceivable – Users must be able to identify and interact with content. This includes providing text alternatives for images, captions for videos, and other sensory accommodations.
    • Operable – The site must support navigation with a keyboard, screen reader, or other assistive tools—without relying solely on a mouse.
    • Understandable – Information and functionality should be easy to comprehend and behave in expected ways to avoid confusion.
    • Robust – Content must be compatible with a wide range of current and future assistive technologies, such as screen readers or voice commands.

    And it’s not just your website. These principles should also extend to digital documents, confirmation emails, customer service interactions, and anything else a user might engage with online.

    Common Pitfalls on Retail Websites

    Retail sites face some of the most complex accessibility challenges. Here are a few issues that often trigger lawsuits:

    • Unlabeled or mislabeled form fields that prevent screen reader users from checking out.
    • Broken keyboard navigation makes it impossible for users with motor impairments to complete transactions.
    • Missing alt text on product images.
    • Low color contrast between text and backgrounds.
    • Non-dismissable modals or popups that trap users.
    • Checkout flows that break when even one component isn’t accessible.

    These barriers frequently appear when using templates, third-party plugins, or custom JavaScript that hasn’t been accessibility-tested. They can completely disrupt the buying experience for users who depend on assistive technologies. Web accessibility for retailers requires a consistent and intentional approach to prevent these obstacles from resurfacing.

    What Happens If You’re Sued

    Most lawsuits begin with a demand letter—often asking for immediate remediation and a financial settlement. If ignored, this can escalate into a federal lawsuit under the ADA or state-level laws like California’s Unruh Civil Rights Act, which allows for additional penalties.

    Settlements may cover remediation costs and legal fees, but the real damage is often reputational—especially when exclusion of disabled users becomes public knowledge.

    Even if your business wins the case, legal defense costs are high. And if your site remains non-compliant, you may be targeted again. With web accessibility for retailers, prevention is significantly less costly than a reactive legal defense.

    A Proactive Plan for Retailers

    Accessibility isn’t a one-time fix. It’s an ongoing strategy. Here’s how to start with accessibility for retailers:

    1. Start with an Audit

    Use automated tools like Lighthouse or WAVE for a quick scan. But don’t stop there—manual testing is essential for identifying real-world usability barriers.

    2. Fix Key Areas First

    Prioritize your homepage, product pages, cart, and checkout. Make sure form fields are labeled, keyboard navigation works, and screen readers can read your content.

    3. Address Dynamic Elements

    Focus on complex components—like popups, modals, filters, and third-party integrations—that often create the biggest challenges. Use semantic markup and ARIA attributes to support assistive tech.

    4. Monitor Continuously

    Your site changes frequently. Build accessibility checks into your update process so new features don’t break usability, or use a monitoring service like a11y.Radar.

    5. Train Your Team

    Give your developers, content editors, and marketing teams the knowledge they need to create inclusive content from the start.

    6. Consider Outside Help

    Accessibility is nuanced. A qualified team can help you get it right—and keep it that way.

    Retailers: Don’t Let Accessibility Be an Afterthought

    Web accessibility for retailers is no longer optional. It’s central to building a sustainable, inclusive, and legally safe business. In a digital environment where over 30% of the top 500 eCommerce retailers were sued last year, doing nothing is no longer a risk—it’s a liability.

    But there’s a real upside, too. Accessibility leads to better experiences, broader audiences, stronger SEO, and a more trusted brand.

    Start now. Audit your site. Fix the gaps. Train your team. Partner with experts. Turn accessibility from a compliance headache into a strategic advantage.

    Need Help Making Your Retail Site Accessible?

    216digital offers full audits, real-world testing, and proactive monitoring to ensure your site meets WCAG standards and stays lawsuit-resistant. Let’s make your eCommerce experience inclusive—and legally safe—from day one.

    Greg McNeil

    June 11, 2025
    Legal Compliance
    Accessibility, ADA Compliance, ADA Lawsuit, ecommerce website, Retail, WCAG, Web Accessibility, Website Accessibility
  • WordPress Accessibility: Common Pitfalls & Fixes

    WordPress gives developers a head start with accessibility—but it’s just that: a start. While the platform includes solid foundations like semantic markup and keyboard-friendly admin features, building an experience that works for everyone still requires thoughtful decisions on our part. As developers, we’re in a unique position to go beyond the basics, spotting the small oversights that can create big barriers for users.

    In this guide, we’ll walk through some of the most common accessibility missteps we see in WordPress projects—along with practical fixes you can implement right away. Whether you’re refactoring an old theme or launching something new, these insights are meant to help you create experiences that are not just compliant, but genuinely inclusive.

    Misuse of Heading Structures for Visual Styling

    It’s easy to reach for <h2> or <h3> tags to style text because they’re built into most WordPress themes with bold and larger font sizes. But when headings are used purely for visual emphasis—not structure—you end up distorting the page’s semantic outline.

    Why It Matters

    Screen reader users often rely on heading navigation to scan and jump between sections. If headings are skipped, out of order, or misused, the page becomes harder to understand, and key content may get missed entirely.

    How to Fix It

    • Use CSS for Styling: Apply styles using classes or inline styles, not heading tags. In Gutenberg, you can use blocks with custom styles or reusable blocks instead of jumping heading levels.
    • Follow a Logical Heading Hierarchy: Begin with one <h1> per page (usually the title), then use <h2> for top-level sections, <h3> for subsections, and so on.
    • Audit Your Work: Use tools like WAVE or the Google Lighthouse Accessibility Report to evaluate your heading structure and flag potential misuses before they go live.

    Overreliance on Theme Defaults for Color Contrast

    Many developers trust their WordPress theme’s default color scheme to do the heavy lifting—but while a palette may look good visually, it doesn’t mean it’s accessible. Default colors often fail to meetWCAG 2.1 AA standards, especially for body text and buttons.

    Accessibility Risk

    Poor color contrast is a major barrier for users with low vision or color blindness. If your text blends into the background, you’re excluding readers—sometimes without realizing it.

    Practical Fixes

    • Test Contrast Ratios: Use WebAIM’s Contrast Checker or the Color Contrast Analyzer to validate text against its background.
    • Override Theme Defaults: Most modern themes offer customization options via the Customizer or Full Site Editing. Make small adjustments—lighten text, darken backgrounds—to meet or exceed the 4.5:1 minimum contrast ratio.
    • Offer User Controls: Consider giving users the ability to switch to high-contrast mode with plugins like “WP Accessibility.” This gives more control to your users while improving inclusivity.

    Improper List Markup Practices

    It’s not unusual to see developers create the appearance of a list using <div> tags, line breaks, or other non-semantic methods—especially in custom blocks or page builders commonly used in WordPress.

    Why It’s a Problem

    Screen readers rely on semantic tags like <ul>, <ol>, and <li> to announce that a list exists, how many items are in it, and how items relate to each other. Without this structure, users lose context.

    Best Practices

    • Use Native List Markup: If it’s a list—code it as a list. Use <ul> for unordered lists and <ol> for ordered ones. Wrap each list item in <li>.
    • Handle Nesting Thoughtfully: For sub-lists, nest another <ul> or <ol> inside an <li>. Screen readers will announce the nested structure properly.
    • Test Your Output: Run accessibility audits or inspect the DOM to ensure list structures are coded semantically, especially when using custom Gutenberg blocks or page builders.

    Neglecting Contextual Relevance in Alt Text

    WordPress auto-generates alt text from image file names if authors don’t supply one. That’s how you end up with images labeled “IMG_4829.jpg”—which isn’t helpful to anyone.

    Why It Matters

    Alt text should describe why the image is there, not just what it looks like. If the image provides important context, instructions, or emotion, a generic label fails users who rely on screen readers.

    What Developers Can Do

    • Write Purpose-Driven Alt Text: If the image is showing a concept, outcome, or step in a process, describe that context directly. For example, “Screenshot of the plugin settings menu with Accessibility Mode enabled.”
    • Avoid Phrases Like “Image of…” Screen readers already announce the presence of an image. Jump straight into the relevant description.
    • Use Empty Alt for Decorative Images: For visuals that are purely aesthetic and add no informational value, use alt="" so assistive tech knows to skip it entirely.

    Overuse and Misapplication of ARIA Attributes

    ARIA is a powerful toolset—but like any tool, misuse can cause more harm than good. Adding roles and attributes without understanding their implications can break screen reader behavior or clutter the accessibility tree.

    The Real Cost

    Improper ARIA use can confuse assistive technologies, interfere with default behaviors, and even make components harder—not easier—to use. Overengineering is just as dangerous as under-engineering.

    Smarter ARIA Use

    • Favor Native HTML First: If you’re building a checkbox, <input type="checkbox"> with an associated <label> is far more reliable than using a <div> with ARIA roles and states.
    • Use ARIA Only When Required: If you’re building a custom interactive widget (like a tabbed interface or menu), consult the ARIA Authoring Practices Guide. Choose correct roles and manage keyboard interactions accordingly.
    • Test Your Implementation: Use screen readers like NVDA or VoiceOver to verify that ARIA is behaving as expected. Pay attention to focus, announcements, and interaction patterns.

    Overlooking Keyboard Navigation and Focus Management

    Many developers unintentionally design for mouse users first. But for users relying on keyboards—whether due to preference, disability, or temporary injury—keyboard accessibility is critical.

    Key Accessibility Concerns

    • No Visible Focus Indicators: Removing browser outlines with outline: none; without providing alternatives leaves users lost.
    • Custom Components Not Keyboard-Aware: Modals, sliders, dropdowns, and carousels built from scratch often lack proper keyboard event handling and focus management.

    Developer-Friendly Fixes

    • Ensure Focus Visibility: Style focused elements clearly using CSS, like :focus { outline: 2px solid #000; }. Customize this to match your theme, but don’t remove it entirely.
    • Handle Keyboard Events: For custom components, add keydown or keyup listeners to handle Enter, Escape, and Arrow keys appropriately. Don’t rely on click events alone.
    • Do Keyboard-Only Testing: Regularly test your site using only the keyboard. Tab through each interactive element and verify focus moves logically, without skipping important controls.

    What True Accessibility Looks Like in WordPress

    Accessibility isn’t a checklist—it’s a mindset. When we write clean, semantic code, ensure visual clarity, and support every way a user might interact with our sites, we’re not just doing right by WCAG—we’re doing right by our users. The real goal is to build experiences that work for everyone, without assumptions about how people navigate the web.

    As WordPress developers, we have powerful tools and a vibrant ecosystem at our disposal. Let’s use them with care and intention. Keep testing, stay curious, and don’t hesitate to dig deeper. And if you’re looking to strengthen your accessibility efforts, 216digital offers ADA compliance briefings tailored to development teams. We’re here to support your work—because inclusive development is better development.

    Greg McNeil

    June 10, 2025
    How-to Guides, Legal Compliance
    Accessibility, How-to, WCAG, Web Accessibility, web developers, web development, Website Accessibility, WordPress
  • Are Accessible Websites More Expensive to Develop?

    Let’s get one thing out of the way: making your website accessible does not mean doubling your budget or dragging out your timeline. One of the biggest misconceptions we hear from clients is that accessible websites are more expensive to build. But when done right, accessibility isn’t some extra layer you slap on later—it’s a smarter way to build from the beginning.

    Accessibility isn’t about adding bells and whistles. It’s about giving everyone a fair shot at using your site—no matter how they access it. And when accessibility is baked into your planning, design, and development phases, it actually saves you money. On the flip side, skipping it now often leads to expensive fixes, rework, or even legal issues later.

    Bottom line: accessible websites aren’t more expensive to develop—inaccessible ones are.

    What Accessibility Actually Requires

    If you’re picturing accessibility as a mountain of custom features and complicated coding, let’s pump the brakes. Most accessibility best practices are about making smarter choices early in the process, not reinventing the wheel.

    Let’s look at a few low-effort, high-impact things your team can do:

    • Add alternative (alt) text as you upload images. It takes seconds and provides screen readers with essential context.
    • Use semantic HTML (like proper headings, lists, and buttons) instead of just styling with divs and spans.
    • Structure navigation so users can tab through with a keyboard.
    • Check your color contrast in early design stages—this small choice determines readability for millions of users.

    Accessibility isn’t about building entirely new tools. It’s about ensuring your site plays nicely with existing assistive technologies—like screen readers, screen magnifiers, or voice navigation tools.

    That means you don’t have to build special versions of your site for users with disabilities. You just need to support the way they already navigate the web.

    Building Accessibility from the Ground Up Saves Time and Money

    Now here’s where the real costs come in: retrofitting. When accessibility isn’t part of the original plan, fixing issues after launch becomes much more expensive.

    Let’s say you skipped writing alt text during image uploads. Going back to write descriptions for 1,000+ images after the fact? That’s hours—if not weeks—of work.

    Or maybe you used complex JavaScript widgets without thinking about keyboard access. Retrofitting those components to be screen reader-friendly may mean rewriting large sections of your code.

    In other words, fixing inaccessible websites costs more than doing it right the first time. And those fixes often introduce technical debt—clunky workarounds, inconsistent updates, and ongoing maintenance headaches.

    Accessible websites, when built with care from the start, are easier to update, scale, and maintain. They’re leaner, cleaner, and future-proof.

    Accessibility Supports Other Core Business Goals

    Accessibility isn’t just about doing the right thing—it’s also good business.

    Search Engine Optimization (SEO)

    Search engines love accessible sites. Why? Because many accessibility best practices—like using descriptive alt text, heading tags, and semantic HTML—also help search engines understand and index your content.

    Performance and Usability

    Accessible websites tend to have faster load times and cleaner code, which improves the overall user experience. Mobile users, for example, benefit from accessible design as much as someone using a screen reader.

    Security and Stability

    Accessible forms often rely on well-structured HTML and simple interactions rather than fragile JavaScript plugins. This makes your site more stable and secure, reducing the likelihood of bugs or failures.

    In short, accessibility supports the same goals that developers, designers, marketers, and business owners already care about: visibility, usability, and reliability.

    The Real Risk: Legal Liability and Missed Market Potential

    Now let’s talk about the elephant in the room: lawsuits.

    Accessibility-related lawsuits have been on the rise for years—especially under ADA Title III, which covers websites as places of public accommodation. And it’s not just the big guys being targeted. Small and midsize businesses are increasingly in the crosshairs.

    Worse, many businesses try to cut corners with accessibility overlays or plugins. These tools promise instant compliance but often fall short of legal standards like WCAG (Web Content Accessibility Guidelines). Relying on them can actually increase your legal risk.

    And beyond compliance? Let’s not ignore the massive untapped audience:

    • 1 in 4 U.S. adults lives with a disability.
    • Older adults, one of the fastest-growing groups of online shoppers, benefit from larger text, clearer navigation, and reduced motion.
    • Consumers care—more people are making buying decisions based on brand values like inclusivity and social responsibility.

    An accessible website isn’t just a shield against lawsuits. It’s a magnet for customers you might otherwise miss entirely.

    Smart Accessibility Decisions by Role

    No matter your role on a digital team, you can make choices that support accessible websites from the beginning.

    For Designers

    • Choose high-contrast color schemes.
    • Use legible fonts with scalable sizes.
    • Structure content with a clear visual hierarchy.
    • Design for flexibility—not everyone uses a mouse or touchscreen.

    For Developers

    Use semantic HTML for structure.

    • Make sure all interactive elements work with a keyboard.
    • Don’t overuse ARIA—follow best practices and use it only when necessary.

    For Content Creators

    • Write in plain, easy-to-understand language.
    • Make sure your links say where they go (“Read our pricing guide,” not just “Click here”).
    • Use headings and lists to break up content.

    For Project Managers

    • Treat accessibility like you would security or performance. It’s not optional—it’s critical.
    • Schedule accessibility testing early and often, not just at the end.
    • Work accessibility into every sprint, deliverable, and stakeholder review.

    Accessibility is everyone’s job—and it’s much easier when it’s a shared priority from the beginning.

    Accessibility as an Investment, Not a Line Item

    Let’s reframe the conversation.

    Accessibility isn’t just a cost on your project spreadsheet. It’s a long-term investment in your brand, your user experience, and your operational efficiency.

    Here’s what you gain:

    • Simpler redesigns: Sites built on semantic, accessible foundations are easier to rebuild or re-theme.
    • Better customer experiences: More people can use your site with ease—and they’ll remember it.
    • Improved trust: Customers, partners, and regulators alike see accessible websites as a sign of responsibility and care.

    Even the W3C, the global standards organization behind WCAG, notes that accessible websites “often work better for everyone” and “improve the user experience across devices.”

    At 216digital, we’ve seen it firsthand—companies that build accessibly from the start end up with stronger, leaner, and more successful digital platforms.

    Make Accessibility a Strategic Priority

    So, are accessible websites more expensive to develop?

    Not if you do it right.

    Integrating accessibility from the beginning is faster, cheaper, and more effective than fixing it later. It supports your other business goals, opens up new markets, and protects you from legal risk.

    Inaccessible websites may cost less upfront—but they cost far more in the long run.

    If you’re planning a redesign or wondering where your current site stands, scheduling an ADA accessibility briefing with 216digital is a smart, low-commitment first step. We’ll help you assess your current risk, prioritize improvements, and put you on the path to building more inclusive digital experiences.

    Because accessibility isn’t an extra—it’s just smart business.

    Greg McNeil

    June 9, 2025
    Testing & Remediation
    Accessibility, Accessibility Remediation, cost, Web Accessibility Remediation, Website Accessibility
  • ARIA Alert 101: Loud, Clear, and Accessible

    If you’ve built interactive web apps, you know how crucial timely feedback is for a good user experience. But here’s something developers often overlook: what about users who rely on assistive technologies like screen readers? For them, getting real-time notifications isn’t just convenient—it’s essential. That’s exactly why understanding how to use an ARIA alert matters.

    This guide breaks down what ARIA alerts are, how they work, where they shine, and how to implement them correctly—without overwhelming users or creating redundant announcements.

    What Exactly Is an ARIA Alert?

    An ARIA alert is your app’s way of tapping a screen reader user on the shoulder. By using role="alert", you’re signaling that the content inside that element is critical and should be announced immediately—without needing to move focus or interaction.

    Technically, role="alert" behaves the same as setting aria-live="assertive" and aria-atomic="true". That means:

    • The content update will be read aloud right away.
    • The entire updated region will be announced, not just the changed portion.

    Use it when urgency matters—like an error message or a warning about a session timeout.

    How ARIA Alerts Actually Work (And Why They Can Be Tricky)

    For an ARIA alert to trigger, it must announce a change. If you statically load a message with no updates, nothing will happen—even if you’ve assigned role="alert".

    Here’s the trick: the alert container must exist in the DOM when the page loads, and its content must change dynamically. You can do this by:

    • Inserting new text into the container.
    • Revealing text that was previously hidden with CSS (e.g., display: none → display: block).

    A reliable pattern is to preload an empty alert container, then inject or unhide content as needed. This ensures assistive tech is “watching” the region.

    Real-World Scenarios for Using ARIA Alerts

    Let’s look at some common, effective use cases:

    • Form validation: “Oops! Please enter a valid email.”
    • Session timeouts: “You’ll be logged out in 1 minute.”
    • Connection issues: “Unable to save changes—check your connection.”

    Here’s an updated practical implementation using best practices:

    <div role="alert" aria-live="assertive" aria-atomic="true" id="email-alert"></div>
    <form id="contactForm">
      <label for="email">Email:</label>
      <input type="email" id="email-input" placeholder="Enter email">
      <button type="submit" onclick="validateEmail(event)">Submit</button>
    </form>
    <script>
    function validateEmail(event) {
      event.preventDefault();
      const email = document.getElementById('email-input').value;
      const alertBox = document.getElementById('email-alert');
      alertBox.textContent = ''; // Clear previous message
      if (!email.includes('@')) {
        // Trigger update
        alertBox.textContent = 'Please provide a valid email address.';
      }
    }
    </script>

    Pro tip: Clearing the alert content first helps some screen readers recognize the change reliably.

    alert vs. alertdialog: Know the Difference

    Use role="alert" for passive, immediate notifications that require no interaction. But if your message needs a user response—like confirming an action or acknowledging a warning—role="alertdialog" is a better fit.

    It shifts focus into the alert and keeps the user there until they respond—perfect for time-sensitive prompts.

    When Another Role Fits Better

    ARIA alerts aren’t the only live region role. Use the right tool for the right job:

    • Use role="status" for passive, non-urgent updates, such as “Settings saved.”
    • When presenting chat logs or continuously updating feeds, apply role="log".
    • Countdowns or ticking clocks are best served with role="timer".
    • For moving text like stock tickers or news crawls, assign role="marquee".

    This prevents alert fatigue and keeps your UI meaningful and calm.

    Best Practices for ARIA Alerts

    To ensure your ARIA alert implementation actually helps users, keep these principles in mind:

    • Avoid using aria-live="assertive" on top of role="alert" — it’s redundant and may cause double announcements.
    • Don’t assign role="alert" to the trigger (like a button); apply it to the message container.
    • Avoid focusing the alert — screen readers will announce it automatically.
    • Leave the container empty at first — content must be injected or toggled dynamically to trigger an announcement.

    Here’s an example using a hidden alert message:

    <div role="alert">
      <span id="error-message" style="display:none; color:red;">Please provide a valid email address.</span>
    </div>
    <script>
    function submitForm(event) {
      event.preventDefault();
      const emailField = document.getElementById('email');
      const errorMessage = document.getElementById('error-message');
      if (!emailField.value || !emailField.value.includes('@')) {
        errorMessage.style.display = 'block';
      } else {
        errorMessage.style.display = 'none';
        alert('Form submitted successfully');
      }
    }
    </script>

    Common Pitfalls (and How to Fix Them)

    • Too many alerts: It’s tempting to ARIA-ify everything, but overusing alerts overwhelms users. Use sparingly and meaningfully.
    • Alerts that vanish too quickly: Follow WCAG 2.2.3 (AAA) recommendations and give users enough time to absorb information—especially at slower screen reader speeds.
    • Missing initial DOM presence: Screen readers may not monitor the alert region if developers add it after the page loads and it wasn’t in the initial DOM.
    • Static content: No matter the role, alerts only fire when content updates. Don’t forget to trigger a change—whether inserting, revealing, or replacing content.

    Advanced Tips to Polish Your ARIA Alerts

    Reuse One Container

    Don’t overcomplicate things with multiple regions. Instead, keep a single reusable alert container:

    const alertContainer = document.getElementById('reusable-alert');
    alertContainer.textContent = '';
    setTimeout(() => {
      alertContainer.textContent = 'Your session will expire soon!';
    }, 50);

    The slight delay ensures screen readers detect the change.

    Hidden Alerts for Assistive Tech Only

    Sometimes, users with screen readers need information that sighted users don’t. You can use visually hidden alerts to serve that audience without affecting your UI:

    <div role="alert" class="visually-hidden">
      Background task completed successfully.
    </div>

    This preserves visual clarity while maintaining inclusivity.

    Testing: Manual Beats Automated

    While tools like Lighthouse are helpful, automated testing can’t catch everything. To verify ARIA alert functionality:

    • Use screen readers directly (NVDA, JAWS, VoiceOver).
    • Test updates dynamically—don’t rely on static behavior.
    • Confirm timing, visibility, and repeatability.

    Get feedback from real users whenever possible.

    Make Critical Updates Count With ARIA Alerts

    An ARIA alert isn’t just a technical fix—it’s a way to respect your users’ need for timely, clear communication. When implemented well, it’s like adding a layer of empathy to your UI. You’re saying, “Hey, I’ve got your back—even if you can’t see what’s on the screen.”

    If you’re unsure whether your alerts are firing at the right moments—or want expert help ensuring your digital experience is accessible—connect with the team at 216digital. We offer accessibility audits, developer guidance, and hands-on remediation services tailored to your site.

    Let’s make accessibility loud, clear, and effective—together.

    Greg McNeil

    June 5, 2025
    How-to Guides
    Accessibility, ARIA, ARIA alert, How-to, web developers, web development, Website Accessibility
  • Law Firms Aren’t Built for Accessibility Remediation Services

    When a demand letter lands in your inbox, or an ADA-related lawsuit hits your desk, your first thought might be to call a lawyer. That’s a natural reaction—after all, legal issues usually call for legal help.

    But here’s where things get a little more complicated: if the problem is your website’s accessibility, then legal advice alone won’t fix it. And that’s where many businesses take a wrong turn. Legal teams can guide you through the paperwork, but they’re rarely the ones who dig into your code, address the real barriers, or help you prevent the next lawsuit.

    This article walks you through why relying on a law firm to handle accessibility remediation services might not be the best move—and what a smarter, more effective approach looks like.

    The Problem: Law Firms Handle Lawsuits—Not Code

    Let’s be clear—attorneys have an important role. If you’ve received a demand letter or lawsuit, they can help you respond, negotiate, or represent you in court. But legal involvement doesn’t make the accessibility problem go away. The root issue—your website not working for people with disabilities—still remains. And it’s that issue that continues to carry legal and reputational risk.

    Most law firms don’t have in-house technical teams. No developers, no certified accessibility experts, no usability testers. So what happens? They either outsource the actual accessibility remediation services to third-party vendors (often charging a premium along the way) or provide high-level reports filled with checklists that leave your dev team guessing at what to do next.

    That means you’re still on the hook for the real work—and possibly paying more for it.

    Hidden Risk #1: You’ll Pay More for Less

    Law firms typically charge by the hour, which makes sense for legal tasks like reviewing contracts or negotiating settlements. But when they apply those same rates to accessibility-related work—such as interpreting WCAG guidelines, coordinating with vendors, or reviewing audit summaries—it turns into a costly game of telephone.

    You end up paying for layers of administrative overhead that slow down progress and don’t actually improve your website.

    Worse, you might not even realize where the money is going. Legal fees can pile up quickly without producing the tangible results your business actually needs: a compliant, accessible, functional website. For small to mid-size organizations trying to manage both compliance and budget, this model is hard to justify.

    Hidden Risk #2: The Fixes May Not Be Complete

    Fixing accessibility isn’t about running a quick scan and addressing a handful of errors. Real remediation requires technical precision, contextual judgment, and manual testing—especially with screen readers and keyboard navigation. It involves understanding how accessibility issues present in code and how they affect the user experience for people with different disabilities.

    Many law firms don’t have the tools—or the trained personnel—to go that deep. And their vendor partners often lean heavily on automated tools that only catch surface-level issues.

    Here’s what that kind of partial remediation can miss:

    • Form fields without accessible labels
    • Improper heading structures that confuse screen readers
    • Modal windows that can’t be closed without a mouse
    • Buttons or links that don’t receive keyboard focus
    • Dynamic content changes that don’t alert assistive technologies

    These aren’t fringe cases—they’re exactly the kinds of issues that trigger lawsuits. Unfortunately, teams often overlook them when legal experts, rather than technical specialists, lead accessibility remediation efforts.

    Hidden Risk #3: No Plan for the Long Term

    Even if your legal team manages to patch things up for now, accessibility isn’t a one-and-done situation. Websites evolve. New content is added. Platforms update. If you don’t have an ongoing plan, you risk falling out of compliance all over again—and landing back in legal trouble.

    Law firms are built for casework, not for long-term technical oversight. Most won’t offer monitoring services, provide training for your content team, or stay engaged as your digital properties change over time. Without a partner who understands how to maintain accessibility remediation services, you’re left exposed.

    That’s why sustainable compliance calls for a proactive strategy—one that goes beyond legal checkboxes and focuses on real-world usability, continuous improvement, and future-proofing your site.

    What Proper Accessibility Remediation Services Look Like

    To address ADA compliance issues the right way, you need more than legal advice—you need a full-service accessibility team that knows how to diagnose, prioritize, and implement lasting solutions.

    Here’s what effective accessibility remediation services typically involve:

    1. In-Depth Accessibility Audit

    Experienced accessibility professionals start by reviewing your site against WCAG 2.1 A/AA standards using both automated and manual testing. This ensures nothing gets missed. A proper audit covers the following:

    • Screen reader testing using tools like NVDA, JAWS, or VoiceOver
    • Keyboard-only navigation analysis
    • Color contrast checks
    • Semantic HTML review
    • ARIA role validation for dynamic content

    It’s this level of testing that uncovers real usability barriers.

    2. A Clear, Actionable Roadmap

    Instead of a vague checklist, a solid remediation team will provide a prioritized list of issues, each translated into plain language with clear technical recommendations. The goal is to make it easy for developers to understand what needs to be fixed—and how.

    3. Code-Level Fixes

    This is the heart of remediation. A professional team doesn’t just point out problems—they roll up their sleeves and solve them. That includes adjusting templates, improving focus states, rewriting inaccessible components, and ensuring your code structure supports screen readers and keyboard navigation.

    It’s hands-on work—and it requires skilled front-end developers who understand both accessibility and UX.

    4. Real-World Usability Testing

    After you make changes, your work isn’t done. Test the updated site again—this time in real-world scenarios using assistive technologies. This step confirms that your remediation efforts actually work for the people they’re designed to support.

    5. Documentation & Legal Support

    While not a substitute for a legal team, many remediation partners provide helpful documentation—such as accessibility statements, conformance reports (like VPATs), and audit results—that demonstrate your organization’s commitment to accessibility. These materials can also support your response if you’re facing legal scrutiny.

    6. Ongoing Monitoring

    Even after remediation, your site should be monitored regularly. A good partner will offer scanning tools like a11y.Radar for testing and alerts to catch issues early—before they turn into compliance risks.

    Why Accessibility Professionals Are the Better Fit

    Accessibility specialists solve the actual problem: they make websites usable for people with disabilities. They work closely with your development, design, and content teams to create solutions that align with your brand, support your UX goals, and meet compliance requirements.

    Unlike law firms, accessibility pros don’t just help you react—they help you prepare. Their job is to prevent problems, not just manage them after the fact.

    They bring technical knowledge, lived user experience insights, and a collaborative mindset to the table. That’s how you get lasting results—not just legal coverage, but a stronger, more inclusive digital presence.

    Conclusion: The Smart Path to Lasting Compliance

    If you’re navigating legal pressure because of an inaccessible website, it’s important to act quickly—but also wisely. Legal teams play a role, yes, but true ADA compliance requires more than legal documents and advice. It takes technical expertise, accessibility remediation services, and a long-term plan that goes beyond checking boxes.

    The right partner doesn’t just help you respond to a lawsuit—they help you prevent the next one by making your website genuinely usable for everyone. That means fewer legal risks, stronger user trust, and a better experience across the board.

    At 216digital, we specialize in real solutions—not just legal responses. From WCAG audits and code-level fixes to usability testing and ongoing monitoring, we help you build and maintain a site that works for everyone.

    Schedule an ADA briefing with our accessibility team today to get clear, honest guidance on what your site needs, what’s at risk, and how to move forward confidently. Let’s make your compliance efforts count—for your users and your business.

    Greg McNeil

    June 4, 2025
    Legal Compliance
    Accessibility, Accessibility Remediation, Accessibility testing, ADA Compliance, WCAG, Web Accessibility, Web Accessibility Remediation, Website Accessibility
  • Court Ruling Confirms ADA Title III Covers Websites

    As the boundaries between physical and digital business continue to blur, courts are stepping in to clarify what inclusion really means online. One recent ruling, Frost v. Lion Brand Yarn Company, brings that conversation into focus. In February 2025, a Minnesota federal judge ruled that websites qualify as places of public accommodation under ADA Title III. This decision supports what many in the digital and legal communities have long believed: accessibility online deserves consistent attention. While it doesn’t resolve every legal question, it strengthens the case for making digital inclusion part of a responsible business approach.

    Frost v. Lion Brand Yarn Company Case

    In Frost v. Lion Brand Yarn Company, Clarence and Tammy Frost—both legally blind—alleged that the company’s website was inaccessible to screen reader users. They argued this violated ADA Title III, which prohibits discrimination based on disability in places of public accommodation.

    Lion Brand Yarn asked the court to dismiss the case, claiming that its website wasn’t a physical place and therefore didn’t fall under the scope of the ADA.

    Court Decision and ADA Title III Interpretation

    On February 6, 2025, U.S. District Judge Katherine Menendez denied the motion to dismiss. Her decision stated that a website can, in fact, be considered a place of public accommodation under ADA Title III. She emphasized the law’s broad intent and noted that excluding digital spaces would limit access in today’s online world.

    Legal Reasoning Behind ADA Title III Decision

    Judge Menendez’s ruling follows a growing trend in how courts interpret the ADA. Even though the law was written before websites existed, many judges now recognize that its goals—ensuring equal access—apply in digital spaces, too.

    The court explained that ignoring websites under ADA Title III would go against the law’s purpose. If businesses offer goods and services online, people with disabilities must have equal access to those experiences.

    Broader Implications of ADA Title III in Digital Accessibility

    This case contributes to the growing conversation about whether ADA Title III covers digital platforms.Some courts have said yes, others no—but momentum is building toward broader interpretation. More judges, and the Department of Justice, are saying that websites count.

    By viewing digital platforms as essential for communication and commerce, this ruling helps make the case that online inclusion is part of federal disability rights.

    The Legal Shift Toward Website Accessibility Under ADA Title III

    The Minnesota decision supports what many businesses and advocates have been saying: websites need to be accessible. While there’s still legal gray area, the trend is clear—courts are treating digital inaccessibility more seriously.

    Congress didn’t limit ADA Title III to physical places, and courts are using that flexibility to apply it to today’s technology. With websites acting as digital storefronts, accessibility is increasingly expected as a baseline.

    Agencies like the Department of Justice also support this view. As websites become central to how businesses operate, they must be designed with accessibility in mind.

    Actionable Steps for Compliance with ADA Title III

    If your business operates online, now is the time to prioritize accessibility. Here are some practical, proven steps to move in the right direction:

    Conduct Accessibility Audits

    Use a mix of automated tools and manual checks to find and fix barriers that prevent access.

    Implement WCAG Guidelines

    Follow the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA to ensure your content is usable for people with disabilities.

    Train Development Teams

    Make sure developers and designers understand accessibility best practices from the start.

    Engage Users with Disabilities

    Include people with disabilities in your testing process—they offer insights that no automated tool can.

    Maintain Ongoing Compliance

    Use tools like a11y.Radar to monitor your site regularly and stay on top of new issues. Accessibility isn’t a one-time fix—it’s ongoing.

    Erkan v. David A. Hidalgo, MD, P.C. provides one example of proactive compliance. There, a judge acknowledged that steps taken to address accessibility concerns helped mitigate legal risk. It’s a good reminder that prevention is always better than response.

    Implications of ADA Title III for Businesses

    This ruling matters most for businesses that sell or provide services online. Failing to address accessibility could lead to legal challenges, negative press, and missed opportunities to connect with customers.

    On the flip side, investing in accessibility shows you value all your users. It can improve user experience, increase brand trust, and even open up new markets.

    The Time to Act is Now

    The Minnesota ruling strengthens the growing understanding that websites are part of the ADA Title III conversation. While not every legal question is settled, businesses have more reason than ever to take accessibility seriously.

    If your website serves the public, this case is a signal to act. Not because you’re forced to—but because it’s the right thing to do.

    To learn more about how to proactively address ADA conformance, schedule an ADA briefing with 216digital today. Our team of accessibility experts is ready to guide your business through every step of the process, helping you stay ahead of evolving legal standards while building a more inclusive web for everyone.

    Greg McNeil

    May 23, 2025
    Legal Compliance
    Accessibility, ADA Compliance, ADA Lawsuits, ADA Title III, Title III, Website Accessibility
1 2 3 … 17
Next Page
216digital Scanning Tool

Audit Your Website for Free

Find Out if Your Website is WCAG & ADA Compliant













    216digital Logo

    Our team is full of expert professionals in Web Accessibility Remediation, eCommerce Design & Development, and Marketing – ready to help you reach your goals and thrive in a competitive marketplace. 

    216 Digital, Inc. BBB Business Review

    Get in Touch

    2208 E Enterprise Pkwy
    Twinsburg, OH 44087
    216.505.4400
    info@216digital.com

    Support

    Support Desk
    Acceptable Use Policy
    Accessibility Policy
    Privacy Policy

    Web Accessibility

    Settlement & Risk Mitigation
    WCAG 2.1/2.2 AA Compliance
    Monitoring Service by a11y.Radar

    Development & Marketing

    eCommerce Development
    PPC Marketing
    Professional SEO

    About

    About Us
    Contact

    Copyright 2024 216digital. All Rights Reserved.