Digital Marketing Tips and Strategies to Grow Your Business

Who Needs Web Accessibility Training?
Think about all the hands that shape a website before it goes live.

A designer sketches the layout. A content writer crafts the story. A developer brings it to life. A marketer promotes it. A project manager keeps the wheels turning. But if even one person in that chain doesn’t understand the basics of accessibility, the final experience can fall short for someone trying to navigate with a screen reader, keyboard, or other assistive tools.

Accessibility issues don’t usually happen because people don’t care—they happen because people don’t know what to look for. That’s why accessibility training isn’t just for developers or tech teams. It’s for everyone who shapes the digital experience—from strategy to support.

When teams understand their role, accessibility becomes part of the process—not a last-minute fix. And that’s when real progress begins.

Why Broader Accessibility Training Matters

Accessibility barriers often hide in plain sight. A confusing heading can trip up a screen reader. An auto‑playing video can trap a keyboard user. Each issue might start with a different team, so solving them requires shared awareness and a shared skill set.

When every role learns the basics, good habits form early. This lowers future repair costs, speeds up projects, and reduces legal risk. Just as important—it sends a clear message: “Our doors are open to everyone.”

Who Should Learn—and What They Need to Know

Here’s how accessibility training benefits each team involved in your digital presence.

1. Executives and Senior Leaders

What they do: Set vision, approve budgets, choose partners.

Why they train: Training helps leaders connect accessibility to results—larger audiences, stronger brand trust, and measurable ROI. They also learn how setting clear goals and timelines keeps inclusion on track.

2. Designers and UX Teams

What they do: Choose colors, type, layouts, and flows.

Why they train: Design choices determine whether text is readable, buttons are reachable, and flows make sense. Training covers contrast, consistent icon labels, logical headings, and visible focus indicators.

3. Developers and Engineers

What they do: Write and test code.

Why they train: Developers learn how to apply semantic HTML, ARIA roles, keyboard support, and accessible error handling. Even seasoned coders benefit from updated WCAG guidance and modern tooling.

4. Content Creators and Editors

What they do: Write blog posts, help articles, PDFs, and product pages.

Why they train: Clear headings, plain language, and helpful alt text transform raw info into inclusive content. Training includes quick checks for reading level, link clarity, and captioned media.

5. Marketers and Social Media Managers

What they do: Create campaigns, videos, landing pages, and emails.

Why they train: Marketing moves fast, and small oversights spread wide. Training ensures captions are added, visuals are described, and flashing graphics are avoided—protecting both reach and user safety.

6. Quality‑Assurance Testers

What they do: Validate features before launch.

Why they train: QA staff learn how to run both automated scans and manual checks with keyboards and screen readers. Catching issues here prevents costly post-launch fixes.

7. Product and Project Managers

What they do: Gather requirements, plan sprints, and manage scope.

Why they train: They learn to include accessibility in acceptance criteria and timelines, and track progress against WCAG standards—making sure nothing slips through.

8. Customer Support Teams

What they do: Handle questions and feedback.

Why they train: Support agents are often the first to hear about accessibility barriers. Training helps them log issues clearly, guiding meaningful improvements.

Building a Culture of Learning

Workshops are a great start—but lasting accessibility comes from weaving training into everyday workflows. Here’s how to keep that momentum alive:
- Start with a quick win: Host a one‑hour session on headings and alt text. Immediate impact builds confidence.
- Use role-based paths: Designers explore contrast and layout. Marketers focus on captions and social media accessibility.
- Pair training with checklists: A simple “before you publish” list—contrast, keyboard reach, captions—keeps lessons at the top of your mind.
- Bring in real users: Invite people with disabilities to demos. Live feedback drives empathy and makes the value of inclusive design unmistakable.
- Celebrate success: Recognize teams that close accessibility tickets or launch inclusive content.
Choosing the Right Accessibility Training Format

Not everyone learns the same way. Mix formats to meet your team’s needs:
- Live workshops: Great for Q&A and real-time practice.
- Short video modules: Ideal for busy schedules or quick refreshers.
- Office hours: Open sessions where experts answer questions from any team.
- Documentation hubs: Centralized space for checklists, coding samples, and brand guidelines.
Larger organizations may also benefit from certification tracks or external mentors to support deeper learning and audits.

Measuring Success

Track the impact of training to keep improving:
- Fewer accessibility issues during QA.
- Lower remediation costs thanks to early awareness.
- Positive user feedback from screen reader and caption users.
- Fewer legal notices or compliance complaints.
Quarterly progress reports help leadership see the value and maintain support.

Overcoming Common Roadblocks
- “We don’t have time.” Break accessibility training into 15-minute micro-lessons that fit between meetings.
- “We can’t teach everyone everything.” Focus on essentials for each role—developers need ARIA, executives don’t.
- “It sounds too technical.” Share real stories. A single form label can help both a low-vision user and someone filling it out in bright sunlight.
Getting Started: A Quick Action Plan
1. Audit your team’s skills. Survey knowledge gaps.
2. Create a roadmap. Start with high-impact roles.
3. Choose a learning partner. Consultant, online platform, or internal champion.
4. Launch a pilot session. Start with something approachable, like image alt text.
5. Review and refine. Gather feedback and evolve your approach.
When people know what to look for, accessibility becomes second nature—not a scramble.

Equip Your Team, Elevate Your Experience

A successful accessibility program isn’t powered by one expert—it’s built on shared understanding. The more your teams know, the more they can contribute to inclusive, compliant, user-friendly experiences from the very beginning.

Now’s the time to turn knowledge into action. Whether you’re setting strategy, designing experiences, writing content, or launching campaigns, accessibility training helps each role identify where inclusion starts—and how to make it stick.

Accessibility Training That Moves Teams Forward

At 216digital, we include complementary ADA training with every project because we believe that lasting accessibility starts with alignment. Our role-based approach ensures your team isn’t just meeting requirements—they’re embedding inclusion into design, development, and communication with confidence.

Ready to move forward? Schedule a personalized ADA briefing with us. We’ll help you map out your goals, identify key opportunities, and launch a training strategy that’s effective, affordable, and built to last.

The most accessible experiences are the ones designed with intention. Let’s help your team build them.
Greg McNeil

April 17, 2025

Web Accessibility Training

Accessibility, Accessibility Training, Marketer, Web Accessibility Training, web developers, Website Accessibility
Accessible Documents: 7 Issues You Might Overlook
Have you ever tried to read a PDF on your phone only to pinch‑zoom until the text blurs? Now, picture that same frustration multiplied for someone who relies on a screen reader, a keyboard, or extra magnification. Inaccessible documents aren’t minor annoyances—they’re brick walls that block information. That’s why creating accessible documents is more than a best practice—it’s a necessity.

This post walks through seven barriers often hidden inside PDFs and Word files. For each one, you’ll see why it matters, which Web Content Accessibility Guidelines (WCAG) success criteria apply, and how a few practical tweaks can open the door for every reader.

Invisible Obstacles: Why Documents Trip People Up

Web pages are usually built with clear HTML tags that signal headings, lists, and links. Conversely, documents mix text, images, and complex layouts in a single container. If you skip semantic structure or rely on visual styling alone, those layers become invisible mazes for people using assistive tech.

WCAG was designed for the web, yet its principles work perfectly for accessible documents. Meeting them keeps your files usable for screen readers, keyboard navigation, high‑contrast modes, and more.

1. Missing or Misused Headings

When screen reader users rely on heading levels to navigate, skipping or misusing them turns a well-organized document into a frustrating guessing game. Simply enlarging font size doesn’t cut it—headings need to be properly structured.

Make it better: Use built-in heading styles (H1, H2, H3, etc.) in Word or Google Docs, not manual formatting. Stick to one H1 per page for your title, followed by a clear hierarchy.

Don’t forget: WCAG 1.3.1 requires meaningful structure—not just visual formatting. Run an accessibility checker before exporting to PDF to make sure your headings stay intact.

Pro tip: Set your document language, so screen readers know how to pronounce text correctly. In Word, go to Review > Language > Set Proofing Language.

2. When PDFs Are Just Pictures

A scanned contract that looks fine on screen may be completely silent to assistive tech. Without real text, a screen reader simply announces “graphic… graphic… graphic.” There’s no searching, no enlarging, and no reading.

What to do instead: Use OCR (Optical Character Recognition) to create a text layer. Adobe Acrobat, ABBYY FineReader, and Google Drive all have built-in OCR tools.

Make it work: Always proofread OCR results—blurry scans and fancy fonts often lead to errors.

Standards check: WCAG 1.4.5 requires using real, selectable text whenever possible.

Bonus tip: Use document properties to add a title and author—these help screen readers and improve file organization. In Word: File > Info > Properties.

3. Color Contrast That’s Too Subtle

That soft gray text might look sleek on a light background—but if you have low vision or are reading on a dim screen, it becomes nearly invisible.

How to fix it: Check color combinations before publishing. Use tools like WebAIM’s Contrast Checker or Adobe’s color contrast tools.

What the guidelines say: WCAG 1.4.3 calls for a minimum contrast ratio of 4.5:1 for standard text.

Design reminder: Check charts, infographics, and callout boxes too—those often sneak past brand reviews.

4. Vague Link Text

When every hyperlink says “Click here,” a screen reader user hears the same phrase over and over, with no context. It’s like walking through unlabeled doors and hoping for the best.

Do this instead: Write descriptive links like “Download the 2025 Benefits Guide (PDF).” This helps everyone know what to expect before they click.

Standards note: WCAG 2.4.4 requires link text to make sense on its own.

Extra clarity: In Word, use ScreenTips (Alt + Ctrl + D) to add hover-text instructions for links.

5. Images Without Alt Text

If an image doesn’t include alt text, assistive tech can’t describe it—and users miss the point. Charts, infographics, and even decorative flourishes need attention.

Quick fix: Describe the key message, not every visual detail. For example, summarize trends or highlight data points in charts.

WCAG compliance: Guideline 1.1.1 requires text alternatives for all meaningful images.

Helpful tip: Tag purely decorative images as “null” or “decorative,” so screen readers skip them. For complex visuals, link to a longer description or add it in an appendix.

6. Tables That Don’t Translate

Tables made with tabs or manual spacing may look fine, but screen readers can’t follow the structure. Data ends up being read out of order—turning financials or schedules into a jumbled mess.

Get it right: Use built-in table tools. Define the first row as a header and use column headers where needed.

Testing tools: In Word: Table > Properties > Row > Repeat as header row. In Acrobat Pro, use the Table Editor and test with NVDA or VoiceOver.

Remember: WCAG 1.3.1 also applies here—data must be presented with proper markup and relationships.

Avoid this: Don’t use tables for layout. It may seem like a shortcut, but it often leads to accessibility headaches.

7. Lists That Don’t Act Like Lists

Typing dashes or asterisks might look fine visually, but to a screen reader, it’s just a single paragraph. The structure—and meaning—is lost.

Better approach: Use the bullets or numbering tools built into Word or Docs. Real lists help assistive tech break up and interpret content correctly.

After exporting: Run “Autotag Document” in Acrobat and verify that lists are correctly tagged.

WCAG reference: Once again, 1.3.1—structure matters.

8. Use Clear Language and Layout

Overly complex language or long-winded paragraphs can be barriers in themselves. Accessibility isn’t just about code or design—it’s about comprehension too.

Try this: Write with clarity. Use simple words, short sentences, and plenty of white space. Break things up with subheadings and bulleted lists.

Pro tip: Aim for an 8th-grade reading level or below when possible. Tools like Hemingway Editor or Microsoft Editor can help simplify your language.

9. Choose the Right Export Settings

Even the best-crafted document can lose accessibility features when exported carelessly.

Before hitting “Save As”:
- Use formats that preserve tags, alt text, and headings (e.g., PDF/A).
- Use built-in export tools from Word, not third-party converters.
- Double-check using an accessibility checker like Adobe Acrobat’s.
10. Provide Alternative Formats

Not every user consumes content the same way. Offering alternative versions ensures a broader reach.

Examples:
- A transcript for a video.
- A plain-text version of a design-heavy PDF.
- A mobile-friendly HTML version of a Word document.
- This level of flexibility supports users with screen readers, low vision, dyslexia, and more.
Beyond the Basics: Keep Creating Accessible Documents

Fixing the top document issues is a great start—but real accessibility doesn’t stop at a checklist. It’s something you build into the process and revisit as tools evolve, teams shift, and standards update.

Don’t rely on tools alone. Automated checkers are helpful for flagging missing tags or contrast issues, but they won’t catch everything. They can’t tell if your heading structure makes sense or if your alt text actually describes the image. A quick manual review—ideally from someone who understands assistive tech—can make all the difference.

Keep your team in the loop. Many of the most common document barriers come down to simple habits: skipping heading styles, forgetting to add alt text, or using layout tables. Short training sessions or documentation refreshers can prevent a lot of repeat issues, especially if you’re onboarding new staff or updating templates.

Check your templates yearly. Accessibility standards grow. So do the tools we use to write, design, and export. A quick annual review of your document templates helps ensure you’re not accidentally locking in outdated practices or missing opportunities to improve.

Make Your Documents Work for Everyone

Document accessibility isn’t about perfection—it’s about intention. When you take the time to apply heading styles, write descriptive link text, or check contrast ratios, you’re creating something that works for more people, in more ways.

These changes aren’t hard. They’re habits. And once your team knows what to look for, accessible documents become second nature—just like spell check or formatting a title page.

At 216digital, we offer more than advice. We can review your files, train your staff, and even build accessible templates tailored to your needs. Every project we take on includes complementary ADA training—so your team is empowered, not just compliant.

If you’re ready to move past the guesswork and start building documents that include everyone, schedule a quick briefing with us. Together, we can turn accessible content into a shared standard—not a scramble.

Let’s take that first step—one document at a time.
Greg McNeil

April 16, 2025

How-to Guides

Accessibility, accessible documents, How-to, PDF, WCAG, Website Accessibility
What to Expect from an Accessibility Audit
Running a business is no small feat. Between managing daily operations, keeping customers happy, and staying on top of your digital presence, it’s easy to overlook something like web accessibility. But in today’s world, where more users rely on assistive technology to browse online, accessibility is no longer optional—it’s essential.

That’s where an accessibility audit comes in. It’s a smart, proactive step that helps you understand how well your website works for people with disabilities and where improvements are needed. It’s not just about avoiding legal trouble—it’s about creating a better experience for all your visitors.

Let’s break it down so you know exactly what to expect.

Why Accessibility Matters

Reaching Every Visitor

Web accessibility is about making sure everyone can use your website—no matter their ability. That includes people who rely on screen readers, keyboard navigation, or voice control, as well as those with visual, hearing, or cognitive challenges.

A more accessible site leads to:
- Better user experience
- Improved search engine visibility
- Increased customer trust
It’s a win for your users and your business.

Reducing Legal Risk

ADA-related lawsuits over inaccessible websites are on the rise, and many target small to mid-sized businesses. In fact over 67% of lawsuits in 2024 were targeting businesses with an annual revenue under $25 million or less.

These cases can be stressful and expensive—even if the issues weren’t intentional.

A professional accessibility audit helps you spot and fix issues early, protecting your business while showing your commitment to inclusion.

What Is an Accessibility Audit?

An accessibility audit is a full review of your website to find any barriers that might stop people with disabilities from using it. These barriers could be anything from missing image descriptions to forms that don’t work with a screen reader.

The audit is based on the Web Content Accessibility Guidelines (WCAG), which provide a clear set of standards for accessible web design. Following WCAG helps ensure your site meets legal requirements—and, more importantly, that it works for everyone.

The Accessibility Audit Process: Step-by-Step

Here’s what typically happens during a full accessibility audit:

Initial Consultation & Scope Definition

The process starts with a conversation. You and your audit team will review your website’s goals, user flows, and top-priority pages—like your homepage, checkout process, or contact form. This helps focus the audit on what matters most.

Automated Testing

Automated tools run quick scans to catch common issues like:
This is a great first step, but automated testing only catches part of the picture. That’s why manual checks are so important.

Manual Evaluation

Accessibility specialists then take a deeper look at your site. They’ll test things like:
- Can users navigate with just a keyboard?
- Are screen readers reading content in the correct order?
- Do buttons and links have clear, accessible labels?
Manual testing finds the issues that machines often miss—and ensures your site works for real people in real situations.

User Testing with Assistive Technology

In some cases, the team may bring in people who use assistive tools daily—like screen readers or alternative input devices—to test your site. Their feedback offers invaluable real-world insight that helps uncover problems no tool or developer could spot alone.

Documentation of Findings

Once testing is done, you’ll receive a report that includes:
- A list of all issues
- Where each problem exists
- The specific WCAG criteria it violates
- Visual examples and code references for clarity
This report serves as your roadmap to fixing issues efficiently.

Prioritization of Issues

Not all issues are created equal. The audit team will help you prioritize based on the following:
- How severe the issue is
- How many users it might impact
- Whether it poses a legal risk
This lets you address the biggest barriers first and build a smart action plan moving forward.

Remediation Recommendations

Finally, you’ll receive clear, actionable guidance for fixing each issue. These recommendations will be tailored to your site’s platform, content, and team capacity. Some fixes might be quick, while others may take more planning—but you’ll know exactly what to do and where to start.

What Happens After the Audit?

Implementing Fixes

After the accessibility audit, it’s time to put the findings to work. Your team—or a trusted partner like 216digital—can help implement those changes, making sure they align with best practices while preserving your brand’s design and functionality.

Team Training

To keep your site accessible over time, it helps to train the people who update it. That could mean a short session on how to use alt text or a checklist for adding new content. A little knowledge goes a long way in preventing future issues.

Ongoing Monitoring

Accessibility isn’t something you check off once and forget about. Websites are living things—they change, grow, and update over time. That means new accessibility issues can pop up without warning, especially as content is added or platforms evolve.

That’s why regular monitoring is key. Running periodic scans, reviewing key pages, and staying alert to new barriers helps you maintain accessibility long after the initial audit. Tools like a11y.Radar, 216digital’s ongoing monitoring service, are designed to make this easier. It quietly keeps tabs on your site, flags issues early, and helps ensure your site stays in line with accessibility best practices—without the need for constant manual checks.

Your Website’s Future Just Got Brighter

A professional accessibility audit gives you more than just a report—it gives you peace of mind. It’s a smart, future-focused way to protect your business, improve your site, and welcome every visitor who comes your way.

At 216digital, we specialize in helping small to mid-sized businesses make sense of accessibility. Our expert-led audits, clear documentation, and hands-on remediation support make the process easy to follow and effective to implement. We help you go beyond compliance—to a website that’s truly inclusive.

If you’re ready to create a better experience for everyone and reduce your legal risk, let’s talk. A more accessible site isn’t just better for users—it’s better for business.
Greg McNeil

April 15, 2025

Testing & Remediation

Accessibility, Accessibility Audit, Accessibility testing, automated testing, manual audit, Web Accessibility, Website Accessibility
How GDPR and CCPA Are Shaping Data Privacy
Data privacy isn’t a new concept. Businesses have been managing sensitive customer information for decades—through paper files, databases, CRMs, and now digital platforms. What has changed is the growing expectation that people should have control over their own data. Laws like the General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA) didn’t invent data privacy—but they’ve redefined the standards.

These regulations are reshaping how organizations around the world approach data—how they collect it, store it, share it, and most importantly, how they communicate about it. If you’re leading a business, managing digital operations, or overseeing customer experience, understanding how these laws work isn’t just a compliance task—it’s a strategic advantage.

What the CCPA Introduced to U.S. Businesses

When the CCPA took effect in 2020, it marked a turning point for U.S.-based organizations. For the first time, there was a law that gave American consumers—not just businesses—clear, enforceable rights over their personal data. It caught many companies off guard.

California residents gained the legal right to:
- Know what personal information is being collected about them.
- Request the deletion of that information.
- Opt out of the sale of their data.
For businesses, this meant a new level of transparency. You needed to disclose how data was being used, offer clear opt-out tools, and ensure your privacy policies were not only accessible—but written in plain, understandable language.

This wasn’t just about legal boxes to check. It was about shifting power. CCPA put the customer in the driver’s seat.

A Ripple Effect Beyond California

Even though the CCPA is a state law, its impact has reached far beyond California’s borders. Why? Because any business that serves California residents—regardless of location—has to comply. And for companies with customers across the U.S., it simply made sense to raise privacy practices across the board.

That’s why CCPA didn’t stay a California issue. It sparked national conversations, boardroom discussions, and policy rewrites. It also paved the way for other states to create their own laws. Virginia, Colorado, Connecticut, and Utah have already passed privacy regulations of their own. Each carries unique nuances, but most borrow heavily from the same foundational ideas introduced by the CCPA and GDPR.

The GDPR: Setting the Global Standard

Before CCPA came onto the scene, there was GDPR. Introduced by the European Union in 2018, the General Data Protection Regulation quickly became the global benchmark for data privacy.

Its scope was ambitious—and intentional. GDPR applies to any organization, anywhere in the world, that processes data from EU citizens. Whether you’re based in Paris, New York, or Singapore, if your business interacts with European customers, you’re expected to comply.

Core GDPR Requirements:
- Consent: Businesses must get clear, informed consent before collecting personal data.
- Right to Be Forgotten: Individuals can ask for their data to be deleted permanently.
- Breach Notification: Organizations must report data breaches within 72 hours.
- Data Portability: Consumers have the right to access and transfer their own data.
The GDPR’s influence is still growing. Many new laws—both in the U.S. and abroad—are built using GDPR as a model. And in the absence of a single U.S. federal privacy law, many organizations default to GDPR compliance as a way to meet the highest global standard.

GDPR vs. CCPA: Two Paths, One Direction

While GDPR and CCPA share the same underlying goal—giving people more control over their personal data—they approach it in different ways.

Who’s Affected?
- GDPR: Global reach. Applies to any company handling EU data.
- CCPA: U.S.-based, but applies to companies interacting with California residents.
Consumer Rights
- GDPR: Offers broad rights—access, deletion, correction, portability.
- CCPA: Emphasizes transparency, deletion, and the right to opt out of data sales.
Consent Models
- GDPR: Requires proactive, upfront permission.
- CCPA: Allows post-collection opt-outs, which can be more flexible for businesses but less direct for consumers.
The differences matter—but the direction is the same. Regulators are moving toward greater accountability, and consumers are demanding more clarity and control.

A Growing Patchwork of U.S. Laws

The U.S. now faces a growing number of state-level privacy laws, each with its own requirements and timelines. Virginia’s VCDPA, Colorado’s CPA, and Connecticut’s CTDPA are just a few of the new players. While many reflect GDPR or CCPA in principle, the details vary—and that’s where things get tricky.

For multi-state businesses, managing these differences isn’t just time-consuming—it can be a real risk. You’re not just dealing with technical updates to your website. You’re coordinating privacy notices, opt-out mechanisms, data retention policies, and more—often with overlapping or conflicting requirements.

A unified federal privacy law, like the proposed American Privacy Rights Act (APRA), could help simplify things. However, with delays in Congress and shifting political priorities, that kind of clarity is still out of reach.

What You Can Do Now

So what’s the path forward? The answer isn’t to wait for regulation to catch up—it’s to lead with purpose.

1. Map Your Data

Know what you’re collecting, where it’s stored, who has access, and why. Without a clear inventory, compliance is guesswork.

2. Strengthen Your Privacy Policy

Make sure your privacy policy is accurate, accessible, and written in plain language. Your customers—and regulators—should understand it without needing a legal degree.

3. Build in Flexibility

Invest in systems and processes that can adapt. Privacy laws will continue to evolve. Your infrastructure should be ready to scale with them.

4. Respect User Rights

Whether it’s a GDPR data access request or a CCPA opt-out form, your business should respond quickly, clearly, and respectfully. That responsiveness builds trust.

5. Lead with Transparency

Customers don’t expect perfection. But they do expect honesty. Be upfront about what data you collect and how you use it. When in doubt, over-communicate.

Final Thoughts

Data privacy isn’t a passing trend—it’s a defining feature of the modern digital experience. And laws like GDPR and CCPA aren’t just compliance checklists. They’re a signal that the world is changing, and that businesses are expected to change with it.

The companies that embrace this shift—proactively, strategically, and transparently—will be the ones that win customer trust and loyalty over the long term.

If you’re looking for help navigating this evolving landscape, 216digital is here to support you. Schedule a privacy and accessibility briefing with our team and take the first step toward smarter, future-ready data practices.
Greg McNeil

April 14, 2025

Legal Compliance, Web Design & Development

CCPA, data privacy, GDPR, web development
How to Use aria-describedby for Web Accessibility
Have you ever looked at a form, seen the bold text or red borders, and instantly known what to do next? That’s because as visual users, we get a lot of clues from layout, color, and spacing. But for someone using a screen reader, those visual hints don’t exist. Instead, they rely on code—programmatic clues—to make sense of what’s on the screen.

That’s where aria-describedby comes in. If you’ve ever struggled to make a form, button, or modal accessible, you’re not alone. aria-describedby is a powerful tool that helps users understand what’s happening—if you use it right.

In this article, I’ll walk you through how to use aria-describedby the right way. We’ll go through practical code examples, real use cases, and common mistakes. I’ll also show you how it ties into making things like captions and subtitles more accessible, especially for users with assistive technology.

Unpacking aria-describedby

aria-describedby lets you link an element to other content that gives extra detail. It points to the ID(s) of one or more elements that contain helpful text. Think of it like this:
- aria-labelledby gives something its name.
- aria-describedby gives it extra explanation.
If a screen reader sees an input with aria-describedby= "pw-hint", it will read the input label and the hint.

Why It’s Important

Used correctly, aria-describedby helps you meet the Web Content Accessibility Guidelines (WCAG) success criteria. It improves accessibility for users who rely on screen readers. It’s especially helpful when native HTML doesn’t cover all the information a user needs. This matters for users navigating complex interfaces—like forms, modals, or media players with captions and subtitles.

When Should You Use aria-describedby?
- Form fields: Add help text or error messages.
- Buttons: Clarify what will happen, especially for destructive actions.
- Dialogs/modals: Explain what the dialog is for.
- Tooltips: Offer extra information without cluttering the interface.
- Live status updates: Let users know when things change, like upload progress or loading indicators.
aria-describedby can even support captions and subtitles in video players by giving extra context for the screen reader user, describing what’s happening beyond the visual content.

When Not to Use It
- If HTML already does the job (like using <label> or <fieldset>).
- If it adds repetitive or unnecessary text.
Code Walkthroughs: Real-World Examples

Let’s get into some code. These examples show how to use aria-describedby in ways that make a real difference.

Form Fields

Password Requirements
```
<label for="pw">Password</label>
<input type="password" id="pw" aria-describedby="pw-hint">
<p id= "pw-hint">Password must be at least 12 characters long and include a number.</p>
```
Error Messages
```
<label for="email">Email address</label>
<input type="email" id="email" aria-invalid="true" aria-describedby="email-error">
<p id="email-error" class="error">Please enter a valid email address.</p>
```
Multiple Descriptions
```
<input type="text" id="username" aria-describedby="username-req username-tip">
<p id="username-req">Must be at least 8 characters.</p>
<p id="username-tip">Displayed on your profile.</p>
```
Buttons

Destructive Action Explanation
```
<button aria-describedby="delete-desc">Delete Account</button>
<p id= "delete-desc">This will permanently remove your account and all data.</p>
```
Dialogs and Modals

Accessible Dialog
```
<div role="dialog" aria-modal="true" aria-labelledby="dialogTitle" aria-describedby="dialogDesc">
  <h2 id="dialogTitle">Confirm Deletion</h2>
  <p id= "dialogDesc">This action is permanent and cannot be undone.</p>
</div>
```
Tooltips and Live Regions

Accessible Tooltip
```
<input type="text" id="first" aria-describedby="tip1">
<div id="tip1" role="tooltip">Optional field.</div>
```
Status Messages
```
<div aria-describedby="upload-status">
  <input type="file" onchange="showUploadStatus()">
  <div id="upload-status" aria-live="polite">Uploading...</div>
</div>
```
These techniques can also apply to custom media players. You can use aria-describedby to point to captions and subtitles that are visible on screen but also need to be announced programmatically.

Common Mistakes to Avoid
- Too Many Descriptions: Linking to 3 or 4 IDs might overwhelm users.
- Broken References: Make sure every ID you point to actually exists.
- Redundant Content: Don’t repeat what’s already in the label.
- Timing Issues: Don’t change the text dynamically during focus unless absolutely necessary.
- Inconsistent Patterns: Keep your approach consistent across similar components.
Best Practices for Effective Implementation
- Write Clear Descriptions: Keep them short, useful, and easy to understand.
- Avoid Jargon: Explain things in plain language.
- Keep Descriptions Visible: If possible, don’t hide the text—what helps screen reader users can help sighted users, too.
- Use Native HTML First: ARIA is a supplement, not a substitute.
- Test Often:
  - Use screen readers like NVDA, JAWS, and VoiceOver.
  - Test in browsers like Chrome, Firefox, and Safari.
- Stay Consistent:
  - Create reusable components.
  - Document your design patterns.
  - Automate accessibility checks.
This also applies to any content with captions and subtitles—they should be clearly described in a way that works for both visual and non-visual users.

Beyond the Code: Organizational Tips
- Code Reviews Should Include Accessibility
- Use Linters and Audits: Tools like Google Lighthouse or WAVE to catch ARIA barriers.
- Add Accessibility to Your QA Checklist
- Train Your Team: Make sure everyone knows what ARIA does and doesn’t do.
If you’re building tools with captions and subtitles, include accessibility from the start. Don’t bolt it on later.

Accessible Descriptions, Better UX

aria-describedby is one of those quiet heroes of accessibility. It helps fill the gaps between what users see and what assistive tech can tell them.

Used well, it improves the user experience for everyone—not just people using screen readers. It’s especially helpful in forms, dialogs, and anything with captions and subtitles, where the added context can be critical.

So remember: use aria-describedby intentionally, test it thoroughly, and keep your patterns consistent. And if your team needs help making your site or app more accessible, 216digital offers expert guidance to help you meet compliance standards—while creating a better experience for all users.

Let’s keep building an internet that works for everyone. One line of code at a time.
Greg McNeil

April 11, 2025

How-to Guides

ARIA, aria-describedby, How-to, Web Accessibility, web developers, web development, Website Accessibility
Judge Pushes Back on Serial ADA Plaintiffs
The Americans with Disabilities Act (ADA) was enacted in 1990 to prohibit discrimination against people with disabilities. Over the years, it’s helped make public spaces—including digital environments—more accessible to everyone. However, the rise of serial ADA plaintiffs—individuals who file dozens or even hundreds of lawsuits—has raised serious concerns among business owners and judges alike. Some of these cases appear less about securing genuine accessibility improvements and more about generating quick financial settlements.

Recently, a federal judge pushed back against this growing trend, signaling that the courts are beginning to question the motives and tactics of some serial ADA plaintiffs. This shift could mark a turning point for businesses frustrated by opportunistic lawsuits. But it doesn’t mean business owners can relax when it comes to ADA compliance—especially online.

In this article, we’ll explore what serial ADA litigation looks like, why businesses risk non-compliance in the first place, how a recent judge’s ruling might change the game, and what proactive steps businesses can take to protect themselves. We’ll also show how partnering with a firm like 216digital can ensure your digital properties are accessible and legally compliant.

What Are Serial ADA Plaintiffs?

A serial ADA plaintiff is someone who files multiple lawsuits under the ADA, often targeting small businesses for alleged accessibility violations. While the ADA is a civil rights law that rightly empowers individuals to hold businesses accountable, these serial filings usually follow a pattern:
- Rapid-fire lawsuits: Dozens of complaints are filed in a short period, often by the same attorney.
- Low-hanging claims: Plaintiffs target minor infractions, such as font contrast issues or missing alt text on websites.
- Settlement-focused: Lawsuits are usually resolved with monetary settlements rather than actual accessibility improvements.
These actions put a financial strain on small and mid-sized businesses, many of which settle to avoid legal fees—even if they were unaware of the issues or were actively working toward compliance.

Why Do Businesses Risk ADA Non-Compliance?

Many business owners want to do the right thing, but digital accessibility often falls through the cracks for a few reasons:
- Lack of awareness: Some companies don’t realize ADA applies to their websites, not just physical locations.
- Complex regulations: Accessibility laws and standards like WCAG (Web Content Accessibility Guidelines) can be difficult to interpret without expert guidance.
- Limited budgets: Small businesses may not have the resources to hire in-house accessibility experts.
- Inconsistent enforcement: Until recently, the legal system’s tolerance for serial plaintiffs made compliance seem like an expensive guessing game.
Unfortunately, ignorance of the law doesn’t exempt businesses from lawsuits—especially when aggressive litigants are actively seeking out violators.

Judge Cogan Pushes Back: A Turning Point?

In a recent case, federal Judge Cogan of California dismissed multiple web accessibility lawsuits brought by a serial plaintiff, citing a lack of standing and evidence of genuine harm. The court noted that the plaintiff had filed over 50 nearly identical lawsuits against small businesses, often without ever intending to visit or interact with them in any meaningful way.

Judge Cogan questioned whether the plaintiff had suffered real injury or was simply using the ADA as a tool to generate settlements. The ruling emphasized that the purpose of the ADA is to promote meaningful access, not to enable exploitative litigation.

This decision doesn’t make digital accessibility any less important—but it sends a clear message: the courts are starting to scrutinize the intentions behind ADA lawsuits. It’s a warning to serial plaintiffs and an opportunity for businesses to address compliance proactively rather than react to legal threats.

Practical Steps to Avoid Being Targeted

Whether or not the courts are curbing serial litigation, businesses should take real accessibility seriously. Here are steps to protect your brand, reduce legal risk, and create better experiences for all users:

1. Conduct a Professional Accessibility Audit

Start by identifying what accessibility issues exist on your website. Automated tools can catch some problems, but a full audit—especially one that includes manual testing with assistive technologies—is the gold standard.

2. Fix the Most Common Accessibility Errors

Serial plaintiffs often target:
- Missing alt text on images
- Poor color contrast
- Inaccessible navigation menus
- Improper heading structures
- Forms that can’t be completed with a keyboard
Addressing these issues can significantly lower your risk of being sued.

3. Document Your Accessibility Efforts

Even if your site isn’t perfect, showing that you’re making active efforts can make a difference in court. Keep records of audits, remediations, and ongoing updates.

4. Stay Informed on Legal Requirements

Accessibility standards evolve. Staying up to date on WCAG guidelines and DOJ updates to ADA interpretations is essential to maintaining long-term compliance.

5. Implement Ongoing Monitoring

Accessibility isn’t a one-and-done project. Use tools like a11y.Radar, offered by 216digital, to continuously monitor and address new issues before they become problems.

How 216digital Helps You Stay Accessible—and Lawsuit-Proof

At 216digital, we specialize in helping businesses of all sizes navigate the often-confusing world of digital accessibility. We go beyond automated scans and generic checklists to provide comprehensive, real-world accessibility services that keep you compliant and reduce your legal exposure.

Our Services Include
- Phase 1 Risk Mitigation: We identify and fix the most high-risk accessibility issues that could attract serial ADA plaintiffs.
- Phase 2 Real-World Accessibility: We use screen readers, keyboard-only navigation, and other assistive technologies to test your site like real users do.
- a11y.Radar Monitoring: Our proprietary service provides ongoing accessibility monitoring and alerts, ensuring your site stays compliant even as content changes.
- Accessibility Consulting and Training: We don’t just fix your website—we empower your team with the knowledge and tools to maintain accessibility long-term.
By working with 216digital, you’ll avoid frivolous lawsuits and create a better online experience for all your users, including those with disabilities.

Final Thoughts

The recent judicial scrutiny of serial ADA plaintiffs is a promising development for business owners who feel trapped between doing the right thing and defending against exploitative lawsuits. But make no mistake: web accessibility still matters—and compliance is still your responsibility.

Rather than playing defense after a lawsuit hits your inbox, you can take a proactive approach that protects your business, supports your customers, and aligns with the original spirit of the ADA.

Let 216digital help you stay compliant, reduce risk, and deliver a more accessible web experience for everyone.

Need help getting started?

Contact 216digital today for a professional web accessibility audit and find out how we can help you safeguard your digital presence from serial ADA plaintiffs.
Greg McNeil

April 10, 2025

Legal Compliance

Accessibility, ADA Lawsuit, Web Accessibility, Website Accessibility
Is Your Website Compliant with Australia’s DDA?
When you think about making a website, you might picture coding, design, or content. But have you ever considered whether everyone can actually use your site? Web accessibility isn’t just a tech issue—it’s about making the online world open to everyone, including people with disabilities. In Australia, there’s a growing focus on this topic, and it’s changing how websites are built and maintained. The Disability Discrimination Act, or DDA, is a key piece of the puzzle, because it covers much more than physical buildings. In fact, it also affects your digital presence.

In this post, we’ll dig into why web accessibility matters, how the DDA factors in, and what you can do to make your website more inclusive. Think of this as a friendly chat that aims to keep things simple, helpful, and human-centered. After all, good web design isn’t just about code—it’s about people.

Why Web Accessibility Should Be on Your Radar

More than 1 in 5 Australians live with some form of disability. That’s millions of people who might need your products or services. If your site has poor design, confusing navigation, or features that aren’t easy to use with assistive technology, you risk losing a huge chunk of potential customers. In fact, nearly 5 million Aussies are affected by poor accessibility every day.

But web accessibility isn’t just about meeting a legal requirement under the DDA—it’s also good for business. When you make a site easier for people with disabilities, you often end up improving the user experience for everyone. Aging users with weaker eyesight benefit from clearer text, while someone with a broken arm might be thankful for keyboard-friendly navigation. Even people dealing with slow internet connections appreciate a well-optimized site. Accessibility is bigger than just a checkbox; it’s an approach that says, “I’m open to all.”

What the Disability Discrimination Act (DDA) Actually Says

The DDA (Disability Discrimination Act) was passed in 1992, and it aims to protect people from discrimination because of their disability. While many people think of it in terms of physical locations or employment, the law also applies to services and goods. And in the modern world, that means websites and online stores can’t shut people out.

Real Cases That Changed the Game
- Bruce Maguire vs. Sydney Olympics (1999): This case involved a blind man who found the official Olympics website nearly impossible to use. It was the first major situation in Australia that highlighted digital accessibility and made it clear that the DDA applies online as well.
- Gisele Mesnage vs. Coles (2014): Gisele, who is blind, had serious trouble doing her online grocery shopping because of inaccessible design. She took the issue to the Federal Court, showing again that large companies can’t ignore web accessibility—and neither can smaller ones.
These cases proved that the DDA isn’t just legal talk; it has real impact on how websites are made. If you’re offering goods or services online, you need to pay attention.

So… Does This Apply to Your Website?

Short answer: Almost definitely. The DDA is broad, and it covers government sites, public-facing services, and private businesses too. Whether you run a bank, a school, an eCommerce store, or a travel website, you should take steps to be accessible. Even if any inaccessibility is unintentional, it can still lead to complaints or legal action. No one wants that—so it’s better to get ahead of the game.

The Standards You Need to Know (and Follow)

When people talk about web accessibility standards, they’re usually talking about the Web Content Accessibility Guidelines (WCAG). These are international guidelines that detail how to make online content usable for everyone. In Australia, the target is WCAG 2.1 or 2.2 at Level AA.

Yes, the guidelines can feel a bit technical, but they break down into principles that are pretty straightforward:
- Perceivable: Make sure people can see or hear your content.
- Operable: Your site should work with a keyboard, not just a mouse.
- Understandable: Use clear language so people don’t get confused.
- Robust: Support different types of assistive technologies and devices.
The government requires its websites to comply. Private businesses might not face legal pressure in every case—but make no mistake, the DDA clearly expects you to make your site accessible.

Government Strategies & National Guidelines

Australia has several strategies and guidelines to push web accessibility forward:
- National Transition Strategy (NTS): This initiative set the expectation that all government websites meet WCAG 2.0 AA. Even though it first focused on government sites, it signaled that accessibility is a big deal for any public-facing platform.
- Digital Service Standard: Thirteen principles guide inclusive design for government services. Though aimed at government, many businesses look to these standards for best practices.
- AS EN 301 549:2020: This one’s pretty tech-heavy, but it’s an Australian accessibility standard based on European laws, covering software, hardware, and other ICT services. If you hear it mentioned, know it’s part of the broader push for more inclusive digital tools.
What Happens If You Don’t Comply?

So what if you decide you can ignore the DDA? First, complaints usually go to the Australian Human Rights Commission. If they can’t be resolved through conciliation, the issue might end up in the Federal Court. That can mean big fines, hefty legal fees, and the kind of negative attention that hurts your brand. You don’t have to be a huge company like Coles to face consequences. The DDA has wide reach, and smaller businesses can face the same legal and financial risks if they don’t meet accessibility standards.

Making Your Website Accessible: Where to Start
- Understand Web Accessibility Guidelines: Familiarize yourself with WCAG to know what needs to be done for accessibility.
- Conduct a Website Audit: Regularly check your site for issues like missing alt text or poor contrast using automated tools or a professional audit.
- Implement Ongoing Training: Train your team to ensure everyone understands accessibility and prioritizes it in future updates.
- Stay Informed and Up-to-Date: Keep up with changes in web accessibility standards and best practices.
- Ongoing Monitoring: Use services like a11y.Radar for continuous monitoring, helping you address new accessibility issues promptly.
Make Accessibility a Priority—Not an Afterthought

If you remember just one thing from this discussion, it’s that web accessibility matters for real people. Sure, the DDA provides the legal framework—but beyond that, it’s simply good business sense and the right thing to do. A more accessible site doesn’t just keep you out of trouble; it opens the door to new customers, better user experiences, and a stronger brand image.

By making web accessibility a priority, you show you care about all your users, including those with disabilities. This mindset helps shape a future where the internet is truly open to everyone. If you’re unsure about where to start or how to keep your site fully compliant with the DDA, consider reaching out to professionals like 216digital. They can guide you through audits, training, and ongoing support, ensuring that you’re not just following the rules, but actively creating a more inclusive digital world.

Remember: the DDA doesn’t just regulate—it motivates. By taking accessibility seriously, you build a website that’s welcoming and friendly to anyone who visits. And that’s something we can all get behind. Let’s keep growing the web in a way that benefits us all.
Greg McNeil

April 9, 2025

Legal Compliance

Accessibility, accessibility laws, DDA, Disability Discrimination Act, International Accessibility Laws, Website Accessibility
What Designers Get Wrong About Accessible Web Design

When we talk about accessible web design, most people picture developers digging into code to fix issues after the fact. But the real magic—and often the biggest missed opportunity—starts much earlier in the process. It starts with us, the designers.

Design isn’t just about how something looks; it’s about how something works. That includes making sure every user can interact with it, regardless of ability. The challenge is, even seasoned designers can unintentionally leave accessibility gaps in their work. Not out of carelessness, but simply because we weren’t taught to think about it.

Let’s take a look at the most common ways accessible web design gets overlooked in the design phase—and how small changes can make a big difference. These aren’t technical developer fixes. They’re simple, design-first decisions that help create a more inclusive experience for everyone.

Relying on Color Alone

Using color to communicate meaning—like red for errors or green for success—might feel intuitive. But it doesn’t work for everyone. People with color vision deficiencies may not distinguish between red and green. Others might be browsing on devices in bright sunlight or with grayscale settings turned on. Color alone just isn’t enough.

The good news is that accessible web design doesn’t mean ditching color—it means backing it up. A red border becomes more effective with an icon like an exclamation point and a short label that says “Error.” Color still enhances the message, but now it’s readable by everyone, regardless of how they perceive color.

Poor Contrast Between Text and Background

Minimalist palettes are trendy, but light gray text on a white background can create a serious readability issue. For users with low vision, poor contrast turns your carefully crafted content into a frustrating puzzle. It’s not just a style choice—it’s a usability barrier.

Aiming for at least a 4.5:1 contrast ratio ensures your text is readable under a wide range of conditions, including mobile screens and bright environments. Tools like WebAIM’s Contrast Checker make it easy to test combinations. With accessible web design, clarity and style can absolutely coexist.

Hover-Only Interactions

Hover effects can make an interface feel sleek and modern, especially for desktop users. But the reality is that not everyone navigates with a mouse. Touchscreen devices and keyboard users don’t have the option to hover, which means they could miss essential content like tooltips, dropdowns, or action buttons.

Accessible web design calls for interaction that works across devices and input types. If something appears on hover, it should also be accessible via keyboard focus or tap. That way, no one is left guessing—or worse, completely missing part of the site.

Hiding or Removing Focus Styles

One of the more subtle mistakes designers make is removing focus outlines to make interfaces feel cleaner. That glowing blue ring might not match the brand aesthetic, but it’s a crucial indicator for users navigating with a keyboard. It shows where they are on the page.

Instead of removing it, try styling the focus indicator in a way that fits your brand. Make it visible, make it intentional. It’s a small touch, but it honors the needs of users who rely on keyboard navigation. That’s the heart of accessible web design—keeping things usable, not just pretty.

Icon-Only Buttons Without Labels

A trash can, a gear, a hamburger menu—these are all familiar icons to some of us. But they’re not universal. Assuming every user will instantly recognize what an icon means can create confusion, especially for users with cognitive differences or those who are new to digital interfaces.

By adding a short label like “Delete” or “Settings,” or by providing an accessible name using ARIA labels, you give your users clarity. Icons still add visual interest, but now they’re functional for everyone. It’s another way accessible web design respects a broader range of experiences.

Vague Link Text

Link text like “Click here” or “Learn more” might seem harmless, but it quickly becomes a problem for people using screen readers. These users often navigate by skimming a list of links, completely out of the surrounding context. If all the links say the same thing, it’s impossible to know where they go.

Writing meaningful link text—like “Download the 2025 Pricing Guide” or “Explore Our Accessibility Services”—adds clarity for everyone. Plus, it’s great for SEO. In accessible web design, clarity and functionality always go hand-in-hand.

Layouts That Fall Apart When Text Is Resized

Many users with low vision increase their device’s text size to read more comfortably. But if a layout isn’t built to handle that, the entire page can fall apart. Text overlaps, buttons get cut off, and navigation becomes a mess.

Designing with flexibility in mind—using relative units like em, rem, or percentages instead of fixed pixel values—helps keep layouts intact even when zoomed in. Responsive grids, media queries, and scalable components all support accessible web design by making sure your content can adapt.

Skipping Alt Text on Images

Every image on your site has a purpose, whether it’s decorative or informative. But when you leave out alt text—or worse, insert placeholder text like “image123.jpg”—users who rely on screen readers are left without context.

Good alt text is short, specific, and helps users understand the image’s role in the content. For example, “Smiling customer using our mobile app” is useful. If the image is decorative and adds no meaningful content, you can mark it as such so screen readers skip it. Accessible web design makes visuals work for everyone, not just those who can see them.

Hard-Coded Font Sizes

Hardcoding fonts in pixels may seem like a safe bet for maintaining visual control, but it can limit how users adjust their settings. People who need larger text may be blocked by your choices, especially if CSS prevents scaling.

By using relative units, you give users control over their reading experience. Fonts should scale with their preferences, not fight against them. Accessible web design puts usability first, allowing your audience to engage with your content in the way that works best for them.

Overly Complex Navigation

Mega menus, fancy interactions, and unique navigation patterns can look impressive in a mockup—but they can create major barriers for people using keyboards or assistive tech. When navigation becomes a puzzle, users are more likely to get frustrated and leave.

The most effective navigation is simple, consistent, and easy to explore. Use clear labels, test with keyboard-only input, and rely on semantic HTML whenever possible. Accessible web design doesn’t mean boring—it means dependable, predictable, and inclusive.

Where Good Design Meets Real-World Impact

Designers have the power to make the web more inclusive. And the best part? You don’t have to start from scratch. These changes are often small, thoughtful adjustments that make a big difference for users who rely on them.

Accessible web design isn’t a limitation—it’s an invitation to create better work. It asks us to go beyond trends and think deeply about the people who use the things we build. With every project, we can help make the internet a place where more people feel seen, supported, and able to fully participate.

If you’re looking for a partner who understands the balance between beauty, functionality, and accessibility, 216digital is here to help. Together, we can make accessible web design the standard—not the exception.

Greg McNeil

April 8, 2025

How-to Guides, Web Design & Development

Accessible Design, ADA Lawsuit, How-to, responsive design, UX, Web Accessible Design
How 216digital Makes Accessibility Remediation Simple
If you’re a small or mid-sized business owner, you’ve probably heard stories about other businesses getting hit with ADA (Americans with Disabilities Act) web accessibility lawsuits. Often, these lawsuits come out of nowhere, catching website owners by surprise. You might not even know what you did wrong, why your site was targeted, or how to fix it. It’s frustrating, and it’s scary. Even if you haven’t faced a lawsuit yet, you could be worried about your level of risk. Nobody wants a legal headache—especially not when you’re already juggling everything else that goes into running a business.

Here at 216digital, our goal is to change the conversation around web accessibility. We help small to mid-sized businesses protect themselves from costly accessibility lawsuits while also making websites more inclusive for everyone. Instead of quick fixes that only look good on the surface, we focus on lasting solutions through real accessibility remediation. By partnering with us, you’re not just avoiding legal trouble—you’re also improving every visitor’s experience on your site. Good access equals good business.

In this article, we’re going to break down what web accessibility actually means, how our services work, and why our people-focused approach sets us apart from companies that might rely on short-term, fear-based tactics. We’ll also show you how to schedule a free ADA briefing so you can gain clarity on your level of risk and figure out the next steps to make your site welcoming to all.

What Is Web Accessibility, Really?

Understanding the Basics

The term “web accessibility” can feel intimidating if you haven’t delved into it before. But when you boil it down, it’s quite straightforward: web accessibility means designing and updating your website so that people with disabilities can use it just as smoothly as everyone else. This includes visitors who use screen readers, rely on keyboard navigation, need larger text, or have other accessibility requirements.

Accessibility Helps Everyone

Making a site more accessible often has bonus benefits for everyone. For example, clearer website structure can improve your overall user experience, boost your SEO (search engine optimization), and make your site more user-friendly across different devices. In other words, meeting accessibility standards isn’t just about legal risk—it’s also about creating a smoother experience for all your visitors. That’s why accessibility remediation is such a critical part of a business’s digital strategy.

The Problem: Why Lawsuits Are Happening

Why the Legal Risk Is Growing

Over the past few years, courts have increasingly treated websites as “places of public accommodation,” meaning they fall under rules that require them to be accessible to people with disabilities. This has led to a spike in legal actions against businesses—some well-intentioned (from people who genuinely can’t access certain sites) and others more opportunistic, aiming to force quick settlements.

Proactive Prevention with Remediation

Either way, if your website has accessibility barriers, you could end up with a lawsuit or a demand letter. That often means paying lawyer fees, making sudden updates to your site under intense time pressure, and dealing with stress you never saw coming.

At 216digital, our approach is all about preventing these problems before they happen. Through comprehensive accessibility remediation, we don’t want you to face that unexpected expense or crisis moment. Instead, we want to set you up for success by making sure your site meets recognized accessibility standards in a thorough, sustainable way.

How 216digital Helps You Meet Accessibility Standards

1. Risk-First Approach: Stop Lawsuits Before They Start

When you bring us on board, we don’t just run a quick scan of your site and hand you a list of potential problems. A quick list is a start, but it doesn’t actually fix anything. Instead, we take a risk-first approach. We identify the areas of your site most likely to trigger a lawsuit and tackle them right away. This rapid response significantly reduces your potential exposure.

From there, we proceed through the rest of your site, ensuring all content and functions align with trusted accessibility standards. That way, you’re not left vulnerable to new complaints popping up in the future. That’s the difference between surface-level adjustments and meaningful accessibility remediation.

2. Full WCAG Implementation (The Gold Standard for Accessibility)

If you’ve done even a little reading on accessibility, you’ve likely seen mention of WCAG (Web Content Accessibility Guidelines). Judges, lawyers, and advocacy groups generally refer to WCAG 2.1 for determining whether a site is accessible. These guidelines cover areas like color contrast, text size, navigation, labels, and much more—essentially the nuts and bolts of a properly accessible website.

At 216digital, we don’t guess at what might be acceptable; we follow a systematic process to ensure your site aligns with WCAG 2.1 AA standards. We conduct thorough manual reviews along with automated checks to verify real-world accessibility, not just box-ticking. Our team’s hands-on accessibility remediation work results in a site that is recognized as accessible by the broader web community.

3. Ongoing Monitoring with a11y.Radar

A frequent misconception is that fixing accessibility barriers is a one-time job. In reality, websites are ever-evolving. You add new pages, adjust your site design, or change your content management system. Each of these updates can unintentionally introduce fresh barriers or break fixes you’ve made in the past.

That’s why we built a11y.Radar. It’s our specialized monitoring tool that consistently keeps an eye on your site, even after you’ve addressed the initial round of accessibility issues. a11y.Radar periodically checks if new problems have cropped up or if previously fixed areas have broken. With this in place, your accessibility remediation efforts stay intact, and you can relax, knowing you’re not being blindsided by hidden hurdles.

4. Hands-On Guidance and Support

Technical expertise is crucial, but we believe that easy-to-understand communication is just as important. Our team provides one-on-one support and guidance, answering questions you have about accessibility guidelines, legal implications, and the practical steps to ensure your site meets the right standards.
- Plain-Language Explanations: We won’t drown you in legal or tech jargon.
- Training Resources: If your developers or content team need training to maintain accessibility remediation practices, we’re happy to help.
- Personalized Assistance: Every website is different, so we don’t force you into a cookie-cutter solution.
We want you to feel confident about your site’s accessibility, not left in the dark about what’s happening behind the scenes.

Why We’re Different from Other Accessibility Companies

We’re Not Selling Fear—We’re Solving a Real Problem

Let’s be honest: lawsuits are a genuine risk, and the ADA is taken seriously in court. But 216digital’s mission is to educate you, not terrify you. We want to give you a clear understanding of what’s at stake and how you can proactively protect your business. Scare tactics aren’t our style. Instead, we rely on proven, professional accessibility remediation to resolve real issues.

No Overlays, No Shortcuts

Some companies push accessibility “overlays” that claim to magically solve every potential issue. While these might address a few surface-level features (like text resizing or color contrast toggles), they rarely fix deeper code-level or structural issues—and sometimes even introduce new difficulties.

At 216digital, our philosophy is to fix your site at the source. We go into the code and address each issue thoroughly. Yes, it’s more work. But the results are genuine and reflect real progress that stands the test of time. That’s the power of full-scale accessibility remediation.

We’re a Small Team That Cares

We’ve been around for more than 25 years. In that time, we’ve supported hundreds of businesses across industries, from e-commerce shops to local service providers. We know what it’s like to run a small or medium-sized business, and we treat your goals and concerns with respect. We’re also proud to say we’re a tight-knit crew. When you call us, you’ll speak to real people who care about your success—and who care deeply about getting your accessibility remediation right.

Ready to Talk? Let’s Schedule Your ADA Briefing

Worried your website might have accessibility barriers? Not sure if you’re at risk for a lawsuit? We offer a free ADA briefing to help you figure out your next move. It’s a no-pressure conversation where you’ll learn what’s really happening on your site and how we can help.
- Site Assessment: We take a basic look at your site to spot any glaring red flags.
- Risk Overview: We talk about possible risks that could leave you open to legal action.
- Options & Timeline: We lay out what solutions might look like, with a sense of how long and how much effort they might take.
We’re not here to push a sales pitch—just to share our expertise and help you make the best decision. If you decide to work with us, awesome! If not, at least you’ll walk away with a clear understanding of your situation and how to move forward.

If you’re ready to stop wondering about your site’s accessibility status and start taking proactive steps, reach out to schedule your free ADA briefing. We’ll explain everything you need to know in a straightforward, understandable way. Fill out our contact form below or schedule online today at 216digital.com/ada-briefing. We can’t wait to hear from you and show you how simple real accessibility remediation can be.
Greg McNeil

April 7, 2025

Testing & Remediation

Accessibility, Accessibility Remediation, Accessibility testing, automated testing, Web Accessibility, Web Accessibility Remediation, Website Accessibility
eCommerce Accessibility: Cart & Checkout Best Practices
As a front-end developer, you already know how much the small stuff matters—clear labels, logical tab order, and meaningful feedback. These details don’t just polish the experience; they make the difference between a site that works for everyone and one that silently shuts people out. When it comes to eCommerce accessibility, gaps tend to show up in the usual suspects: shopping carts, forms, payment flows, and filters.

Below, we’ll explore common eCommerce accessibility gaps and show you how to fix them. You’ll see examples of HTML and ARIA attributes that make a real difference in usability—without requiring you to overhaul your entire site. Just clean, thoughtful code that helps your work reach more people, the way it’s meant to.

Why Accessibility Matters in E-Commerce

Better eCommerce accessibility results in a better user experience. When you streamline navigation, label form fields properly, and offer multiple payment methods, you’re benefiting everyone, not just shoppers with disabilities. You’re also opening your doors to more customers, including those who use screen readers, have limited mobility, or simply prefer an intuitive layout.

Beyond enhanced usability, there’s also the legal side. Lawsuits related to eCommerce accessibility are on the rise. Addressing accessibility from the start can help reduce legal risks, but the bigger win is ensuring all potential customers feel welcome in your store.

eCommerce accessibility often breaks down at a few critical points:
- Shopping carts with unclear or missing labels.
- Forms and checkouts that don’t offer proper error messages.
- Payment flows that are dependent on inaccessible CAPTCHAs or limited payment methods.
- Product filters that are keyboard-incompatible or lack clear feedback.
If you’re a developer responsible for these features, you’re in the perfect position to fix these problems. A few strategic lines of code or well-placed attributes can help transform a confusing checkout into a seamless experience for all.

Making Your Shopping Cart Work for Everyone

Add Clear Labels (Yes, Even for Buttons)

It’s a common oversight to have buttons or icons without descriptive text. Screen readers can’t interpret an icon unless you provide an aria-label or similar attribute. Give every button clear text or an invisible descriptor for assistive tech.
```
<button aria-label="Remove item from cart">
  Remove
</button>
```
This simple step ensures that anyone using a screen reader knows exactly what action they’re about to take.

Let People Update Cart Items Without Guesswork

Quantities, item removals, and other cart updates should be straightforward. If you’re using a numeric input, label it properly so a screen reader user knows what they’re adjusting.
```
<label for="quantity">Quantity:</label>
<input type="number" id="quantity" name="quantity" min="1" value="1">
```
When quantity fields are clearly labeled and keyboard-friendly, customers can adjust items easily—no mystery involved.

Show Helpful Feedback When Things Go Wrong

Errors happen: maybe a shopper enters an invalid quantity or tries to remove an item that’s no longer in stock. Instead of reloading the entire page (and frustrating users), use an aria-live region to announce errors in real-time:
```
<div role="alert" aria-live="assertive">
  Error: Please enter a valid quantity.
</div>
```
This alerts people using screen readers without forcing them to refresh or hunt for an error message.

Shipping Forms That Are Easy to Use (and Easy to Navigate)

Use Straightforward, Consistent Labels

Forms can become confusing if users aren’t sure what to type. Proper <label> tags tied to the correct inputs make a huge difference for both sighted customers and those using assistive tech.
```
<label for="address">Shipping Address:</label>
<input type="text" id="address" name="address">
```
When labels are descriptive and consistent throughout the form, everyone knows exactly what information to provide.

Make Sure Users Can Tab Through Fields Logically

Keyboard-only users often navigate by pressing the Tab key. If your form fields aren’t in a logical sequence, they’ll jump around unpredictably. Paying attention to the natural DOM order is usually enough, but if you must alter it, use tabindex carefully.

Show Errors Clearly and Offer Suggestions

Generic error messages like “Invalid input” force users to guess what they did wrong. Instead, offer specific guidance so people know exactly how to fix the issue:
```
<div role="alert">
  Error: ZIP code must be five digits.
</div>
```
This clarity benefits everyone, speeding up the checkout process and reducing frustration—two big wins for eCommerce accessibility.

Designing a Payment Flow That’s Smooth and Inclusive

Offer More Than One Way to Pay

Variety in payment methods—credit cards, PayPal, Google Pay, Apple Pay, etc.—ensures different shoppers can complete purchases in a way that suits them. Some assistive technologies work better with certain payment platforms, so having options expands your customer reach.

If You Use CAPTCHAs, Make Them Accessible

Nothing derails a checkout faster than an inaccessible CAPTCHA. If possible, rely on server-side checks. If you do need a CAPTCHA, consider offering an audio version or a more user-friendly alternative. This prevents people with disabilities from being locked out at the final step of their eCommerce accessibility journey.

Choose Accessible Payment Gateways

Third-party payment platforms can introduce new accessibility issues. Do a quick review to ensure any external gateway meets basic WCAG standards and is compatible with screen readers and other assistive tools. Even the best checkout flow can fail if the final payment step isn’t accessible.

Don’t Let Product Filters Be a Barrier

Make Filters Keyboard-Friendly

Checkboxes, sliders, and dropdowns all need to be navigable via keyboard. That means ensuring users can Tab to each control, use arrow keys for sliders, and press Enter or Space to toggle checkboxes or confirm a selection.

Let Users Know What Filters Are Applied

Always make it clear which filters are currently active, both visually and programmatically (via ARIA attributes). This helps sighted users and people using screen readers track their selections and remove or adjust filters easily.

Stick to Native HTML Controls When Possible

While custom-styled checkboxes and radio buttons can look appealing, they often introduce accessibility quirks. Native HTML elements are easier to make accessible:
```
<fieldset>
  <legend>Filter by Size</legend>
  <label><input type="checkbox" name="size" value="small"> Small</label>
  <label><input type="checkbox" name="size" value="medium"> Medium</label>
  <label><input type="checkbox" name="size" value="large"> Large</label>
</fieldset>
```
You can style them to fit your brand while ensuring they work out of the box for most assistive tech. It’s one of the easiest ways to improve eCommerce accessibility.

Testing and Validating Your Work

Start with Automated Tools (But Don’t Stop There)

Tools like Google Lighthouse and WAVE are great starting points. They scan for many common issues, but automated tests can’t cover everything, especially more nuanced user interactions.

Test Manually with Real Assistive Tech

Grab a screen reader like NVDA (Windows) or VoiceOver (Mac). Try using only your keyboard to navigate the site. This hands-on approach reveals a lot about real-world usability that automated checks might miss—especially in areas related to eCommerce accessibility.

Get Feedback from Real Users

If you can, involve people with disabilities in your testing. Their direct experience helps pinpoint issues you might never notice on your own. Real-world feedback is invaluable for refining the shopping journey.

Small Fixes, Big Impact

Building an accessible eCommerce site doesn’t require a complete overhaul. Most improvements, like adding clear labels or structuring forms properly, are quick, incremental changes in your code. These small fixes can significantly enhance the experience for shoppers who rely on assistive technology—and often make the site more pleasant for everyone else as well.

If you want more detailed guidance or an expert review, there are plenty of resources on WCAG and web.dev. You can also team up with 216digital, where we specialize in making sure online stores meet eCommerce accessibility standards from start to finish. Whether you need help with checkout flows, product filtering, or a full-site audit, our team is here to ensure every shopper can complete their purchase with ease.

Remember: inclusive design isn’t just a checkbox—it’s a mindset. By prioritizing eCommerce accessibility at each step of your development process, you’ll build online shopping experiences that truly welcome everyone. And that’s good business for everyone involved.
Greg McNeil

April 4, 2025

How-to Guides

Accessibility, ecommerce website, How-to, WCAG Compliance, Web Accessibility, web developers, web development, Website Accessibility

Why Broader Accessibility Training Matters

Who Should Learn—and What They Need to Know

1. Executives and Senior Leaders

2. Designers and UX Teams

3. Developers and Engineers

4. Content Creators and Editors

5. Marketers and Social Media Managers

6. Quality‑Assurance Testers

7. Product and Project Managers

8. Customer Support Teams

Building a Culture of Learning

Choosing the Right Accessibility Training Format

Measuring Success

Overcoming Common Roadblocks

Getting Started: A Quick Action Plan

Equip Your Team, Elevate Your Experience

Accessibility Training That Moves Teams Forward

Invisible Obstacles: Why Documents Trip People Up

1. Missing or Misused Headings

2. When PDFs Are Just Pictures

3. Color Contrast That’s Too Subtle

4. Vague Link Text

5. Images Without Alt Text

6. Tables That Don’t Translate

7. Lists That Don’t Act Like Lists

8. Use Clear Language and Layout

9. Choose the Right Export Settings

10. Provide Alternative Formats

Beyond the Basics: Keep Creating Accessible Documents

Make Your Documents Work for Everyone

Why Accessibility Matters

Reaching Every Visitor

Reducing Legal Risk

What Is an Accessibility Audit?

The Accessibility Audit Process: Step-by-Step

Initial Consultation & Scope Definition

Automated Testing

Manual Evaluation

User Testing with Assistive Technology

Documentation of Findings

Prioritization of Issues

Remediation Recommendations

What Happens After the Audit?

Implementing Fixes

Team Training

Ongoing Monitoring

Your Website’s Future Just Got Brighter

What the CCPA Introduced to U.S. Businesses

A Ripple Effect Beyond California

The GDPR: Setting the Global Standard

Core GDPR Requirements:

GDPR vs. CCPA: Two Paths, One Direction

Who’s Affected?

Consumer Rights

Consent Models

A Growing Patchwork of U.S. Laws

What You Can Do Now

1. Map Your Data

2. Strengthen Your Privacy Policy

3. Build in Flexibility

4. Respect User Rights

5. Lead with Transparency

Final Thoughts

Unpacking aria-describedby

Why It’s Important

When Should You Use aria-describedby?

When Not to Use It

Code Walkthroughs: Real-World Examples

Form Fields

Password Requirements

Error Messages

Multiple Descriptions

Buttons

Destructive Action Explanation

Dialogs and Modals

Accessible Dialog

Tooltips and Live Regions

Accessible Tooltip

Status Messages

Common Mistakes to Avoid