Web Accessibility Remediation Archives/Category

Is Accessibility in Your Marketing the Missing Link?
Marketers love to talk about connection—finding that message, tone, or moment that really lands. Yet for years, accessibility sat on the sidelines. It was something teams circled back to after launch, if they got to it at all.

But bringing accessibility into the creative process from the start changes that. It refines ideas, sharpens the message, and makes the experience easier to use. Reach grows not by pushing harder, but by removing the barriers that hold people back.

Most of us weren’t taught to work this way, and that’s understandable—marketing has often moved faster than the systems built to support it. But that’s beginning to change. This article explores how accessibility in marketing is reshaping the creative process itself—and how embracing it can make our work not only more inclusive, but more effective and enduring.

Why Accessibility Belongs in Your Marketing Roadmap

Accessibility isn’t a new idea, but it’s finally being recognized as a core part of communication strategy. One in five adults lives with a disability that affects how they engage online. When we design with those experiences in mind, we don’t just improve access—we improve clarity, usability, and trust for everyone.

The Business Case for Accessibility

Accessibility pays off in ways that are both practical and measurable:
- Wider reach: When more people can access your content, your audience grows naturally.
- Stronger SEO: Structured headings, alt text, and transcripts help search engines—and people—understand your message.
- Higher engagement: Clear layouts, legible text, and captioned videos make it easier to stay connected.
- Better retention: Usable design keeps people from bouncing away in frustration.
- More trust: When users feel considered, they’re more likely to return and recommend.
The Risk of Leaving Accessibility Out

Ignoring accessibility comes with its own set of costs. Legal frameworks like the ADA and WCAG continue to expand, but reputation often carries the higher stakes. Inaccessibility doesn’t just cause frustration—it signals that some users weren’t considered. Building inclusivity into your work helps prevent that, and it strengthens credibility over the long term.

Understanding why accessibility matters is only half the story. The next step is making it part of how your team actually works—building it into everyday processes so it becomes second nature.

Building Accessibility into Your Marketing Workflow

You don’t need to overhaul your entire process to make it accessible—you just need to integrate it into the one you already have. Accessibility works best when it’s treated as a mindset that travels through every stage of a project.

Start Early

Bring accessibility into the conversation from the first meeting. Talk about things like contrast, reading level, captions, and structure while you’re still shaping creative direction. When inclusion is part of the plan from the start, it stops feeling like a post-production fix.

Create Together

Accessibility thrives when everyone contributes:
- Writers can use plain, active language and clear CTAs that describe the next step.
- Designers can choose accessible color palettes, scale type properly, and maintain consistent structure.
- Developers can ensure forms, buttons, and navigation work for keyboard users and assistive technologies.
When every role takes ownership, accessibility becomes a shared value rather than a box someone else has to check.

Test Before Launch

Automation helps, but people matter more. Run your pages or campaigns through accessibility tools like WAVE or Lighthouse, then do a manual pass. Navigate with a keyboard, listen to your content through a screen reader, and check if the flow feels intuitive.

Maintain a short, clear accessibility guide that lives where your team works. It doesn’t need to be heavy-handed—just a practical reminder of how to write alt text, structure headings, or format captions consistently.

Where Accessibility in Marketing Matters Most

Website

Your website is your primary channel—and often the first impression of your brand’s care for its audience.
- Keep headings structured (H1–H6) for both readability and SEO.
- Use descriptive alt text that communicates meaning, not just appearance.
- Maintain color contrast ratios of at least 4.5:1.
- Label form fields clearly, and include helpful error messages that explain what went wrong.
- Make sure interactive elements like sliders and pop-ups are keyboard-friendly.
Email and Newsletter

Email accessibility keeps your content inclusive across devices and inboxes.
- Use responsive templates that stay readable up to 200% zoom.
- Keep essential information in text, not images.
- Write subject lines that are short, descriptive, and easy for screen readers to interpret.
- Include a plain-text version of every email for those who need or prefer it.
Social Media

Accessibility on social media helps your message reach everyone—without changing your tone or style.
- Use CamelCase for hashtags (#AccessibleMarketing).
- Add alt text to images and captions to videos.
- Limit emoji use and place them at the end of sentences.
- Avoid stylized fonts that break accessibility tools.
Each platform has its nuances—alt text on Instagram, captions on TikTok, numbered threads on X (Twitter)—but the principle remains the same: good communication should never rely on one sense alone.

Designing for Comfort and Clarity

No matter where your campaigns live—web, email, or social—good design ties it all together.

Accessible design isn’t about restraint—it’s about intention. Every design choice shapes how someone experiences your message.
- Plain language makes ideas easier to follow without losing personality.
- Descriptive links replace uncertainty with confidence.
- Predictable structure creates a sense of ease and familiarity.
- Accessible visuals ensure infographics and charts aren’t barriers.
- Visible focus indicators and balanced contrast guide users naturally through the experience.
When accessibility becomes part of your creative language, the result feels more human—not less artistic.

Testing and Improving Accessibility

Accessibility testing is less about perfection and more about awareness. Run quick automated checks to catch common errors, then explore your content as your users would. Can you navigate without a mouse? Does the text hold up when zoomed in? Does the order make sense when read aloud?

Invite people with disabilities to test your work when possible. Their lived experiences surface the details that automation can’t. Over time, track metrics like caption coverage, alt text completion, and user feedback. Accessibility can be measured—and it can show real progress.

Keeping Accessibility in Motion

Accessibility isn’t a one-time effort. It’s a practice that builds momentum through consistency.
- Schedule quarterly accessibility reviews for your highest-traffic content.
- Include accessibility checkpoints in every project template.
- Offer short, focused training sessions across writing, design, and development teams.
- Ask vendors and partners to share their accessibility documentation and compliance statements.
When accessibility becomes a shared responsibility, it naturally integrates into the way your team works.

Measuring What Matters

You’ll know accessibility is working when the results start showing up in familiar metrics:
- Engagement improves as more users interact with your content.
- Visibility rises through better SEO and structured content.
- Trust strengthens because your brand feels more considerate and reliable.
- Risk decreases because accessibility is built in—not retrofitted later.
Accessibility in marketing doesn’t slow creativity—it sharpens it. It makes every campaign perform better because it’s built for everyone from the start.

Accessibility as Ongoing Momentum

Every caption written, every alt tag added, every clear headline or color contrast adjustment is a step toward a better experience for your audience.

When accessibility is built into your creative process, your marketing becomes more durable, adaptable, and human. It’s not a trend—it’s a reflection of what good communication has always been about: connecting with people in a way that feels effortless and authentic.

If you’re ready to take the next step, consider scheduling an ADA briefing with 216digital. Our team helps organizations identify accessibility barriers and plan remediation strategies that make their websites and marketing more usable for everyone.
Greg McNeil

October 16, 2025

How-to Guides

Accessibility, Digital Marketing, How-to, Marketing, Web Accessibility, Website Accessibility

How to Create Accessible Dialogs and Modals

You’ve probably clicked a button that suddenly stopped everything — a pop-up asking, “Are you sure?”Or maybe you’ve seen a small info box appear off to the side — helpful, but never in the way. Both are dialogs, designed to grab attention in different ways.

Used well, dialogs create clarity and focus. Used poorly, they interrupt, confuse, and make people feel stuck.

The HTML <dialog> element makes these patterns easier to build than ever before. But accessibility isn’t built into the code — it comes from the decisions you make around it. The choice between a modal and a non-modal dialog affects more than layout. It shapes how people experience trust, control, and flow within your interface.

This guide looks at when to use each and how to design accessible dialogs that feel natural, respectful, and human-centered — helping everyone move forward with confidence.

Modals vs. Dialogs: Key Differences and Use Cases

Every dialog creates a moment — a small pause in the user’s flow. Some moments need all of a person’s attention; others just need to offer quiet support in the background. The real skill lies in knowing which one your design calls for.

What’s the Difference?

A modal dialog asks users to stop what they’re doing and make a choice before continuing. When opened with showModal(), it locks focus inside and disables the rest of the interface. That’s not a flaw — it’s intentional. Modals are meant to protect important steps: confirming a deletion, submitting a form, or saving something that can’t be undone.

A non-modal dialog, opened with show(), works alongside the main content. It might appear as a sidebar, filter panel, or help window — something that adds clarity without breaking the user’s rhythm. The rest of the page stays usable, giving people control over how and when to engage.

Both patterns have value. The difference isn’t technical — it’s about the kind of experience you want to create. Modals demand attention. Non-modals share it.

When to Use Each

Modal Dialogs	Non-Modal Dialogs
Confirming destructive or irreversible actions	Providing optional settings or filters
Displaying critical warnings or alerts	Showing help text or guidance
Collecting essential information, like passwords or payments	Offering contextual tools that enhance workflow
Presenting legal or security confirmations	Sharing reference information while users continue working

Advantages and Drawbacks

Type	Advantages	Drawbacks
Modal Dialogs	• Keeps users focused on what matters most. • Prevents data loss or accidental actions. • Creates clear decision points. • Makes sure critical alerts are seen.	• Interrupts workflow and momentum. • Can frustrate or confuse if overused. • Requires careful focus handling for accessibility.
Non-Modal Dialogs	• Supports multitasking and flow. • Reduces cognitive strain by giving users control. • Feels less intrusive and more flexible.	• Important details might go unnoticed. • Not ideal for high-stakes actions. • Can clutter layouts if poorly managed.

Choosing the Right Type

When deciding between the two, ask yourself:

Does this moment need to stop the user, or simply guide them?

Use modals when you need someone to confirm, commit, or acknowledge something before moving on.
Choose non-modals when the goal is to assist or inform without interrupting their process.

Both serve accessibility — just in different ways. A well-timed modal can prevent errors. A well-designed non-modal can preserve flow. The goal isn’t to eliminate interruptions altogether, but to make every one of them intentional.

Accessible dialog design starts with empathy. Think about how people move through your interface — how they regain focus, how they understand what just appeared, and how much control they still have. When you build from that mindset, you’re not just meeting standards. You’re respecting your users’ attention, time, and agency.

Building Accessible Dialogs: From Code to Experience

Creating accessible dialogs isn’t about adding extra layers of code — it’s about protecting clarity and ease of use. The HTML <dialog> element already gives you a strong starting point. What you do next determines whether the experience feels effortless or confusing.

Start with Solid HTML

HTML gives you two built-in paths:

showModal() creates a modal dialog.
show() creates a non-modal dialog.

Both handle basic focus and background behavior automatically. From there, it’s all about refinement.

Always include a clear, labeled close button — and make sure it returns focus to the element that opened it.

<button id="close-dialog">Close</button>
<script>
  document.querySelector('#close-dialog')
    .addEventListener('click', () => myDialog.close());
</script>

It’s a small step, but it reinforces something bigger: giving users control — the foundation of every accessible experience.

Label Everything Clearly

Assistive technology depends on structure that makes sense. Every dialog should announce what it is, why it’s there, and how to leave it.

<dialog aria-labelledby="dialog-title" aria-describedby="dialog-desc">
  <h2 id="dialog-title">Confirm Action</h2>
  <p id="dialog-desc">This will permanently delete the record.</p>
</dialog>

If it’s an urgent message, add role="alertdialog" so screen readers read it immediately. Otherwise, keep the default role and double-check that:

The title and description are linked with aria-labelledby and aria-describedby.
The close button is labeled with text, not just an icon.
Focus moves logically when the dialog opens and closes.

When these pieces work together, the dialog doesn’t just appear — it communicates clearly, with purpose and respect.

Keep Focus on Track

Focus is where accessibility either shines or breaks.

When a dialog opens, the user’s focus should land directly inside it. When it closes, focus should return to the element that triggered it.

dialog.addEventListener('close', () => trigger.focus());

A few extra checks help keep that flow intact:

Tab and Shift+Tab should only move through active elements inside the dialog.
Escape should always close it.
Every interactive element should have a visible focus indicator.

If you’ve ever been trapped inside a modal with no way out, you already know why this matters. Freedom of movement — even within a small overlay — is core to accessibility.

Prevent Background Scrolling

When a modal appears, the world behind it should stay still.
Allowing the background to scroll while a dialog is open can disorient users, especially those relying on visual context or assistive technology.

A simple CSS rule can make all the difference:

body.modal-open {
  overflow: hidden;
}

Toggle that class when opening and closing the dialog. It’s a subtle fix that steadies the visual environment and prevents confusion — small detail, meaningful improvement.

Design for Visual Calm

Accessibility isn’t only technical — it’s visual. A dialog should direct attention, not demand it.

Use gentle layering, thoughtful contrast, and spacing that feels natural.

dialog::backdrop {
  background-color: rgba(0, 0, 0, 0.65);
}

Follow WCAG contrast guidelines:

4.5:1 for normal text
3:1 for large text

Soft shadows, calm edges, and balanced spacing help users focus on content without feeling overwhelmed. A well-designed dialog doesn’t shout — it invites. It says, “Look here, when you’re ready.”

That’s what visual accessibility feels like — respectful, intentional, and human.

Best Practices for Accessible Dialogs

Accessibility isn’t just about getting the mechanics right — it’s about how the experience feels. These best practices go beyond compliance to help you design accessible dialogs that feel considerate, consistent, and calm.

1. Keep Users Oriented

People should always know where they are. On larger screens, let a touch of the background remain visible so the dialog feels connected to the page. On mobile, a full-width layout often works better for readability and touch targets.

It’s about maintaining orientation — helping users feel connected to where they are, not suddenly somewhere else. When context stays visible, confidence follows.

2. Offer Multiple Ways Out

A good dialog respects autonomy. There should never be a sense of being trapped.

Include a clearly labeled “Close” button, let the Escape key work naturally, and if clicking outside dismisses the dialog, make sure screen readers announce that it closed.

The best dialogs don’t just let people leave — they make that exit easy to find, every time.

3. Use Restraint with Motion

Animation should support, not distract. Avoid heavy fades, blurs, or large shifts that feel like the page vanished.

A dialog should feel like a step forward, not a teleport. Subtle transitions — a soft fade or gentle scale — help users stay oriented and avoid triggering motion sensitivity.

If it feels smooth and steady, you’re doing it right.

4. Test Like a Real User

Once the dialog looks good, use it the way your audience will.

Try it with only a keyboard.
Run it with NVDA or VoiceOver.
Zoom in to 200% and see if anything disappears or becomes unreadable.

If something feels clunky or confusing, it is. Real testing turns assumptions into insight — and that’s where true accessibility takes shape.

5. Respect Timing and Intent

Never open modals automatically or stack several in a row. Give people time to think, act, and close things at their own pace.

Accessibility is as much about emotional comfort as it is about usability. Respecting timing and intent helps users feel calm and in control. That’s what good design does — it builds trust through patience.

Accessibility Beyond the Dialog

Dialogs and modals are moments of conversation between your site and your users. When they’re done right, they help people act confidently and stay in flow. When they’re not, they create friction and fatigue.

The best accessible dialogs are quiet — they guide without getting in the way. They respect focus, timing, and attention so users never have to think about accessibility; it’s already part of the experience.

At 216digital, we see accessibility as communication done right — designing in a way that includes everyone from the start. If your team is ready to move beyond checklists and create digital experiences that truly connect, schedule an ADA briefing with us today. Together, we’ll make accessibility a natural, lasting part of how your organization grows.

Greg McNeil

October 15, 2025

How-to Guides

Accessibility, accessible dialogs, How-to, web developers, web development

Can a Command Line Be Accessible by Design?
If you’ve spent any time in development, you know the command line is where things get real. It’s efficient, fast, and—let’s be honest—satisfying. That single blinking cursor has powered decades of progress. From deploying servers to pushing commits, the command line is still where we get work done.

But for all its simplicity, it isn’t always as accessible as it seems. Yes, it’s text-based. Yes, it’s keyboard-driven. Yet those strengths can be deceiving. For developers who rely on screen readers or braille displays, a CLI’s clean look can hide a mess of barriers: missing structure, unreadable tables, spinning animations that never speak.

Accessibility isn’t just a web problem—it’s a design principle. When a command line is an accessible CLI, it becomes what it’s always meant to be: a tool for everyone to build, create, and solve problems efficiently.

Why Accessibility Still Matters in the Command Line

A 2021 study by Google researchers Harini Sampath, Alice Merrick, and Andrew Macvean took a closer look at command-line accessibility for developers with visual impairments. What they found might surprise you: CLIs, for all their strengths, are far from friction-free.

Participants could technically complete tasks—but it took significantly more effort, time, and patience than expected. The issue wasn’t skill. It was design. CLIs are, by nature, streams of text with no built-in structure for assistive technology to interpret. There are no headings, no semantic anchors, no easy ways to navigate.

One developer summed it up perfectly: the CLI “works, but it’s tiring.” Most found themselves building workarounds—copying output into Notepad, exporting text to a browser, or writing custom scripts to make data readable.

And that’s really the heart of it: accessibility isn’t just about whether something can be used. It’s about whether it can be used well. That’s where building an accessible CLI from the start changes everything.

Where the Command Line Trips Up—and How to Fix It

The study’s findings highlight some clear patterns that every CLI developer can learn from. None of them require reinventing the wheel; they just ask for intention.

1. Structure Matters More Than You Think

We tend to think of text as automatically accessible—but not all text is equal. The command line outputs everything as flat strings. There’s no hierarchy, no markup, and no way for screen readers to interpret context.

Take man pages. They look structured, with headings and sections, but to a screen reader they’re just one long stream. Users can’t jump between sections or skim efficiently. Many developers in the study said they avoid man pages entirely and rely on web docs instead.

A simple solution? Offer structure where it’s missing:
- Provide HTML or Markdown versions of documentation.
- Add export options (--help-html, --manual-online).
- Allow users to format output as CSV or JSON for easy navigation.
A truly accessible CLI doesn’t stop at giving you data—it gives you data you can navigate.

2. Tables and Long Outputs Need Rethinking

Tables are a classic offender. They look organized, but they’re actually just rows of text spaced apart. For a screen reader, that structure disappears. Developers have to mentally map where each number belongs, remembering what every column represents.

That’s not accessibility—that’s endurance.

Better approaches include:
- A --flat or --no-table flag to simplify output.
- Options to export to structured formats (--output=csv, --output=json).
- Including clear, readable headers for every data point.
And for those endless command outputs? Let users redirect text to a file automatically (--export, --logfile, --view-html). Searching or filtering shouldn’t require stepping out of accessibility tools just to get the job done.

These simple changes turn a good CLI into a genuinely accessible CLI—one that respects how different users interact with information.

3. Feedback Should Be Informative—Not Decorative

Developers love a good spinner or progress bar. But when screen readers encounter those fancy progress indicators, they usually read something like “dot dot dot dot fail.”

In Google’s study, one developer said it best: “I could tell something was happening, but I didn’t know what.”

Instead of simulating motion, communicate progress with plain, descriptive text:

“Deploying container… 50% complete.”

“Success: VM created.”

And always give users an escape hatch: flags like --no-animation or --static-output keep feedback clean without slowing anyone down. A smart, accessible CLI never assumes sight is the only way to know something’s working.

4. Make Error Messages Clear and Human

If you’ve ever seen a CLI error filled with regex syntax, you can imagine how that sounds when read aloud: “left bracket A dash Z right bracket…”? Not exactly clear.

Error messages in the study were one of the most common frustrations. Developers spent hours debugging issues that could’ve been solved with one plain-language sentence.

Here’s the fix:
- Describe what happened, not just what failed.
- Offer actionable next steps.
- Keep symbols and regex out of default messages—reserve them for verbose or debug modes.
The goal isn’t to oversimplify; it’s to make sure the message is usable by everyone who reads—or hears—it.

Practical Guidelines for Designing an Accessible CLI

The study concludes with recommendations that align perfectly with inclusive design best practices.

Here’s how to apply them in your next CLI project:
1. Provide HTML versions of documentation: Treat --help and man outputs as summaries, not full references.
2. Let users export long outputs: Make it easy to redirect results to text, HTML, or CSV.
3. Document output structures: Explain what your CLI prints before users run it—help them form a mental model.
4. Make tables convertible: Offer ways to flatten or export tabular data for screen reader compatibility.
5. Always include progress and status updates: Never assume silence equals success.
6. Use progress indicators that read correctly: ASCII art may look fun, but it sounds like noise.
7. Write error messages that are understandable aloud: Avoid shorthand or syntax that doesn’t translate when spoken.
An accessible CLI isn’t a niche feature—it’s a sign of thoughtful engineering.

Start Where Developers Live: The CLI

Here’s the takeaway: accessibility isn’t a bonus; it’s good design. The same features that help someone using a screen reader—structured data, consistent output, clear feedback—help everyone who uses your tool. They make automation cleaner, logs easier to parse, and development faster.

Most importantly, they remove the unnecessary friction that holds good developers back.

At 216digital, we see accessibility as the foundation of quality, not the final coat of paint. Whether it’s your website, software, or CLI, inclusive design starts with asking a simple question: Can everyone use this the way it’s meant to be used?

If you’re building developer tools and want to make them as efficient as they are inclusive, schedule an ADA briefing with 216digital. We’ll help you test, refine, and design CLIs that truly work for everyone—from the first keystroke to the final command.
Greg McNeil

October 14, 2025

How-to Guides

Accessibility, accessible CLI, How-to, Web Accessibility, web developers, web development, Website Accessibility
Product Media Accessibility: Are You Doing It Right?
Visuals drive e-commerce—they shape how customers understand, compare, and connect with products. But for users relying on screen readers or other assistive technologies, those visuals only work when paired with accurate alt text and accessible labels. Without them, key product details disappear, leaving users unable to engage or buy.

Accessibility also drives measurable results. Research shows that 71% of users with disabilities leave sites that present barriers, while inclusive design reduces bounce rates and builds trust. Search engines benefit, too—HubSpot reported a 779% increase in image traffic after optimizing alt attributes. And with nearly 15% of the global population living with a disability, accessible images open your storefront to a wider audience that can browse and buy without friction.

When done well, accessibility becomes more than a technical fix—it’s a competitive advantage. It improves visibility, trust, and conversion, all while making your brand easier for everyone to experience.

This guide explores what that looks like in practice—how to make product media accessible, where teams most often slip, and how to integrate accessibility into your daily workflow.

What Makes a Product Media Accessible

High-quality product media isn’t just about presentation—it’s about communication. Every image should help shoppers understand your product, evaluate their options, and make confident decisions.

In accessible design, that means ensuring every photo, color variant, and product angle can be understood not only visually, but also through assistive technology.

Below are the key principles that make product media both effective and accessible.

1. Clear and Descriptive Alt Text

Alt text gives images meaning. Without it, assistive technologies have nothing to announce—and essential product details disappear. Descriptive alt text ensures that shoppers who rely on screen readers can access the same information as anyone else.

When written thoughtfully, alt text also supports SEO, helping search engines understand what’s being shown and improving how your products appear in image searches.

If you’re coding manually, add the alt attribute directly to your <img> tag:
```
<img src="example.jpg" alt="A description of the image">
```
Keep descriptions concise but specific, focusing on what’s visually relevant to the shopper.

For those using a CMS like Shopify, WordPress, or Magento, you can add this text in the Alt Text or Alt Description field during upload. Many platforms support bulk editing—an efficient way to replace missing or generic alt text and ensure consistency across your catalog.

When Product Media Need Alt Text (and When They Don’t)

Product photos are the foundation of any e-commerce experience. They convey material, color, and quality—all the details a shopper depends on. Because of that, almost every product media needs alt text.

The only exception is when an image adds no new visual information—for instance, when showing the same product from another angle without revealing new features or details.

Redundant Product Views

Multiple images of the same item are common: front, back, side, or top-down shots. These angles help sighted users but can become repetitive when read aloud by screen readers.

If each image shows the same product with no meaningful change, you can mark the duplicates as decorative with an empty alt attribute:
```
<img src="product-side.jpg" alt="">
```
This signals assistive technologies to skip the image without disrupting the experience. Just ensure that at least one image—usually the primary product photo—has full, descriptive alt text.

Does Your Image Need Alt Text?

If an image adds context or new information that could influence a shopper’s decision, it must have its own alt text.

Ask: Would this image help someone understand or evaluate the product differently? If so, describe it.

Examples include:
- Different colors or finishes:
  “Red ceramic table lamp with linen shade” vs. “Blue ceramic table lamp with linen shade.”
  Each variant should have distinct alt text.
- Unique features or components:
  If an image highlights stitching, a removable part, or a texture, mention it briefly.
- Lifestyle or context photos:
  When a photo shows the product in use—like a jacket being worn or a sofa in a living room—include that context to communicate scale and purpose.
- Images with embedded information:
  If an image includes text such as a sale banner, sizing chart, or label, that information must also appear in alt text or nearby HTML. Screen readers cannot interpret text embedded in images.
Writing Effective Alt Text

Good alt text is concise, factual, and written with purpose. It shouldn’t describe every detail—just what matters to understanding the product.

Best practices include:
- Keep descriptions under 125 characters when possible.
- Avoid phrases like “image of”—screen readers already announce it.
- Use specific, factual terms: “brushed,” “polished,” “textured,” “matte.”
- Mention what changes between images, such as angle or color.
- Adjust wording for context—a banner image may need different phrasing than a gallery thumbnail.
A consistent alt text style guide helps teams stay aligned, especially when managing large catalogs or working across departments.

2. Optimizing Product Media Formats for Accessibility

Accessibility also depends on clarity and performance. Large, slow-loading images can undermine user experience, particularly on mobile.

Use formats that balance quality and speed:
- WebP delivers high-quality visuals with efficient compression, improving load times.
- SVG is ideal for scalable graphics such as logos or icons, maintaining crispness on any screen size.
Fast, responsive images ensure your store remains usable across devices and assistive technologies alike.

3. Avoiding Text Embedded Within Images

If an image includes text—like promotional banners, product specs, or sale messages—screen readers can’t interpret it.

Keep all essential text in HTML or nearby captions.
If embedded text is unavoidable, repeat the information in the image’s alt text or elsewhere on the page so that it’s accessible to every shopper.

4. Maintaining Visual Clarity and Contrast

A clean, modern aesthetic is appealing—but not if it sacrifices visibility.

Low-contrast product photos (for instance, light gray items on a white background) can be difficult for users with low vision to see.

Maintain at least a 4.5:1 contrast ratio between the product and its background. Adding subtle shadows, reflections, or gradient overlays can improve visibility without compromising your design aesthetic.

5. Labeling Interactive Product Media

Any clickable image or icon—such as a “zoom” button, “add to cart” symbol, or “view gallery” thumbnail—should have an accessible name or aria-label.

Describe the action, not the appearance:
- “Zoom product image”
- “Add to cart”
- “Open gallery view”
These small details help users navigate your site predictably and confidently, no matter how they interact with it.

Testing Tools and Workflow Integration

Accessibility isn’t a one-time audit—it’s an ongoing habit built into your development process.

Automated tools:
- WAVE and Lighthouse in Chrome DevTools identifies barriers and improvement tips for each image.
Manual checks:
- Test your pages with NVDA, VoiceOver, or JAWS to hear how descriptions are announced.
- Disable images in your browser and ensure text alternatives still convey essential information.
Workflow tip: Integrate accessibility validation into CI/CD pipelines. Use pre-commit hooks or CMS checks to block uploads missing alt attributes. Over time, this normalizes accessibility as part of the build process—not an afterthought.

Product Media That Speaks to Every Shopper

Accessible product media is about more than compliance—it’s about communication. Every shopper, regardless of ability, deserves the same opportunity to understand your products clearly and confidently.

From writing meaningful alt text to maintaining contrast and responsive performance, accessibility transforms static visuals into tools that inform, guide, and convert. It strengthens trust and creates smoother experiences across every device and interaction.

When your product media works for everyone, your brand stands out for the right reasons: clarity, quality, and care.

If you’re ready to assess your current approach or bring accessibility into your creative workflow, schedule an ADA briefing with 216digital. We’ll help you turn accessibility from a checklist into a lasting standard for digital craftsmanship.
Greg McNeil

October 13, 2025

How-to Guides

Accessibility, How-to, product media, WCAG, Web Accessibility, web developers, web development, Website Accessibility
Will H.R. 3417 Finally Clarify Accessibility?
Digital accessibility in the U.S. has always existed in a kind of fog. Everyone agrees it’s important, but the lingering question is simple: Does the ADA actually require my website or app to be accessible?

For years, that answer has depended on where you are and who you ask. Some courts say yes. Others hesitate. Agencies offer guidance but stop short of making it binding. For organizations trying to do the right thing, the result has been confusion—and a fair amount of frustration.

That may soon change.

H.R. 3417, known as the Websites and Software Applications Accessibility Act of 2025, is Congress’s latest effort to clear the air and make digital accessibility a matter of law, not interpretation. Let’s unpack what it aims to do, why it matters, and what steps you can take to prepare before it takes effect.

What the Bill Proposes

Introduced in May 2025 by Rep. Pete Sessions (R-TX), H.R. 3417 takes on something that’s been missing for far too long—a single, consistent standard for digital accessibility under the Americans with Disabilities Act.

It brings long-needed structure to how accessibility is defined and maintained online.

Under the bill:
- The Department of Justice (DOJ) would oversee regulations for Titles II and III, covering state and local governments as well as public accommodations.
- The Equal Employment Opportunity Commission (EEOC) would manage Title I, which is focused on employment.
Together, these agencies would be responsible for creating clear, enforceable rules—and updating them every three years so the law evolves alongside technology instead of chasing it.

Rooted in the POUR Principles

The framework builds on the four POUR principles that continue to shape accessibility standards worldwide:
- Perceivable: Information should reach people through more than one sense.
- Operable: Interfaces must respond to different types of input.
- Understandable: Content should be predictable, consistent, and easy to follow.
- Robust: It needs to work with assistive technologies—both now and as they advance.
These principles aren’t new, but their inclusion helps bridge the gap between policy and real-world design. It connects legislation to the human experience of using digital tools—the moments when clarity, contrast, and focus truly matter.

A Step Forward for Digital Inclusion

Advocacy groups, including the National Federation of the Blind and the American Council of the Blind, have voiced strong support for the bill. For many, it marks a long-awaited turning point—one that reinforces what accessibility professionals have long understood: inclusion isn’t limited to ramps and doorways. It belongs in every digital space where people work, learn, and live their daily lives.

Why H.R. 3417 Matters

When the ADA became law in 1990, the web wasn’t yet central to daily life. Today, nearly everything happens online—shopping, learning, applying for jobs, and even managing health care. Yet the law never clearly said how accessibility applies to the digital world.

Under Title III, businesses and nonprofits can’t discriminate. Yet there’s still no binding rule that defines what accessibility actually means for websites or apps. Courts have often relied on WCAG (Web Content Accessibility Guidelines) as a reference, but WCAG itself isn’t law. The result is a patchwork of interpretations and uneven enforcement.

H.R. 3417 would change that by replacing uncertainty with structure. It extends accessibility expectations to private businesses, nonprofits, and employment platforms—aligning them with the clarity already provided to public entities under the 2024 DOJ web rule for Title II.

It also ensures the right people are guiding the process. The bill requires an advisory committee—led primarily by individuals with disabilities—to help shape standards that work in real life, not just on paper.

What the Bill Would Do

At its core, H.R. 3417 says this: maintaining an inaccessible website or app would violate the ADA. No more gray zones. No more “we didn’t know.”

The DOJ and EEOC would create detailed accessibility standards—likely drawing from WCAG 2.2 Level AA or its successor—and require all covered entities to comply.

To make adoption realistic, the bill supports smaller organizations with grants up to $10,000, access to a technical assistance center, and longer compliance timelines—up to three years after the final rule takes effect.

It also preserves individuals’ right to sue if barriers remain. Courts could require fixes and award damages or attorney fees. To back it all, Congress plans to allocate $35 million per year for enforcement and oversight from 2026 through 2035.

Who’s Covered
- Employers and employment agencies (Title I)
- Public entities like state and local governments (Title II)
- Businesses, nonprofits, and testing providers (Title III)
That reach is broad—and that’s exactly the point. If you’re already subject to the ADA, your digital platforms will soon fall under the same expectations.

What H.R. 3417 Could Change

If passed, H.R. 3417 would finally give organizations a single, national rulebook for digital accessibility. It would eliminate the guesswork that’s led to years of inconsistent rulings and conflicting advice. For most organizations, that means a clearer sense of what compliance looks like—and how to plan for it.

It would also shift responsibility to where it belongs. For decades, people with disabilities have carried the burden of filing complaints and lawsuits to gain access. This bill would make accessibility an active obligation, not a reaction to litigation.

Of course, laws are only as strong as their enforcement. While the bill includes funding, it doesn’t yet specify how the DOJ or EEOC will prioritize or staff digital accessibility enforcement. Some expect a wave of early lawsuits—similar to what we saw with Section 508 and GDPR—but that initial pressure could drive lasting improvement.

The Act doesn’t explicitly address international harmonization either, though alignment with WCAG would naturally connect it to Europe’s EN 301 549 standard. That keeps global compliance more straightforward for companies working across borders.

The bottom line is that this bill sends a message that’s been coming for a long time—digital accessibility is no longer optional.

What Organizations Can Do Now

There’s no need to wait for the ink to dry—you can start preparing today.

Take a close look at your digital environment: your website, apps, internal portals, and documents. Ask the simple questions first. Can users navigate without a mouse? Are forms labeled clearly? Do videos include captions? Small discoveries today prevent bigger problems tomorrow.

Start With What Matters Most

Focus on the areas people use most—where they log in, fill out forms, or complete purchases. Fix the issues that stop someone from moving forward, like missing labels, alt text, or keyboard navigation.

Include Your Documents

PDFs and digital forms often get overlooked, but are a common source of frustration. Add proper tags, label form fields, and set a logical reading order. Once your templates are structured correctly, every new document follows suit.

Make Accessibility a Shared Effort

It’s not a job for one department. Developers, designers, content creators, and leadership all play a part. Build accessibility checks into your regular workflows and let people know how to report issues.

Collaborate With Your Vendors

Include accessibility expectations in contracts and RFPs. Ask for VPATs or accessibility documentation before new tools go live.

Keep Learning and Documenting

Train your team, stay informed about new regulations, and track your progress. A simple paper trail of audits, fixes, and training sessions shows commitment that goes beyond compliance.

When accessibility becomes part of your process—not a last-minute fix—it strengthens everything: your brand, your usability, and your connection with every user.

The End of Uncertainty—and the Start of Accountability

H.R. 3417 isn’t just another bill. It’s a signal that the era of uncertainty is ending. It tells organizations, large and small, that accessibility isn’t a nice-to-have—it’s a right.

Whether it passes this year or the next, the direction is clear. Start building accessibility into your workflow now, not later.

At 216digital, we see this as a turning point—one that rewards teams who act early and design with everyone in mind. If you’re ready to take the next step, consider scheduling an ADA briefing with our team. These sessions help organizations identify accessibility gaps, plan remediation, and prepare for compliance with confidence.

The web was built for all of us. This bill helps make sure it finally works that way.
Greg McNeil

October 10, 2025

Legal Compliance

Accessibility, accessibility laws, H.R. 3417, state accessibility laws, Web Accessibility, Website Accessibility
Can Google and AI Really Find Your Content?
When you hit “publish,” you picture your post showing up where it should—front and center on Google, or clearly summarized by an AI assistant. But here’s the catch: search engines and AI tools can’t understand what you don’t clearly show them.

Accessible content plays a much bigger role in that than most people realize. The same structure that helps a screen reader follow your page also helps algorithms interpret it correctly. Accessibility and discoverability are really two sides of the same coin—both depend on clarity.

But how exactly does accessibility connect to visibility—and why does it matter for both people and technology?

Accessibility, SEO, and AI: A Shared Language

Accessibility and visibility have always shared the same foundation: clarity. And now, that connection is stronger than ever.

Search engines and AI models like Google’s Gemini, ChatGPT, and Claude rely on structured, machine-readable data to interpret and represent your content. They don’t see pages the way humans do—they read the code underneath. Every accessible feature you include becomes a signal that helps them understand and surface your work correctly.

How Accessibility Practices Strengthen Visibility

Alt text, structured headings, transcripts, and accessible PDFs aren’t just ethical—they’re strategic. Each one sends clear indicators to both search engines and large language models (LLMs):
- Alt text clarifies image content.
- Headings establish hierarchy and keyword context.
- Transcripts add searchable text for videos or podcasts.
- Accessible PDFs transform otherwise invisible documents into readable, indexable content.
A recent Semrush study found that sites with higher accessibility scores consistently outperform competitors in organic traffic, keyword rankings, and authority. It’s no coincidence. Accessibility helps both humans and algorithms find, understand, and trust your content.

When your pages are built with clarity—logical structure, proper markup, and meaningful descriptions—search bots and AI tools can crawl, index, and summarize your work with greater accuracy. That’s the foundation of discoverability in today’s web.

And as search itself evolves, that foundation is becoming even more important.

Dynamics of Modern Search: Accessibility in the Age of AI Overviews

Search is no longer just about blue links and keyword matches. With Google’s AI Overviews and multimodal experiences, results now blend text, visuals, and summaries that answer questions before users even click.

In this new landscape, accessible content keeps your work visible and correctly represented. The same structural cues that support assistive technology—headings, alt text, transcripts, and semantic HTML—also help AI systems parse meaning and determine relevance.

A Closer Look at What Modern Search Values

Even as AI changes the way we search, Google’s message to creators stays consistent: clarity, structure, and usefulness always come first.
- Create unique, helpful content for people first. Quality and clarity come before keywords.
- Provide a good page experience. Fast load times, readable layouts, and intuitive navigation still matter.
- Ensure your content is accessible to crawlers. Avoid blocking bots, broken links, or inaccessible markup.
- Use structured data responsibly. Make sure what users see aligns with what’s coded behind the scenes.
- Support multimodal search. Pair meaningful text with relevant visuals, videos, and transcripts.
In short, the same elements that make your website inclusive also make it understandable to machines. Accessibility gives your content context, precision, and resilience in a constantly changing search environment—ensuring it’s not just found, but found correctly.

So, how can you put these principles into practice and build accessibility into your daily workflow?

Practical Habits That Drive Accessibility—and Discovery

Accessibility and visibility meet in the details. Every choice you make—how you organize headings, describe visuals, or structure content—helps both humans and algorithms understand what you’ve built. These small, consistent habits make your content easier to use, easier to find, and easier for AI systems to summarize accurately.

Structured Headings: The SEO and AI Shortcut to Accessible Content

Headings do more than label sections—they define your content’s hierarchy. For readers, they make scanning and navigation simple. For search engines and AI, they reveal how ideas relate and which ones matter most.

To use headings effectively:
- Use one <h1> for your page title.
- Follow with nested <h2>, <h3>, and so on in logical order.
- Avoid skipping levels or using headings purely for styling.
This hierarchy matters. Screen readers rely on it to help users navigate, and algorithms depend on it to interpret structure. When headings are clear and consistent, everyone—people, crawlers, and AI systems—can follow your logic from top to bottom.

Alt Text: Giving Images a Voice

Images tell part of your story, but machines can’t see them without your help. Alt text gives visuals meaning and purpose.

For people using screen readers, alt text describes what’s on the page. For AI and search engines, it provides metadata that connects visuals with your topic and keywords.

When writing alt text:
- Focus on the image’s intent, not just its appearance.
- Keep it concise and specific—around 125 characters works well.
- Skip “image of” or “photo of”; assistive tools already convey that context.
Strong alt text makes your images accessible, searchable, and easier for AI systems to interpret accurately—an essential ingredient of accessible content.

Transcripts and Captions: Turning Sound into Searchable Context

Audio and video bring stories to life—but unless they’re transcribed or captioned, much of their value remains invisible to search engines and AI tools.

Transcripts and captions convert spoken words into readable, searchable text. That means users who are Deaf or hard of hearing can follow along, while algorithms gain structured language to index and summarize.

Best practices include:
- Providing full transcripts for podcasts, webinars, and interviews.
- Adding accurate captions to videos instead of relying on auto-generated ones.
- Including speaker names or brief context when needed for clarity.
Captions also increase engagement—many people watch videos muted, especially on mobile. Transcripts give your content a second life, helping AI represent it more accurately in search summaries.

Clean HTML: The Foundation of Accessible Content

Behind every web page is code—and its quality determines how easily both humans and systems can make sense of it. Semantic HTML means using the right element for the right job:
- <button> for actions
- <a> for links
- <nav> for navigation
- <section> or <article> for grouped content
A logical structure creates predictability for users navigating with keyboards or assistive tech. It also gives AI and search engines a clear map of what’s interactive, what’s content, and what’s context.

Clean markup isn’t just good development—it’s what keeps your content readable, indexable, and adaptable as search technology evolves. Of course, creating accessible content is only half the work. The real proof comes when you test how it performs for actual users.

How to Check Your Site for Accessibility

Even a well-structured site deserves a reality check. After you’ve refined your headings, tightened your HTML, and written meaningful alt text, it’s worth asking—does it all work the way you expect? In other words, does the experience result in accessible content in practice, not just in theory?

Accessibility isn’t something you set and forget. It’s a process of validation, one that ensures your effort translates into real usability for real people. Testing is where structure meets experience—and where your site proves that clarity isn’t just technical, but tangible.

Ways to Evaluate Your Site’s Accessibility in Practice

The best way to understand accessibility is to experience it from different perspectives.
- Run automated scans with tools like WAVE, or Lighthouse to flag quick fixes such as missing alt text, skipped headings, or low contrast.
- Listen to your pages through screen readers like NVDA, JAWS, or VoiceOver to understand how content flows for non-visual users.
- Navigate by keyboard only, confirming that menus, buttons, and links behave predictably.
- Watch your videos and audio with captions on—do they read naturally, or feel disjointed?
- Review your PDFs and downloads to ensure they’re tagged, readable, and properly ordered.
- Seek real feedback from people with disabilities. No automated tool can replace human experience.
The goal isn’t perfection—it’s awareness. Each check brings you closer to a site that performs gracefully for everyone, including the algorithms interpreting it behind the scenes.

From Clarity to Discovery: The Role of Accessibility in AI Search

So, can Google and AI really find your content?
Only if you make it findable.

Accessibility bridges human understanding and machine interpretation. When your content is clear, structured, and built for everyone, it becomes truly discoverable—by people, by search engines, and by the next generation of AI.

If you’re ready to take the next step toward lasting visibility and compliance, consider scheduling an ADA briefing with 216digital. Our accessibility team helps organizations evaluate, plan, and remediate their websites to meet ADA and WCAG standards—strengthening both compliance and visibility through a more inclusive digital experience.
Greg McNeil

October 9, 2025

The Benefits of Web Accessibility

Accessibility, Benefits of Web Accessibility, Content Writing, Digital Marketing, Marketing, videos and audio content, Website Accessibility
What Is Visually Hidden Content—and Why Use It?
Every interface makes choices about what to show and what to leave unseen. Most of the time, that’s about layout or aesthetics—but it’s also about communication.

For users who rely on assistive technologies, much of that communication happens through structure, labels, and semantic relationships. When visual clarity comes at the cost of semantic clarity, accessibility starts to break down. A clean UI is great, but clarity for assistive technologies is non-negotiable. When we drop visible text in favor of icons or compact layouts, we still owe users the same meaning.

A practical answer is visually hidden content. It’s a technique for keeping information available to assistive tech—screen readers, braille displays, voice navigation—while keeping it out of visual view. Done well, it bridges the gap between a clean interface and a complete experience.

You’ve seen it everywhere:
- A magnifying glass icon that announces “Search.”
- A “Read more” link that includes the article title.
- A skip navigation link that quietly appears when tabbed into.
Each example keeps the design clean while preserving meaning for users who don’t navigate visually. It’s not a trick—it’s thoughtful design expressed through code.

When Hiding Breaks Accessibility

It’s tempting to reach for display: none or visibility: hidden. Both make an element disappear—but they also remove it from the accessibility tree. To a screen reader, that content no longer exists.

The same problem appears in older workarounds—moving elements off-screen with huge negative positioning or marking the wrong element with aria-hidden="true". They achieve visual cleanliness but erase meaning for assistive tools.

If the accessibility tree is a map of what users can explore, those declarations tear off a corner of it. The HTML remains, but users can’t reach it.

When something needs to be read, referenced, or focused, it must stay in the tree. The goal isn’t to hide it from everyone—it’s to make it visually invisible while still programmatically present.

A Modern, Reliable Pattern for Visually Hidden Content

Most modern teams rely on a single, standardized utility for this purpose. It’s simple, maintainable, and works across browsers and devices:
```
.visually-hidden {
  border: 0;
  clip-path: inset(50%);
  height: 1px;
  margin: 0;
  overflow: hidden;
  position: absolute;
  white-space: nowrap;
  width: 1px;
}
```
Each property plays a specific role:
- clip-path: inset(50%) hides the visible area.
- position: absolute removes it from the layout but not the accessibility tree.
- height and width shrink it to an imperceptible size.
- overflow: hidden ensures no text leaks visually.
- white-space: nowrap prevents wrapping or accidental exposure.
This approach replaced older hacks like clip: rect() or sending text off-screen with left: -9999px;. Those caused issues for magnifiers and high-zoom environments. The clip-path pattern is clean, modern, and predictable.

Use it with intention. Adding visually hidden content everywhere can overwhelm screen reader users. The best implementations give context—not clutter.

Making Focusable Elements Work for Everyone

Skip links, “Back to top” anchors, and similar utilities need to stay hidden until they’re actually used. If you apply .visually-hidden directly, keyboard users can focus the link but won’t see it—an invisible focus trap.

The solution is a focusable variant:
```
.visually-hidden-focusable:not(:focus):not(:active) {
  border: 0;
  clip-path: inset(50%);
  height: 1px;
  margin: 0;
  overflow: hidden;
  position: absolute;
  white-space: nowrap;
  width: 1px;
}
```
This keeps the element hidden until it receives focus. Once active, it becomes visible—making skip links discoverable without cluttering the design.

A few practical habits:
- Always provide a visible focus outline and clear contrast.
- Keep the revealed link’s position consistent (usually top-left).
- Use short, direct text—users should immediately understand its purpose.
This small adjustment is what makes keyboard navigation intuitive, discoverable, and consistent across accessible websites.

Visually Hidden or ARIA? Understanding the Difference

Developers sometimes treat these tools as interchangeable. They’re not; they work at different layers.

Use visually hidden content when you need real, localizable text in the DOM—context for links, helper hints, or dynamic status messages that assistive technologies should read naturally.

Use ARIA when you’re labeling or describing elements that are already visible:
- aria-label adds a brief text label.
- aria-labelledby points to a visible label.
- aria-describedby links to explanatory text or error messages.
- Live regions (role="status") announce dynamic changes.
Often, the best solution combines both. A decorative SVG can be marked aria-hidden="true", while a hidden text label provides a proper name. A form field can have a visible label and connect to hidden guidance via aria-describedby.

Knowing when to use which—sometimes both—is what turns compliance into genuine usability.

Writing Hidden Text That Adds Value

Hidden text should earn its place. It’s part of the user experience and deserves the same editorial care as visible copy.

A few best practices:
- Add what’s missing visually—don’t repeat what’s obvious.
- Keep it short and natural; users will hear it read aloud.
- Avoid filler or redundancy—screen readers already announce role and state.
- Localize it so it fits each supported language context.
When written thoughtfully, visually hidden content enhances understanding without adding noise. The best examples are invisible to some, indispensable to others.

Testing What You Can’t See

Accessibility isn’t a box to tick—it’s a conversation between your design and your users. Testing is where that conversation becomes real.

Here’s how to validate your implementation:
- Keyboard: Tab through the page. Ensure focus moves logically and stays visible.
- Screen readers: Use NVDA, VoiceOver, or JAWS to confirm that hidden text reads in context.
- Accessibility tree: Check DevTools to make sure hidden content remains part of the structure.
- Zoom and magnification: Scale up to 200% and confirm no visual artifacts appear.
Automation can’t tell you whether your content makes sense—but a quick, human pass will.

From Utility to System

Once you’ve validated your approach, make it part of your toolkit.
- Include .visually-hidden and .visually-hidden-focusable in your design system.
- Document their purpose, examples, and edge cases.
- Encourage teammates to review hidden content with the same care as visible UI text.
Frameworks like Tailwind’s sr-only class use this exact foundation. Aligning with established patterns makes your code predictable and your accessibility practices easier to scale.

This is how visually hidden content becomes part of your craft—not just a snippet you copy-paste.

The Invisible Work That Shapes Experience

A few quiet lines of CSS can completely change how people experience your site. Visually hidden content doesn’t alter what most users see, but it transforms what others can access, understand, and trust.

That’s what accessibility is really about—creating clarity that transcends sight. And that’s what good front-end work does at its best: it makes meaning visible, even when the code itself is unseen.

If you’re working through accessibility fixes or want a second set of eyes on remediation, consider scheduling an ADA briefing with 216digital. It’s a focused, collaborative session designed to help you identify barriers, prioritize what matters most, and move confidently toward compliance.
Greg McNeil

October 8, 2025

How-to Guides

Accessibility, How-to, visually hidden content, WCAG, Web Accessibility, web developers, web development
ADA Title II Conformance Mistakes to Avoid

Let’s start with a familiar scene.

A resident with low vision tries to pay a utility bill online. The button text fades into the background. They zoom in, squint, and finally give up. Across town, a veteran downloads a benefits form—but the PDF won’t open in their screen reader. They call, wait on hold, and eventually hear the same line everyone dreads: “Try again later.”

These moments rarely make headlines, but they happen every day. And they’re exactly what ADA Title II conformance is designed to prevent.

With new deadlines approaching, the clock is officially ticking. The Department of Justice has set clear expectations: every website, mobile app, and digital document must meet WCAG 2.1 Level AA standards to be considered accessible.

Still, even with those expectations in place, many agencies stumble—not from neglect, but from complexity. Outdated systems, legacy PDFs, limited budgets, and competing priorities all pull in different directions.

This guide outlines ten of the most common pitfalls local governments encounter—and how your team can avoid them before small issues grow into time-consuming, costly problems.

1 | Waiting Too Long to Begin ADA Title II Conformance

One of the most common mistakes is simply waiting. Waiting for next year’s budget, a redesign, or until “things calm down.” But accessibility work takes time—often months, sometimes years—especially when legacy systems or vendor-managed platforms are involved. Every delay widens the gap and makes remediation more expensive.

Start Small, but Start Now

Begin with a WCAG 2.1 AA audit that targets your highest-traffic, highest-risk pages—payment portals, permit applications, emergency alerts. Use the findings to build a phased plan: tackle quick fixes first, then move into deeper remediation like PDFs or interactive content.

Momentum matters more than perfection. Each resolved issue moves you closer to meaningful accessibility—and lasting ADA Title II conformance. But while hesitation can stall progress, so can taking the wrong kind of shortcut.

2 | Relying on Widgets or “Quick Fixes”

When deadlines loom, shortcuts start to look tempting. Accessibility widgets and overlays promise instant compliance, but the data tells a different story. Over 20% of ADA web lawsuits in 2024 involved sites using overlays, and many of those tools introduced new barriers for assistive technology users.

Treat Them as Temporary Support at Best

Widgets don’t repair flawed code—they mask it. Pair automated scans with manual testing to catch what machines miss. True accessibility isn’t something you install; it’s something you build, maintain, and test continuously. Even agencies that avoid quick fixes can still lose momentum when they misunderstand what an audit actually means.

3 | Treating the Audit as the Finish Line

An accessibility audit is a starting point, not a success story. It reveals what’s broken but doesn’t fix it. Too often, agencies check the box once the report arrives, assuming the work is done. Six months later, those same issues remain—and the deadline looms closer.

Turn the Audit Into a Roadmap

Assign clear ownership, set realistic timelines, and track each fix to completion. The goal isn’t to admire the findings; it’s to act on them. An audit shines the light, but ADA Title II conformance only comes from follow-through. Once remediation begins, it’s also essential to remember that accessibility extends beyond the desktop experience.

4 | Overlooking Mobile Accessibility

For many residents, your mobile site or app is their primary touchpoint with local government. If that experience isn’t accessible, your services aren’t either. Yet mobile testing often gets pushed aside until the very end—when changes are most expensive to make.

Test Early and Test on Real Devices

WCAG 2.1 includes mobile-specific guidance on touch targets, gestures, and orientation. Make sure forms resize correctly and navigation works without a mouse. Accessibility should follow the user, not the screen size. And while mobile access is crucial, so are the documents that so many residents rely on for daily interactions.

5 | Ignoring Accessibility in Digital Documents

Even when web pages pass compliance checks, PDFs and other downloadable materials often don’t. Forms, meeting agendas, and reports are some of the most common—and most problematic—files on public sites. The DOJ is clear: if a document provides public information or access to a service, it must be accessible.

Audit Your Digital Library

Start with frequently downloaded or required documents. Train staff to tag PDFs correctly or, when possible, convert them to HTML pages. Each accessible file removes another barrier and brings your agency closer to full ADA Title II conformance. Of course, even well-prepared teams can find their progress derailed by one common factor: vendors who don’t share the same standards.

6 | Not Holding Vendors Accountable

Even when third-party vendors manage your website, accessibility responsibility remains yours. Public agencies can’t outsource compliance. That’s why contracts matter as much as code.

Bake Accessibility Into Every Partnership

Specify WCAG 2.1 AA requirements, mandate assistive-technology testing, and require documentation at handoff. Accessibility clauses shouldn’t live in the fine print—they should be measurable deliverables written into the contract. Without vendor accountability, accessibility can erode quietly with each update. And even with vendor alignment, one final validation step ensures your work actually functions as intended.

7 | Skipping Manual and Assistive-Technology Testing

Automated tools are valuable, but they can’t replicate human experience. Navigation traps, mislabeled buttons, and confusing reading order often pass automated checks unnoticed.

Manual Testing Closes That Gap

Use screen readers, voice navigation, magnifiers, and keyboard-only controls to simulate how real people interact with your site. Better yet, invite users with disabilities to test and provide feedback. Their insights catch what automation never will—and validate genuine ADA Title II conformance. Still, even the most accessible site today can fall out of compliance tomorrow without ongoing monitoring.

8 | Neglecting Ongoing Monitoring

Accessibility isn’t a one-time project; it’s ongoing maintenance. A single CMS update or design tweak can reintroduce barriers.

Make Monitoring Routine

Schedule quarterly manual reviews and monthly automated scans. Keep a visible feedback form on your website so residents can report issues directly. Treat accessibility like preventative care: small, consistent checks that protect long-term health. But even with regular testing, the strongest defense is an informed team that knows how to prevent barriers before they happen.

9 | Underestimating Accessibility Training

Technology identifies issues, but people prevent them. Without training, the same mistakes—missing alt text, unlabeled forms, inaccessible PDFs—keep returning.

Invest in Continuous Education

Provide annual, role-specific training for content authors, developers, and procurement staff. Keep it practical: short sessions, clear checklists, and ongoing refreshers. When accessibility knowledge becomes second nature, compliance becomes culture. And when that culture takes root, it’s worth sharing it publicly.

10 | Failing to Publish a Public Accessibility Statement

A public accessibility statement isn’t a formality—it’s a promise. It tells residents, We’re committed, we’re listening, and we want your feedback.

Publish a Concise Statement

Reference your WCAG standard, list contact information for support, and update it at least once a year. This simple gesture builds transparency and trust—cornerstones of inclusive digital governance.

ADA Title II Conformance Is About People, Not Just Policy

Reaching ADA Title II conformance isn’t just about compliance—it’s about people. It’s about ensuring that every resident can access essential public services with independence and dignity.

When your platforms are accessible, seniors can pay their bills without help. Parents can find school updates easily. Veterans can apply for benefits confidently.

That’s not a technical milestone—it’s a civic one.

Start early. Build steadily. Keep accessibility alive through training, monitoring, and accountability. Compliance may be the mandate, but inclusion is the mission.

If your agency is ready to turn goals into measurable progress, schedule an ADA briefing with 216digital. We’ll help you navigate these ten pitfalls and build a roadmap for sustainable, equitable access for every resident you serve.

Greg McNeil

September 30, 2025

Legal Compliance

Accessibility, ADA Compliance, ADA Title II, ADA Website Compliance, Web Accessibility, Website Accessibility

aria‑selected: Practical Guide for Interactive UI

Modern web applications thrive on interactivity. Tabs, listboxes, and data grids make complex tasks easier for sighted users—but without proper semantics, those same widgets can shut people out.

For example, a set of tabs may look visually distinct, but unless screen readers know which tab is currently selected, the component is unusable for blind users. Similarly, keyboard-only users can be stranded if selection isn’t tied to focus and navigation logic.

That’s where aria-selected comes in. This attribute bridges the gap between visual presentation and assistive technology, ensuring state changes are clearly communicated. In this guide, we’ll cover what aria-selected means, when to use it, real-world code examples, and best practices for building accessible interactions.

Decoding aria-selected

According to the WAI-ARIA specification, aria-selected communicates the selection state of an element in a widget. It doesn’t change visuals—it adds semantic meaning to the accessibility tree so assistive tech can interpret the UI correctly.

Values Explained

true → This item is selected.
false → This item is selectable but not selected.
(Absence) → This item isn’t selectable at all.

Tip: Roles that support aria-selected include: tab, option, row, gridcell, and treeitem. Use it only where a “selected” state makes sense.

aria-selected vs. Other Attributes

It’s easy to confuse aria-selected with other ARIA attributes. Here’s how to know when you’re using the right one:

Attribute	Primary Purpose	Typical Components
aria-selected	Indicates which item is currently chosen	Tabs, listboxes, grids, tables
aria-checked	Binary on/off state	Checkboxes, radios
aria-pressed	Toggle button active state	Toolbar buttons
aria-current	Denotes user’s current location	Nav links, breadcrumbs

Practical Use Cases & Code

Tabs

Tabs are a classic single-select widget. Only one tab can be selected at a time.

<div role="tablist" aria-label="Profile sections">
  <button id="tab-overview" role="tab" aria-selected="true"
          aria-controls="panel-overview">Overview</button>
  <button id="tab-settings" role="tab" aria-selected="false"
          aria-controls="panel-settings">Settings</button>
</div>

<div id="panel-overview" role="tabpanel" aria-labelledby="tab-overview">
  <!-- Overview content -->
</div>
<div id="panel-settings" role="tabpanel" aria-labelledby="tab-settings" hidden>
  <!-- Settings content -->
</div>

Implementation Notes

On click, Enter, or Space: update aria-selected, swap focus, and show the panel.
Keyboard navigation: Left/Right (or Up/Down for vertical), Home/End for quick jumps.

Listbox (Multi-Select)

Listboxes can be single- or multi-select. Here’s a multi-select version:

<ul role="listbox" aria-label="Choose toppings"
    aria-multiselectable="true" tabindex="0"
    aria-activedescendant="opt-pepperoni">
  <li id="opt-pepperoni" role="option" aria-selected="true">Pepperoni</li>
  <li id="opt-mushroom"  role="option" aria-selected="false">Mushrooms</li>
  <li id="opt-olive"     role="option" aria-selected="false">Olives</li>
</ul>

Interaction Details

Arrow keys move focus; aria-activedescendant updates to track the active item.
Space toggles selection state.
Ctrl/Shift + Arrow supports range selection like desktop apps.

Grids / Spreadsheets

Grids allow row and cell-level navigation. They’re common in dashboards and spreadsheets.

<div role="grid" aria-label="Sales records" aria-activedescendant="cell-1-2">
  <div role="row">
    <div role="columnheader" aria-colindex="1">Date</div>
    <div role="columnheader" aria-colindex="2">Sales</div>
  </div>

  <div role="row" aria-rowindex="1">
    <div id="cell-1-1" role="gridcell" aria-colindex="1" aria-selected="false">Jan</div>
    <div id="cell-1-2" role="gridcell" aria-colindex="2" aria-selected="true">5 000</div>
  </div>
  <div role="row" aria-rowindex="2">
    <div id="cell-2-1" role="gridcell" aria-colindex="1" aria-selected="false">Feb</div>
    <div id="cell-2-2" role="gridcell" aria-colindex="2" aria-selected="false">4 200</div>
  </div>
</div>

JavaScript Must Handle

Arrow keys move focus across cells and sync aria-activedescendant.
Space/Enter toggles aria-selected.
Optional: persist state (e.g., in localStorage) to remember selections.

Best Practices for aria-selected

Focus Management

In single-select widgets: focus stays inside, arrow keys update selection.
In multi-select widgets: focus moves independently, Space/Enter toggles states.
Always update aria-activedescendant dynamically.

Visual Feedback Beyond Color

Don’t rely on color alone. Use icons, bold text, or borders.
WCAG 2.2 requires at least 3:1 contrast for selected/focus states.

Keyboard Navigation

Tabs: Arrow keys, Home/End, Enter/Space to activate.
Listbox/Grid: Arrow keys plus Space/Enter (and Ctrl/Shift combos for multi-select).
Optional: Escape to clear selection or exit.

Testing Your Implementation

Accessibility doesn’t stop at code—it must be validated.

Screen reader testing: NVDA, JAWS, and VoiceOver should announce selection changes correctly.
Keyboard walkthroughs: Confirm focus order and selection behavior.
Automated checks: Useful for catching missing attributes, but always supplement with manual testing.

Bonus Patterns

Once you’re comfortable with the basics, aria-selected can also power:

ARIA Trees: File explorer-like navigation.
Carousels: Tabs-like controls for slide navigation.
Email-style panels: Combining aria-selected with aria-multiselectable for Gmail-style selection logic.

Build with Inclusion from the Start

The aria-selected attribute may seem small, but it represents a bigger principle: creating interfaces where everyone can interact equally.

Accessibility is about thoughtful interaction design, not just compliance checklists. By implementing aria-selected correctly, you close the gap between a slick UI and one that’s truly inclusive.

Don’t wait until launch—or worse, until a lawsuit—to think about accessibility. Build it in from the beginning, and both your users and your future self will thank you.

Want clarity on how your site measures up or how to improve implementation? Schedule a private ADA briefing with 216digital and get expert insight on real-world accessibility practices.

Greg McNeil

September 29, 2025

How-to Guides, Uncategorized

Accessibility, ARIA, aria-selected, web developers, web development, Website Accessibility

Deck the Sales with Accessible Holiday Marketing
Every holiday season, online retailers face the same challenge: how to keep up with surging traffic without losing customers to friction. Between November and December, nearly one-fifth of all retail sales happen online—meaning even the smallest accessibility barriers—an unreadable button, a missing label, a poorly designed modal—can quietly chip away at revenue.

But there’s more at stake than missed sales. Accessibility now sits at the intersection of ethics, law, and business strategy. Making your digital experiences usable for everyone isn’t just compliance—it’s a mark of respect for your customers and a driver of measurable growth.

Accessible holiday marketing is how smart teams turn inclusion into performance. It creates digital spaces that welcome all shoppers, reduce drop-offs, and reinforce brand trust at the busiest—and most competitive—time of year. Think of it as rolling out a digital welcome mat, trimmed in garland, for every customer who stops by your virtual store.

Accessibility: An Ethical Imperative and a Business Advantage

Accessibility began as an ethical conversation about fairness and inclusion. Today, it’s also a legal and financial necessity.

Under the Americans with Disabilities Act (ADA) and related global laws, websites are expected to provide equal access to all users. The Department of Justice has affirmed that digital properties—especially those tied to commerce—fall under these requirements. Noncompliance can lead to lawsuits, settlements, and, more importantly, reputational damage that no brand wants under its tree.

Yet beyond risk, the business upside is clear. One in four U.S. adults reports living with a disability, representing a purchasing power that exceeds $1 trillion globally. Accessibility doesn’t shrink your audience—it expands it.

And 80% of consumers say a company’s experience matters as much as its products. In that sense, accessibility isn’t just the right thing to do—it’s the smarter way to compete. During the holidays, it’s also the easiest way to make sure no shopper gets left out in the cold.

Where to Start: Building an Accessible Holiday Marketing Framework

Accessibility shouldn’t be treated as an afterthought in the rush to wrap up year-end campaigns. Instead, build it into your existing production cycle. Here’s how to start unwrapping quick wins.

Step 1: Define What Success Looks Like

Don’t bolt accessibility on at the end. Bake accessible holiday marketing into the same workflow you use for performance and SEO.
- Checkout completion rates: If shoppers abandon forms mid-purchase, that’s a red flag. Accessibility gaps here are like dropping presents halfway up the chimney.
- Cart error rates: – Test both keyboard and screen reader sessions. If errors spike, navigation might need a tune-up.
- Promo email click-throughs: Compare results with images off. If engagement plummets, you’re leaning too heavily on visuals.
- Video completion rates: Captioned videos often earn longer watch times, proof that accessibility can shine brighter than any seasonal campaign light.
Assign an owner for each KPI and add an accessibility review before code freeze—because nothing ruins the holiday rush like last-minute fixes.

Step 2: Reduce Friction in the Core Shopping Flows

The most impactful changes often live in the most familiar places: product discovery, product pages, and checkout.

Product Discovery
- Keyboard navigation: Every filter, dropdown, and toggle should be usable without a mouse. No one wants to wrestle with a website like tangled lights.
- Visible focus states: Highlight where users are on the page with clear outlines—think of it as a guiding star through your interface.
- Logical tab order: Keep navigation smooth and intuitive; users shouldn’t feel like they’re lost in the wrapping paper.
- Clear labeling: Add ARIA labels and visible names to controls so everyone knows what each button does.
Good navigation is like a perfectly organized gift list—clear, predictable, and satisfying to check off.

Product Pages
- Descriptive alt text: Replace “red shirt” with “close-up of red cotton t-shirt with crew neckline.” Paint a picture worth a thousand words—and conversions.
- Text-based selectors: Pair swatches with visible text for color and size. Don’t make users guess whether “cranberry” means red or pink.
- Live region announcements: Notify assistive technologies when stock, price, or promotions change. No one likes a surprise sellout mid-cart.
Clarity here means fewer returns—and happier unboxings.

Checkout

Checkout is where good design proves its worth.
- Label everything clearly: Every field should say exactly what it wants — “Email address,” “Zip code,” not “Field 1.” When users can fill out a form without guessing, they finish faster.
- Put errors where they happen: If someone types their card number wrong, the message should appear right there, not two scrolls away. Nobody wants to play “Where’s Waldo?” in the middle of a purchase.
- Skip the impossible CAPTCHA: If you must verify humans, use a simple checkbox or a one-line logic question.
- Keep focus steady: When a payment pop-up opens, the cursor shouldn’t vanish. Trap focus inside the modal and return users to the right spot when it closes.
- Do a keyboard-only run-through: It takes five minutes. If you can buy something with just the Tab key, you’re in good shape.
It’s not glamorous work, but it’s what turns a holiday shopper into a paying customer.

Step 3: Design an Accessible Holiday Marketing Campaign

Color, Contrast, and Motion
- Contrast ratios: Keep text clear—even against festive reds, greens, or snowy whites. 4.5:1 is the magic number.
- Motion reduction: Add a “pause animation” option for sparkling banners or falling snow. Not everyone enjoys a blizzard of motion.
- Test on multiple screens: Preview your site in bright daylight or cozy lamplight—holiday shoppers browse everywhere.
Accessibility ensures your creativity glows without overwhelming.

Email Accessibility Best Practices

Holiday emails do a lot of heavy lifting, so make them easy to read even when half the inbox blocks your images.
- Use real text for the important stuff. If your subject line says “50% Off,” that shouldn’t vanish the moment images are turned off.
- Write links that make sense out of context. “Unwrap Today’s Deals” works better than “Click here” — and it keeps your brand voice intact.
- Keep the structure simple. Short paragraphs, real headings, and logical flow help screen readers — and people reading on their phones at the kitchen table.
- Underline your links. It’s not old-fashioned; it’s functional. Some users can’t rely on color alone to spot a link.
Think of your holiday campaign like a greeting card — clean, clear, and worth opening.

Video and Social Content
- Closed captions: Accurate, human-checked captions help everyone follow along, from office multitaskers to late-night shoppers.
- Transcripts: Perfect for anyone scrolling during family movie night with the volume low.
- Hashtags and emojis: Use camel case (#MerryAndBright) and keep emojis at the end of posts.
- Alt text: Describe visuals on social posts so every viewer can feel part of the moment.
Small accessibility touches here make your brand feel thoughtful—like that handwritten tag on a gift.

Step 4: Test Early and Often

Automated Checks
- Integrate tools: Add accessibility scans to your CI/CD pipeline so errors get fixed faster than you can say “ugly sweater.”
- Catch recurring issues: Run tests regularly to stop regressions before launch.
- Treat failures seriously: Missing alt text should be a showstopper, not a “we’ll fix it next year.”
Manual Spot Checks
- Keyboard audits: Tab through product → cart → checkout. If you can’t complete it, neither can Santa’s helpers.
- Screen reader reviews: Listen to how your site reads aloud—clarity here is worth its weight in gold tinsel.
- Record findings: Short video clips make debugging faster than long lists of notes.
Pre-Launch Governance
- Accessibility sign-off: Make it part of your “naughty or nice” launch checklist.
- Track waivers: If something’s postponed, record a fix date to stay accountable.
- Align with performance metrics: Accessibility deserves a seat at the same table as SEO and load time.
Step 5: Expand Accessibility Across the Journey

Accessibility shouldn’t stop at checkout—it should carry through every touchpoint.

Landing Pages and Paid Ads
- Avoid autoplay: Let users control media playback; not everyone wants surprise carols.
- Write clear CTAs: Use straightforward text like “Explore Holiday Offers” instead of “Learn More.”
- Add multiple cues: Combine color, text, and icons so everyone can understand your visuals.
- Keep it fast: Optimize load times. Accessibility and speed go hand in hand.
Retention and Loyalty
- Organize gift guides: Use clear headings and a logical structure for quick navigation.
- Make wishlists keyboard-friendly: Ensure “Add to Wishlist” works with both mouse and keyboard.
- Announce updates: When something’s back in stock, let assistive tech announce it too.
Accessible holiday marketing builds trust—and trust keeps customers coming back long after the decorations come down.

Step 6: Equip Customer Support to Handle Accessibility
- Multiple contact options: Offer phone, chat, and email—because not everyone writes letters to the North Pole.
- Accessible chat tools: Check focus order and make sure screen readers can announce new messages.
- Transparent status: Display service hours and response times to prevent frustration.
- Proactive communication: Post banners if known issues exist, and provide alternative paths to complete purchases.
- Train support teams: Teach staff how to gather details about accessibility problems. The more context they collect, the faster fixes arrive.
Support should feel like a helping hand, not a closed door.

Step 7: Measure, Learn, Improve
- Segment analytics: Compare behavior by input method—keyboard, mouse, or touch—to spot friction points.
- Correlate updates: Link accessibility fixes to conversion data; seeing the lift is like watching sales lights twinkle in real time.
- Weekly check-ins: A 15-minute accessibility stand-up keeps everyone aligned during peak traffic.
- Post-season reflection: Capture what worked and what needs improvement before the next holiday rush.
Accessibility improvement is the one gift that keeps on giving.

Quick-Start Accessible Holiday MarketingChecklist

This Week
- Tab-test PDP → Cart → Checkout to ensure a clear path to purchase.
- Update alt text for the top 100 SKUs with product details and purpose.
- Caption all holiday videos—think of it as wrapping each message neatly.
This Month
- Automate accessibility scans so no error sneaks into the new year.
- Refine email templates with an accessible, mobile-friendly design.
- Test campaigns with images off—your message should still shine.
Before Code Freeze
- Perform a manual screen reader review of top pages.
- Publish an accessibility contact channel so feedback doesn’t get lost in the snow.
From Cart to Claus: Keeping Every Shopper Included

Accessibility has moral weight—it ensures equal participation in the digital marketplace. It has legal weight—it aligns with ADA and WCAG standards. And it has business weight—it strengthens loyalty, protects brand trust, and captures a broader audience.

Accessible holiday marketing ties all three together like a perfectly wrapped gift. It makes the web fairer, the experience smoother, and the business stronger.

For teams wanting to check their list twice, an ADA briefing with 216digital helps identify high-ROI accessibility improvements before peak traffic. Our experts help teams unwrap the quick wins—and keep the momentum into the new year.

After all, inclusion isn’t just a seasonal sentiment—it’s how lasting customer relationships begin.
Greg McNeil

September 26, 2025

Content Marketing, Digital Marketing, How-to Guides

Accessibility, Digital Marketing, How-to, Marketing, Web Accessibility, Website Accessibility

Why Accessibility Belongs in Your Marketing Roadmap

The Business Case for Accessibility

The Risk of Leaving Accessibility Out

Building Accessibility into Your Marketing Workflow

Start Early

Create Together

Test Before Launch

Where Accessibility in Marketing Matters Most

Website

Email and Newsletter

Social Media

Designing for Comfort and Clarity

Testing and Improving Accessibility

Keeping Accessibility in Motion

Measuring What Matters

Accessibility as Ongoing Momentum

Modals vs. Dialogs: Key Differences and Use Cases

What’s the Difference?

When to Use Each

Advantages and Drawbacks

Choosing the Right Type

Building Accessible Dialogs: From Code to Experience

Start with Solid HTML

Label Everything Clearly

Keep Focus on Track

Prevent Background Scrolling

Design for Visual Calm

Best Practices for Accessible Dialogs

1. Keep Users Oriented

2. Offer Multiple Ways Out

3. Use Restraint with Motion

4. Test Like a Real User

5. Respect Timing and Intent

Accessibility Beyond the Dialog

Why Accessibility Still Matters in the Command Line

Where the Command Line Trips Up—and How to Fix It

1. Structure Matters More Than You Think

2. Tables and Long Outputs Need Rethinking

3. Feedback Should Be Informative—Not Decorative

4. Make Error Messages Clear and Human

Practical Guidelines for Designing an Accessible CLI

Start Where Developers Live: The CLI

What Makes a Product Media Accessible

1. Clear and Descriptive Alt Text

When Product Media Need Alt Text (and When They Don’t)

Redundant Product Views

Does Your Image Need Alt Text?

Writing Effective Alt Text

2. Optimizing Product Media Formats for Accessibility

3. Avoiding Text Embedded Within Images

4. Maintaining Visual Clarity and Contrast

5. Labeling Interactive Product Media

Testing Tools and Workflow Integration

Product Media That Speaks to Every Shopper

What the Bill Proposes

Rooted in the POUR Principles

A Step Forward for Digital Inclusion

Why H.R. 3417 Matters

What the Bill Would Do

Who’s Covered

What H.R. 3417 Could Change

What Organizations Can Do Now

Start With What Matters Most

Include Your Documents

Make Accessibility a Shared Effort

Collaborate With Your Vendors

Keep Learning and Documenting

The End of Uncertainty—and the Start of Accountability

Accessibility, SEO, and AI: A Shared Language

How Accessibility Practices Strengthen Visibility

Dynamics of Modern Search: Accessibility in the Age of AI Overviews

A Closer Look at What Modern Search Values

Practical Habits That Drive Accessibility—and Discovery

Structured Headings: The SEO and AI Shortcut to Accessible Content

Alt Text: Giving Images a Voice

Transcripts and Captions: Turning Sound into Searchable Context

Clean HTML: The Foundation of Accessible Content

How to Check Your Site for Accessibility

Ways to Evaluate Your Site’s Accessibility in Practice

From Clarity to Discovery: The Role of Accessibility in AI Search