How-to Guides Archives- Page 2 of 8/Category

What Designers Get Wrong About Accessible Web Design

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

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

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

Relying on Color Alone

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

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

Poor Contrast Between Text and Background

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

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

Hover-Only Interactions

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

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

Hiding or Removing Focus Styles

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

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

Icon-Only Buttons Without Labels

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

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

Vague Link Text

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

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

Layouts That Fall Apart When Text Is Resized

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

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

Skipping Alt Text on Images

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

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

Hard-Coded Font Sizes

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

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

Overly Complex Navigation

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

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

Where Good Design Meets Real-World Impact

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

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

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

Greg McNeil

April 8, 2025

How-to Guides, Web Design & Development

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

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

Why Accessibility Matters in E-Commerce

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

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

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

Making Your Shopping Cart Work for Everyone

Add Clear Labels (Yes, Even for Buttons)

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

Let People Update Cart Items Without Guesswork

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

Show Helpful Feedback When Things Go Wrong

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

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

Use Straightforward, Consistent Labels

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

Make Sure Users Can Tab Through Fields Logically

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

Show Errors Clearly and Offer Suggestions

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

Designing a Payment Flow That’s Smooth and Inclusive

Offer More Than One Way to Pay

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

If You Use CAPTCHAs, Make Them Accessible

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

Choose Accessible Payment Gateways

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

Don’t Let Product Filters Be a Barrier

Make Filters Keyboard-Friendly

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

Let Users Know What Filters Are Applied

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

Stick to Native HTML Controls When Possible

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

Testing and Validating Your Work

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

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

Test Manually with Real Assistive Tech

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

Get Feedback from Real Users

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

Small Fixes, Big Impact

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

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

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

April 4, 2025

How-to Guides

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

Alt Text or Image Description? Why Accessibility Comes First

“Should you optimize for SEO or accessibility?” That’s the wrong question.

Let’s be honest—there’s a lot of confusion floating around online, especially on social media, about the difference between alt text and image descriptions. Some folks say you should cram keywords into alt tags. Others say just describe the image “vaguely” for the algorithm. Neither approach helps real people—and they don’t help your brand either.

This article clears things up. We’ll break down the key differences between alt text and image descriptions, explain how both support accessibility and SEO (yes, both!), and offer practical ways to use them well. The goal? Helping you create content that’s not just searchable, but actually usable—for everyone.

Because putting accessibility first doesn’t mean you have to sacrifice SEO. In fact, it means building digital spaces that work better for all users, including search engines.

What Is Alt Text?

Alt text—short for alternative text—is the text you add in HTML to describe an image. It looks something like this:

<img src="pancakes.jpg" alt="Pancakes" />

This little string of text has a few big jobs:

It shows up if an image doesn’t load.
It tells screen readers what the image is for users who can’t see it.
It can help with SEO if written well—but that’s not its main job.

Alt text is usually short and direct. Think “Chocolate cake on a plate” or “Man typing on laptop.” It’s added when you upload images to your website, blog, or CMS.

But here’s the catch: alt text can be too short. It doesn’t always provide enough detail, especially if you’re trying to convey mood, emotion, or complex ideas.

That’s where image descriptions come in.

What Are Image Descriptions?

An image description is a fuller explanation of what an image shows. It’s like telling a story with words instead of just naming what’s in the picture.

Here’s an example:

Alt Text: “Pancakes”

Image Description: “A tall stack of fluffy pancakes covered in golden syrup, powdered sugar, and slices of fresh strawberries and bananas on a white ceramic plate.”

See the difference?

Image descriptions give blind or visually impaired users a more complete picture of what everyone else sees. They may appear near the image in the caption, in surrounding content, or even inside ARIA labels for complex visuals like graphs or maps.

In short: alt text gives a label. Image descriptions give life.

Alt Tags vs. Image Descriptions: Key Differences

Let’s break this down side by side:

Alt Tags	Image Descriptions
Short, a few words	Full sentences
Placed in code (`alt=""`)	In visible content or metadata
Helps screen readers	Helps screen readers and gives more context
SEO-friendly	SEO-friendly
Often auto-generated	Often auto-generated

Think of alt tags as headlines. Image descriptions? They’re the full story.

How Image Descriptions Support Both Accessibility and SEO

Here’s the good news: you don’t have to choose between helping people and helping search engines. Done right, an image description does both.

Let’s say you’re a restaurant. Here’s an example of an image description could look:

“A stack of pancakes from Alexa’s Pancake House, topped with maple syrup, whipped cream, and sliced strawberries.”

This gives a full visual for screen reader users and includes relevant keywords (like your business name) in a natural way.

No stuffing. No tricks. Just useful, clear, descriptive writing.

Tips

Keep your writing simple and honest.
Use your keyword (like image description) naturally—don’t overdo it.
Don’t sacrifice clarity for search performance. Do both.

SEO Pitfalls That Undermine Accessibility

Now let’s talk about what not to do.

Some people think alt text is a great place to dump keywords. That’s a big accessibility mistake. Imagine using a screen reader and hearing:

“Pizza, best pizza, NYC pizza, cheap pizza, pizza restaurant.”

Helpful? Nope. Just frustrating.

Here’s What to Avoid

Keyword packing in alt attributes.
Using phrases that don’t describe the actual image.
Ignoring image descriptions altogether.

A Better Approach

Use short, honest alt text.
Add rich image descriptions nearby for complex images.
Use filenames, captions, and surrounding text to support SEO goals.

Why Accessibility Must Come First

Yes, SEO matters. But accessibility should always come first.

Why?

Because someone who is blind, low-vision, or has a cognitive disability deserves to understand your content just like everyone else. Accessibility means inclusion. It also means better design for all users—including those with slow connections, temporary impairments, or different learning needs.

And let’s not forget: choosing accessibility shows what your brand stands for.

It’s not just for websites either. Platforms like Instagram, Pinterest, and TikTok are full of visuals. People with disabilities use them every day. They deserve full, rich image descriptions too.

Best Practices for Writing Accessible Image Descriptions

Here’s how to get it right:

Keep It Clear and Concise: Avoid long, rambling sentences. Use plain language.
Be Contextual: What’s the purpose of the image? What matters in this moment?
Use Natural Language: Don’t write like a robot. Imagine you’re explaining the image to a friend who can’t see it.
Use Both When Needed: For things like infographics or charts, use a short alt tag and include a detailed image description nearby.
Test with Screen Readers: Listen to how your image description sounds aloud. Would someone understand it without seeing the image?

The Role of Content Creators, Developers, and Marketers

Creating accessible content is a team effort.

Writers and Content Creators: Should know how to write clear image descriptions that include important context.
Developers and Designers: Need to code alt attributes properly and make sure screen readers work well on their platforms.
Marketers and SEO Pros: Can drive results while still being inclusive. Collaboration with accessibility experts is key.

A Better Internet Starts with Better Habits

Here’s the takeaway: You can do both. But accessibility has to come first.

At 216digital, we believe digital accessibility isn’t optional—it’s part of building a better internet. Every well-written image description, every thoughtfully placed alt tag, every small decision adds up.

Not sure if your site is truly accessible? Wondering what your legal obligations are under the ADA?

We can help. Schedule an ADA Accessibility Briefing with our team. It’s your first step toward a more inclusive, compliant, and trustworthy online presence. Let’s build something better—together.

Greg McNeil

April 3, 2025

How-to Guides

Accessibility, Alt text, image description, SEO, WCAG, Web Accessibility

Accordion Accessibility: Common Issues & Fixes
Organizing content effectively on the web is about more than just layout—it’s about usability and inclusivity. When users are forced to scroll through long pages of uninterrupted text, the experience becomes inefficient and frustrating.

Enter accordion components: interactive UI elements that allow content sections to be expanded or collapsed. When implemented correctly, accordion accessibility streamlines navigation and improves content organization. However, if accessibility is overlooked, these helpful components can quickly become barriers.

This guide explores how to design accessible accordion components that enhance the user experience and meet all users’ needs—regardless of their abilities. We’ll cover best practices for structure, semantics, ARIA attributes, keyboard support, and implementation strategies to help you build inclusive, user-friendly interfaces.

Why Accordion Accessibility Matters

Accordions are essential: they reduce visual clutter and allow users to interact with content on their terms. Whether it’s an FAQ page, a product feature breakdown, or technical documentation, accordions help surface only the content that matters at the moment.

However, it’s crucial to remember that not all users interact with content similarly. Screen reader users, keyboard-only users, and others with varying access needs must be able to operate accordions just as easily as those using a mouse or touchscreen. Accessible design isn’t just a nice-to-have—it’s an essential component of responsible development.

The Building Blocks of an Accordion Accessibility-Friendly Component

1. Structure: Header and Panel

Every accordion should be composed of two core parts:

Header (Trigger)

A clickable element (typically a <button>) that users activate to show or hide content. It usually includes a descriptive label and may feature visual indicators like arrows or plus/minus icons.

Panel (Content)

The content is associated with the header. It should be hidden from view and keyboard focus when collapsed and fully accessible when expanded.

For effective accordion accessibility, each header must be clearly linked to its corresponding panel—visually for sighted users and programmatically for assistive technologies.

2. Keyboard Navigation

One of the most common accessibility pitfalls with accordion components is insufficient keyboard support. If users can’t operate your interface without a mouse, it’s not accessible.

Your accordion must support the following interactions:
- Tab / Shift + Tab: Move between focusable elements, including accordion headers.
- Enter or Space: Expand or collapse the currently focused header.
- Arrow Up / Arrow Down: Navigate between accordion headers.
- Home / End: Jump to the first or last header within the accordion group.
By supporting these interactions, you ensure that keyboard users have the same level of control as mouse users.

3. Use Semantic HTML

Semantic HTML provides the backbone of accessibility. It ensures assistive technologies can understand the structure and function of your content without additional cues.

Best Practices for Accordion Accessibility
- Use heading elements (<h3>, <h4>, etc.) to maintain the document outline.
- Place a <button> inside the heading to toggle visibility.
- Wrap panel content in a <div> that follows its associated button.
Why <button> and not <div> or <a>?

Buttons are keyboard-focusable by default, accessible to screen readers, and support interactions like Enter and Space. Enter and Space. If you rely on <div> or <a> for toggling, you’ll need extra code to achieve the same level of accordion accessibility.

4. Implementing ARIA Attributes

ARIA (Accessible Rich Internet Applications) attributes enhance accessibility when native HTML doesn’t fully express an element’s role or state. In custom accordions, these attributes help communicate dynamic behavior to assistive technologies.

ARIA Attributes for Accordion Accessibility
- aria-expanded: Indicates the panel’s expanded (true) or collapsed (false) state. Applied to the button.
- aria-controls: Points to the id of the panel controlled by the button.
- aria-labelledby: Applied to the panel, this links it back to its header button for context.
- aria-hidden:Use decorative icons or non-informative content to prevent screen readers from announcing them.
These attributes ensure that screen reader users receive clear, relevant information about the accordion’s behavior and structure.

Implementation Examples

Option 1: Native HTML with <details> and <summary>

For a semantic-first approach, HTML offers a native accordion-like behavior:
```
<details>
  <summary>Shipping Information</summary>
  <div>
    <p>We offer free shipping on orders over $50...</p>
  </div>
</details>
```
Pros
- Minimal code
- Built-in keyboard support
- Accessible by default in modern browsers
Cons
- Styling can be limited
- Inconsistent support across all assistive technologies
This is a great lightweight option for simple use cases but may fall short in more complex interfaces.

Option 2: Custom JavaScript Accordion with ARIA

If you need more control, a custom accordion allows full styling and behavior management—just be sure to handle accordion accessibility properly.

HTML Structure
```
<h3>
  <button aria-expanded="false" aria-controls="panel1" id="accordion1">
    Shipping Info
  </button>
</h3>
<div id="panel1" role="region" aria-labelledby="accordion1" hidden>
  <p>We offer free shipping on orders over $50...</p>
</div>
```
JavaScript snippet
```
const buttons = document.querySelectorAll('button[aria-expanded]'); buttons.forEach((button) => { const toggleAccordion = () => { const expanded = button.getAttribute('aria-expanded') === 'true'; button.setAttribute('aria-expanded', String(!expanded)); const panel = document.getElementById(button.getAttribute('aria-controls')); panel.hidden = expanded; }; button.addEventListener('click', toggleAccordion); button.addEventListener('keydown', (event) => { if (event.key === 'Enter') { toggleAccordion(); } }); });
```
This implementation not only handles basic interaction but also improves navigation for keyboard users. Combined with semantic structure and ARIA, it creates a robust and inclusive experience.

Best Practices to Keep in Mind
- Use Clear Labels: Avoid generic labels like “Section 1.” Use descriptive headers that make sense out of context.
- Provide Visual Cues: Arrows or plus/minus icons help users understand that a section is expandable. Consider animations that reinforce open/close behavior.
- Maintain Focus Indicators: Never remove focus outlines unless you’re replacing them with custom indicators that are just as visible.
- Be Selective with Accordions: Don’t hide critical content. It should be visible by default if the information is essential (e.g., pricing, legal disclaimers).
Testing Accessibility

Even well-intended implementations can miss the mark without testing. Include accessibility testing as part of your development workflow:
- Keyboard-Only Testing: Navigate the accordion entirely by keyboard.
- Screen Reader Testing: Use tools like NVDA, JAWS, or VoiceOver to check for correct announcements.
- Automated Tools: Run your component through tools like WAVE, or Lighthouse to identify missing attributes or ARIA misuse.
- Manual Code Review: Double-check that all attributes, labels, and roles are properly implemented.
Final Thoughts

Accessible accordions do more than organize content—they foster a better, more inclusive web. By prioritizing structure, semantics, ARIA roles, and thoughtful interaction design, you empower all users to engage with your content meaningfully.

If you’re unsure where to start or want to ensure your components meet accessibility standards, consider working with an experienced accessibility partner like 216digital. We specialize in helping teams build digital experiences that work for everyone—by default, and with accordion accessibility baked in.
Greg McNeil

March 27, 2025

How-to Guides

Accessibility, accordion, accordion accessibility, How-to, web developers, web development, Website Accessibility
What Is Audio Description?
Imagine trying to enjoy a movie when you can’t actually see what’s on the screen. Suddenly, a huge portion of the story—communicated by the actors’ gestures, the set design, and other visual elements—becomes almost impossible to follow. This is where audio description comes in.

For people who are blind or have low vision, audio description is a vital tool that helps them understand what is happening on screen. It turns visual information—like who is walking, what they are wearing, and how they move—into words that fill in the gaps left by dialogue alone. By including audio descriptions, developers can help build a more inclusive internet that meets everyone’s needs.

What Is Audio Description?

Audio description (AD) is defined as “the verbal depiction of key visual elements in media and live productions.” It is a spoken narration that explains what viewers would normally learn from sight alone. AD covers facial expressions, important movements, scene changes, costumes, and on-screen text. Think of AD as the spoken equivalent of alt text for images. Just like alt text describes a picture’s contents when you can’t see it, audio description tells you what is happening visually when you are unable to follow by sight.

Because so many key story elements are conveyed without dialogue, AD ensures blind or low-vision users are not missing out. For instance, a character might make a worried face or show a letter to another actor without saying anything. Without words describing these details, viewers may lose track of the story. That is why this accessibility measure is so important—not just for visual comprehension, but also for equal participation in popular culture.

How Is Audio Description Created?

Creating audio descriptions is both an art and a science. It calls for careful planning and precision so the narration enriches the original content without interrupting dialogue or other important sounds. In general, there are two main steps: writing the script and voicing the narration.

Writing the Script

A trained describer, or sometimes an automated tool, watches the content and notes crucial visual elements that are not otherwise explained. This includes body language, set design, and even text on signs. A human writer can craft a highly accurate script, but some creators use AI-generated drafts as a starting point. A hybrid approach—AI plus human editing—can offer speed and cost benefits while maintaining quality. Once the script is ready, it is carefully timed to fit into breaks between lines of dialogue or music cues.

Voicing the Description

The next step is to record the narration. Human-voiced AD typically uses professional voice actors who can deliver the right tone and clarity. An alternative is synthesized speech, where a computer-generated voice reads the script. This can be faster and cheaper but might lack the warmth and nuance a human can provide. After recording, an audio engineer mixes the new narration with the existing soundtrack. Quality assurance is essential: the final version must be clear, accurate, and properly timed so it helps the viewer without overwhelming the original audio. Many organizations also test the finished product with actual users to confirm it meets their needs.

How Is Audio Description Published?

When it comes to publishing audio descriptions online, developers have a variety of technical approaches:
- User-Selectable Audio Track: Many streaming services and video players provide a separate track that includes AD, often referred to as a Secondary Audio Program (SAP).
- Pre-Mixed Versions: Sometimes, the AD is integrated directly into the main audio track, so every listener hears the narration by default.
- Extended or Integrated Descriptive Audio: In content with rapid action, an extended track may pause or slow the video to allow sufficient time for detailed narration.
- Separate Files on Streaming Platforms: Services like Netflix, Disney+, and Amazon Prime frequently offer multiple audio versions, including AD, which viewers can select. Physical media (DVDs, Blu-rays) often include these options too.
- Mobile Apps and Live Performances: Apps can synchronize real-time narration with a live show or museum exhibit, allowing users to hear descriptions without disturbing others.
- Text-Based Alternatives: If adding audio tracks isn’t feasible, a WebVTT description track can be paired with a screen reader to deliver the same information through speech.
Benefits of Audio Description

While the primary users of this feature are people who are blind or have low vision, there are many others who benefit. Students who like to listen to content while taking notes, commuters who cannot watch a screen, and people who multitask all gain from this practice. Even individuals seated far from a display or those preferring a more multi-sensory viewing experience can find it helpful.

For content creators, adding audio descriptions can grow their audience and boost engagement. Accessibility also supports legal compliance in many regions, protecting organizations from potential lawsuits or fines. Beyond that, it improves a brand’s reputation by demonstrating care for all viewers. Some producers have even seen gains in search engine optimization (SEO) when they create written scripts or transcriptions as part of the process, which can lead to better discoverability of their content online.

Alternative to Audio Description

In some cases, offering audio descriptions may not be possible or practical due to limited budgets, time constraints, or technical hurdles. Still, there are alternatives that can help ensure some level of accessibility:
- Descriptive Transcripts: A transcript that includes not just dialogue, but also details on the visuals. This gives readers enough information to follow the narrative independently.
- Captions with Added Context: Although captions are mostly designed for viewers who are deaf or hard of hearing, they can be adjusted to include simple notes like “[John grins]” or “[Mary enters the room],” aiding those who need more visual context.
- Embedded Descriptions in Dialogue: Some creators write scripts that naturally mention key visuals, such as, “Look at that bright red balloon floating into the clear sky!” This type of embedded language can fill in some gaps without a formal AD track.
- Assistive Technology Integration: Proper use of HTML, ARIA labels, and structured content can also help screen readers convey visual information more effectively.
- Live Describer Services: For virtual events or video calls, a live describer can offer on-the-fly narration. This can be a good choice if you cannot embed pre-recorded descriptions in the media.
Why Audio Description Is Worth Prioritizing

At its heart, accessibility is about recognizing each person’s perspective. When web developers and content creators integrate audio descriptions into their videos, they do more than fulfill legal requirements: they make a statement that everyone belongs. By adding thoughtful narration, you help paint the full picture for anyone who can’t see it, broadening your audience and enriching the viewing experience for all. Even small improvements can bring about major changes in how people engage with your content.

Collaborating with experts, like the team at 216digital, can guide you through each step, from scripting to publishing. In the end, it isn’t just another feature—it’s a powerful bridge to inclusivity, ensuring nobody is left out of the story.
Greg McNeil

March 25, 2025

How-to Guides, WCAG Compliance

audio description, captions, videos and audio content, WCAG, WCAG conformance
How to Make Your Marketing More Accessible

You know how important marketing is already. But the real question is: Who’s not getting your message?

It’s easy to assume your carefully crafted campaigns are reaching everyone—but are they? What about someone using a screen reader? Or someone experiencing cognitive overload from flashing images or cluttered layouts?

You’re already working with engagement rates, algorithms, and design trends if you’re a marketer or content creator. So why do you need to worry about accessibility, too? Because accessible marketing is not optional—it’s necessary if you want to reach more, protect your brand, and build more trust.

Let’s parse out the ways that accessibility intersects with marketing now—and how it actually puts you ahead in terms of competition.

Why Accessibility Matters in Marketing

Grow Your Audience—Organically

Consider this: nearly 16% of people globally possess a disability that affects how they use the internet. If your content or site isn’t accessible, you’re missing out on a significant portion of your audience. Adding accessible marketing helps those individuals, but it also has the effect of simplifying and enhancing the experience for all, making your brand more desirable and accessible.

Improve Your Brand’s Credibility

Audiences today notice—and appreciate—brands that are concerned with being inclusive. Brands like Microsoft and Apple have established trust by being considerate and inclusive behaviors. By adopting accessible marketing, you’re broadcasting a message loud and clear: you genuinely care about your audience. That sincerity boosts customer loyalty and turns customers into brand ambassadors.

Get a Natural SEO Boost

Here’s a practical advantage: accessible marketing tends to coincide with SEO best practices. Descriptive text and clear, well-structured content help search engines and assistive technologies comprehend your content better. By making your site more accessible, you’ll not only enhance user experience but also perhaps enhance your search result visibility.

Stay Compliant and Reduce Risk

You’re probably familiar with accessibility laws like the Americans with Disabilities Act (ADA) and guidelines such as Web Content Accessibility Guidelines (WCAG). Ignoring these standards can lead to serious legal consequences—something no brand wants to face. By integrating accessible marketing into your strategies, you proactively avoid these risks, protecting your business and its reputation.

Website Accessibility Tips

Make Your Content Easy to Navigate

Attempt to use only the Tab key to navigate through your site. Is it easy and self-evident? Good usage of headings (H1, H2, H3) isn’t all about design appearance—it helps users navigate without hindrance, especially those who rely on assistive technologies.

Always Add Alt Text to Images

Alt text is a short description of an image. Screen readers use this text to describe the image aloud for people who can’t see it. For example, if you have a photo of a smiling person holding a dog, your alt text could say, “A woman holding a small brown dog and laughing.”

When writing alt text, be clear and concise. Provide enough information so someone can imagine the picture if they can’t see it. This step takes only a few seconds per image, but it goes a long way in making sure everyone can follow along.

Use Clear Language and Short Sentences

Plain language is your friend. It cuts out fluff and makes your message easier to understand. Not everyone enjoys reading long paragraphs loaded with big words. Simple wording often performs better because people grasp the idea quickly. Then, they can respond, share, or buy without confusion.

Try to limit long sentences. If a sentence feels like it’s going on forever, break it into two. This helps your audience read faster and makes screen readers work better.

Check Keyboard Navigation and Focus Indicators

Not everybody is a mouse user. Well-designed visible keyboard focus indicators make it easy for users with keyboard navigation or assistive device users to access your site with ease.

Be Careful With Animated Content

Animated or blinking content can be distracting or even harmful to some users. When you use animations, always provide an easy way to pause or disable them.

Social Media Accessibility Best Practices

Alt Text Isn’t Just for Websites

Image descriptions (alt text) are supported by most social media platforms these days. Make it a habit—you’re taking a simple step toward accessible marketing.

Format Hashtags Clearly

Hashtags like #MarketingTips2023 (all capitals) are more screen-reader friendly than all-lowercase counterparts, increasing accessibility right away.

Limit Emoji Usage

Emojis are great, but they should be used only sparingly. Excessive emoji usage will provide messy audio experiences for screen reader users.

Tag Your Links with Care

“Click Here” is useless. Descriptive words like “Find our latest products” will all inform users properly of the intent of the link.

Multimedia Accessibility Strategies

Use Captions and Transcripts

Video marketing is a big part of many brands’ strategies. But some viewers are deaf or hard of hearing. Others can’t use sound at certain times, like when they’re in a library or a busy coffee shop. Closed captions let them follow the video’s message without hearing the audio.

A transcript is also helpful. It’s a written version of all the spoken words and important sounds in a video. Transcripts help search engines pick up on your keywords. This gives an added SEO boost.

Add Audio Descriptions

Audio descriptions explain to visually impaired viewers what they are missing. This action unequivocally demonstrates your brand’s commitment to accessible marketing.

Making Accessibility a Habit

Make Accessibility Part of Your Workflow

Accessibility need not be a burden. Incorporate it into your regular content creation processes—train personnel, prep checklists, and add accessibility into every campaign plan. Accessible marketing will be second nature in no time.

Regularly Improve

Accessibility is not set-and-forget. Regular testing with tools like WAVE or Lighthouse and feedback from real-life assistive tech users ensures that your marketing remains effective and inclusive.

Closing the Conversion Gap

Marketing is all about creating a connection—and that connection isn’t whole if parts of your audience are left behind. By committing to accessible marketing, you’re committing to better communication, more active relationships, and more relevant experiences for each and every individual who comes into contact with your brand.

So, how do you begin? Take what you already do so well and add accessibility to it. Utilize it to inform the way you design, write, and present content. And when you need advice, we at 216digital can keep everything in rhythm, accessible to everyone, and effective.

Great marketing is not just something that is seen or heard – it’s something that’s felt by everyone.

Greg McNeil

March 24, 2025

How-to Guides, The Benefits of Web Accessibility, Web Accessibility Training

Accessibility, Digital Marketing, Marketing, Web Accessibility, Website Accessibility
When Is a Skip Link Needed?
We’ve all been on websites that greet us with massive headers, menu bars crammed full of links, or flashy ads stretching across the top. With a mouse, you can scroll or click straight to the section you care about. But if you rely on a keyboard, you’re stuck tabbing through every link and button in that menu before you reach the main story. It can feel like trudging through a maze when you just want to dive into the content.

A skip link offers a simple shortcut: it lets keyboard users jump over that repeated stuff and land exactly where they need to be. In this article, we’ll explore how skip links fit into the Web Content Accessibility Guidelines (WCAG), why they matter for anyone who doesn’t browse with a mouse, and how they can make a site more enjoyable for all visitors—even the ones who love to scroll.

What Is WCAG’s Bypass Blocks Rule?

WCAG’s Success Criterion 2.4.1, known as “Bypass Blocks,” focuses on letting users skip past content that appears on every page, such as headers, navigation menus, and sidebars. These areas can become barriers for people who rely on keyboard navigation or use screen readers, since they have to listen to or Tab through every link each time they land on a new page.

Mouse users can ignore repeated elements by moving their cursor directly to the main section of the page. But if you are using a keyboard only, you have to press the Tab key multiple times to get beyond the menu or header. This extra effort can be frustrating. By contrast, a skip link makes it possible to jump straight to the main content with a single press of the Tab key and an Enter or Space to activate it. Cutting down on keystrokes is a big boost to usability and can remove physical strain for users with motor disabilities.

Do Landmarks and Headings Count as Bypass Tools?

Some people think that WCAG’s requirements force you to include a skip link no matter what. However, WCAG does not specifically demand that you place a “Skip to Main Content” link on your pages in every scenario. If you use proper HTML5 sectioning elements like <main> or set up ARIA landmarks with role= "main", you can fulfill the technical requirement.

When you use clear heading structures (<h1>, <h2>, etc.) and assign landmarks (role= "navigation", role= "banner") to your layout, many screen readers allow users to jump from one landmark or heading to another. This means they can skip large chunks of repeated content. However, there is a key drawback: these landmark shortcuts are tied to assistive technology. Keyboard-only users without a screen reader do not benefit from these features, because landmarks are not accessible through simple keystrokes like Tab. That is where a skip link proves especially helpful, providing an obvious and direct way to move focus into the main content.

Why a Skip Link Is Still Best Practice

Even if you are technically compliant with WCAG, many experts still recommend a skip link. Here’s why:
1. Keyboard-Only Users: Landmarks may help screen reader users, but they are not available to someone who only has a keyboard. A skip link is the only direct and reliable way to jump over repetitive elements.
2. Users with Motor Disabilities: Each extra keystroke can cause strain. Reducing the need to press Tab repeatedly makes it easier for people with limited mobility to explore your site.
3. Users with Cognitive Disabilities: Repeated menus and banners can be visually overwhelming and distracting. A skip link streamlines the experience by letting users focus on the main content faster.
Other Tools That Help With Page Navigation
- Provide a Skip Link: A short text-based link such as “Skip to Main Content” at the top of the page is a universal solution.
- Use HTML Sectioning Elements: Properly labeling <header>, <main>, and <footer> can help screen reader users identify page sections.
- Implement a Logical Heading Structure: When headings form a clear outline, it is easier for people to scan or jump to key areas, especially when assistive technology is involved.
Alternative Navigation Aids

While a skip link is vital, it’s not the only accessibility tool you can use. ARIA landmarks, for example, let you define elements like role= "navigation", role= "banner", or role= "main". Screen readers can use these roles to move focus to each region. Another strategy is to include access keys, which assign keyboard shortcuts to major parts of your site. Yet, these approaches are typically helpful only to those who know how to use them and have compatible assistive technology. For most keyboard users, a skip link remains the clearest and simplest tool.

How to Add a Skip Link the Right Way

A skip link should do more than just jump down the page; it needs to work with the keyboard in a smooth way. Here’s how:

Position the Link as the First Focusable Element

The best practice is to place the skip link at the very top of your page. This ensures it is the first element that gets focus when someone tabs through the page. A common method is to link to the main content area, marked by an ID like id= "main-content".

Ensure Proper Keyboard Functionality

When users activate the skip link, focus should land right on the main content area. For this to happen, that target element must be focusable. If <main> or the first heading is not normally focusable, you can add tabindex= "-1" to make it work. This step also helps users who use screen magnifiers, because the focus moves right to the main section visually.

Example:
```
<a href="#main-content">Skip to Main Content</a>


<main id="main-content" tabindex="-1">
    
</main>
Or, if you want to move focus to the first heading:
<a href="#first-heading">Skip to Main Content</a>


<h1 id="first-heading" tabindex="-1">Welcome to Our Site</h1>

```
Ensure the Skip Link Is Visible When Focused

Many designers hide the skip link until it gains focus. While this can keep the page looking tidy, it’s important that the link is fully visible and noticeable the moment someone tabs onto it. This visibility ensures that keyboard users know there is a helpful tool available. In some designs, leaving the skip link in plain sight all the time may be the best approach.

Mistakes to Avoid With Skip Links

Even if you add a skip link, a few errors can stop it from working as intended:
- Improper Hiding Techniques: If you use display: none; or visibility: hidden;, screen readers will not detect the link at all. Instead, use off-screen positioning so it remains accessible.
- Non-Focusable Targets: Forgetting to add tabindex= "-1" to the target means the user might land near the content but not actually focus on it. This can confuse people using screen readers or screen magnifiers.
- Skipping Too Much Content: Your skip link should jump over repeated menus, but it should not force users to skip crucial information, like an important heading that explains the page’s purpose.
Check That Your Skip Link Actually Works

Testing makes sure your skip link works well:
1. Keyboard Testing: Turn off your mouse and try to navigate the site by tapping through. Watch for the link to show up, and check that it drops you into the main area.
2. Assistive Technology Testing: Use a screen reader to confirm that your skip link is announced and that it moves focus correctly.
3. Cross-Browser Compatibility: Test in different browsers (Chrome, Firefox, Safari, Edge) to confirm that the skip link behaves the same everywhere.
Make Navigation Easy for Everyone with 216digital

Including semantic elements and ARIA landmarks can make your site meet the minimum requirements of WCAG, but offering a dedicated skip link goes a step further by improving usability for keyboard-only users, people with motor disabilities, and users who may become overwhelmed by repeated menus. Rather than viewing accessibility as a set of rules to follow, think of it as a way to create a smoother, more welcoming experience for all.

If you want a site that not only checks the compliance box but also feels inclusive to every visitor, consider working with a partner who understands the importance of thoughtful navigation. At 216digital, we specialize in designing web experiences that work for everyone. A skip link may seem like a small touch, but it can make a world of difference for those who need it. Let’s make the web more inclusive together.
Greg McNeil

March 21, 2025

How-to Guides

skip link, WCAG, WCAG conformance, web developers, web development
Getting Focused: Why Focus Order Matters for Web Accessibility
Most people never think about what it would be like to navigate a website without using their mouse. This is a reality for many users with visual or motor impairments. They rely on using other input modalities, such as the keyboard or gestures, to navigate a web page. This is where focus order comes into play.

In this post, we’ll look at what focus order is, why it’s so important, how it connects to the Web Content Accessibility Guidelines (WCAG), and the most common issues you’ll want to fix. Then, we’ll share a few tips on how to test and improve it on your own site.

Life Without a Mouse

Picture going through your favorite website using only your keyboard. You press Tab to jump from one link or button to another. If the focus order is set up right, you’ll move through the page in a smooth, logical sequence, usually from top to bottom. But if it’s not, you could land somewhere unexpected or miss entirely essential parts of the page.

For anyone who can’t use a mouse, a messed-up focus order often leads to frustration. Improper focus order can lead to the cursor jumping around the page illogically or preventing them from using necessary functionality.

Avoiding Common Pitfalls
1. Skipping Interactive Elements: If a link or button is not coded using the proper semantic HTML tag or does not have the correct attributes, it will not be focusable at all, and users who can’t use a mouse will be unable to interact with the element.
2. Jumping in Strange Ways: If you rely on random tabindex values or a messy HTML structure, the focus may go from the header to a random footer link before bouncing back up. That’s tough to follow.
3. Getting Trapped: Pop-ups, modals, and iframes can trap keyboard users if the code doesn’t let them tab out. People might get stuck until they refresh the page.
4. Invisible Focus: Many designers, developers, or store owners choose to hide the focus outlines for aesthetic purposes without realizing how many people rely on them to navigate the site. Without visible focus outlines, motor-impaired users have no idea which element is currently focused on or selected.
The WCAG Connection

Focus order plays a key role in meeting the standards laid out in WCAG. Some of the main ones include:
- 2.4.3 (Focus Order, Level A): Content should follow a logical order when tabbing through the page.
- 2.1.1 (Keyboard, Level A): All site functions should work with only a keyboard.
- 2.4.7 (Focus Visible, Level AA): People should see which element is active at all times.
- 2.4.11 & 2.4.12 (Focus Not Obscured, WCAG 2.2, Levels AA & AAA): The focused element has to remain visible instead of scrolling off-screen.
Meeting these criteria helps make sure your site is accessible and much easier to navigate.

Simple Tips to Get It Right
- Use the DOM Order: Write your HTML in the order you want people to move through the page. That way, you don’t have to force things with unique attributes.
- Use Correct Elements: If you have something clickable, make it a <button> or <a>. This makes it automatically focusable without extra work.
- Be Careful With tabindex: tabindex= “0” can help include an element in the natural focus sequence. tabindex= “-1” keeps something out of the normal flow but still lets you focus there with scripts. High or random values can create chaos.
- Manage Modals Properly: When a modal pops up, focus should jump into it. People should be able to tab around inside and close it without getting stuck. Once it’s closed, the focus should return to the element that opened it.
- Keep Focus Visible: If your brand style doesn’t match the default outline, customize it with a high-contrast border or box-shadow. Whatever you do, make sure people can still see where they are on the page.
Testing and Tweaking Your Site
1. Manual Testing – Put your mouse away and try tabbing through the page. Ask yourself if the order makes sense and if you can reach everything you need.
2. Browser Tools – Chrome DevTools and Firefox Accessibility Inspector can show you how each element appears in the accessibility tree, which can help you spot weird focus flows.
3. Automated Tests – Tools like WAVE and Lighthouse are helpful for flagging fundamental problems, though they won’t catch everything.
4. Real Users – If possible, ask people who rely on keyboard navigation to test your site. They’ll be the quickest to notice focus issues you might miss.
Wrapping Up

Focus order might sound like a small detail, but it’s a massive deal for those who rely on the keyboard to get around. A logical, precise tab sequence helps keep your site user-friendly, no matter who’s visiting. If you’re worried about your site’s accessibility, it’s never too late to run an audit or refresh your code.

Need extra help? Contact 216digital, where we specialize in creating accessible websites that work well for everyone. Whether you just need a quick review or a complete accessibility plan, we’re here to make your site feel welcoming for all kinds of users.
Greg McNeil

March 19, 2025

How-to Guides, WCAG Compliance

focus order, WCAG, WCAG conformance, web developers, web development
A Guide to Accessible Table Design & Development
Once upon a time, table design was web design. Before the elegance of CSS Grid or the flexibility of Flexbox, we built entire sites with <table>, <tr>, and <td> like it was second nature. They were the backbone of layout — the duct tape holding the early web together. But as web development matured, we traded layout tables for cleaner, more semantic code. Still, tables remain essential — not for layout, but for what they were truly meant to do: present data.

So, where do tables fit into modern, accessible web design? When are they appropriate, and how do we use them in a way that supports users of all abilities, including those using screen readers or keyboard navigation?

In this guide, revisit table design through a modern lens — not to reminisce about the old days of spacer GIFs and nested rows, but to examine how to use tables the right way today. Whether you’re structuring tabular data or dealing with legacy layouts, we’ll walk through practical techniques for designing and coding tables that are both functional and inclusive.

Understanding Tables in Web Design

Tables still serve a clear purpose in today’s web — when used thoughtfully. But there’s a key distinction: data tables are for presenting information, and layout tables… well, those belong in the same drawer as Netscape hacks and the blink tag. How you use them matters, especially for folks navigating with a screen reader or keyboard.

Understanding the difference is the first step toward solid, accessible table design that doesn’t leave users behind.

Data Tables

Need to show structured data like schedules, product comparisons, or sales reports? That’s what data tables were born to do. When used well, they make complex info digestible — like a well-organized spreadsheet that doesn’t make you want to flip your monitor.

Making Data Tables Accessible

Start with semantic HTML — <th> for headers, <caption> for context, and group rows and columns meaningfully. These tags are like orientation tools for assistive tech — they help users actually understand the structure, not just hear a blob of words.

Reading order is your next frontier. If your table reads like it was assembled after three espressos and a deadline, it’s time to regroup. Make sure users can follow the flow with no surprises.

And if you’re knee-deep in rowspans and colspans, it’s worth pausing to ask: “Is this actually helping, or am I just flexing?” Clean table design helps avoid this entirely.

Layout Tables

Let’s talk about the fossil in the room: layout tables. We all used them. Some of us even nested them. Some of us still wake up in cold sweats because of them.

Why They Were Used

Back in the day, if you wanted a three-column layout, you reached for a table. Pixel-perfect footer? Table. It was the best option we had — right up until CSS knocked politely and said, “I got this.”

Why It’s Time to Move On

CSS changed the game. Layout tables now clutter your markup, confuse screen readers, and break responsiveness faster than you can say “media query.” The result? A tangled mess that’s hard to debug and harder to maintain.

Golden rule: Tables for data. CSS for layout. Break this rule only under duress (or for archaeological purposes).

If you must touch layout tables, think of it less as designing a layout and more as preserving legibility. It’s a survival-style form of table design.

When You Have to Use Layout Tables

Sometimes, you inherit legacy code that’s more delicate than a house of cards. Or you’re working with a CMS that still thinks it’s 2003. When you’re stuck, the goal becomes minimizing the chaos.

Best Practices for Using Layout Tables (Responsibly)
- Skip semantic elements: Leave <th> and <caption> out. They’ll only mislead screen readers.
- Use role= "presentation": This politely tells assistive tech, “Nothing to see here — just visuals.”
- Keep content order logical: It might look fine, but hit the tab or turn on a screen reader. If it reads like a jigsaw puzzle, rework it.
- Make it responsive — sort of: You’re already doing something frowned upon. At least don’t let it collapse on mobile.
CSS to the Rescue

Need flexible, responsive, accessible layouts? CSS has your back. You’ve got two powerhouse options ready to roll.

CSS Grid Layout

CSS Grid is built for complex, two-dimensional layouts. It gives you surgical control over rows and columns without diving into the <td> abyss.

Heads-up: Keep your DOM order consistent with your visual order. Otherwise, assistive tech users will be piecing together your layout like a mystery novel.

CSS Flexbox

Flexbox handles one-dimensional layouts like a champ. Think nav bars, form groups, toolbars — anything that lines up in a row or column.

Just remember, Flexbox can reorder your layout visually, but screen readers still follow the source order. Rearranging things for aesthetics? Fine. Just don’t confuse your users while you’re at it.

Both of these tools help prevent misuse of tables and support better table design principles by removing the temptation to force non-tabular content into table markup.

Follow the Principles, Not Just the Code

Accessibility isn’t about ticking boxes — it’s about designing with real people in mind. Think about how someone actually experiences your content. No mouse. No visuals. Just structure, clarity, and flow.

If someone is using a screen reader, keyboard navigation, or sip-and-puff device, your clean CSS layout means nothing if your content order is a mess. Great table design considers these experiences from the start.

Key Guidelines from WCAG to Keep in Mind:
- Info and Relationships (1.3.1): Use markup to show how data connects. Don’t rely on appearance alone.
- Meaningful Sequence (1.3.2): Your content should flow in a way that makes sense, both visually and in the code.
Quick Recap: Best Practices
- Use tables only for tabular data — not layout, not nostalgia
- Mark up data tables semantically — <th>, <caption>, proper scope
- Use CSS (Grid or Flexbox) for layout — always
- Only use layout tables when you absolutely have no other option
- If you must use layout tables, strip out semantics and add role=" presentation"
- Don’t rely on automated tools alone — test with real assistive tech
Final Thoughts

The web’s grown a lot since the days of spacer GIFs and table-based layouts — and thankfully, so have our tools. We can build cleaner, more flexible, more inclusive sites with far less hassle than we could a decade ago.

So let’s do that. Use tables where they belong — to present data. Embrace modern CSS for everything else. And always remember: building for accessibility doesn’t slow you down. It just makes your work better.

And if you’re ever elbow-deep in a legacy layout table with seven levels of nested <tr>, know this: someone out there gets it. And they’re probably muttering “never again” right along with you — while dreaming of cleaner table design.
Greg McNeil

March 18, 2025

How-to Guides

Data tables, How-to, table design, web developers, web development
Coffee Shop Website Accessibility: What’s Missing?
Have you ever visited a coffee shop’s website to check their menu, order online, or see their hours? Did you feel lost because the site was confusing? Now, imagine dealing with that struggle each time you want to find your go-to latte. Or when you want to learn about a shop’s new roast. For people who rely on screen readers or have other visual impairments, that frustration can happen a lot.

Many coffee shop owners and content creators in the United States might not realize these barriers exist. Making sure everyone can move around your website without trouble is more important than you might think. In this post, I’ll point out some common obstacles and why they matter. I’ll also share how a few small changes can make a big impact.

Why Does Coffee Shop Website Accessibility Matters?

When you think about coffee shops, you might picture a warm atmosphere and friendly baristas. You might also imagine the smell of freshly brewed beans. Online, we want to capture that same welcoming feeling. By focusing on coffee shop website accessibility, we want to make sure people can order their favorite drinks. We also want them to read menu items or discover new roasts without trouble.

If a visually impaired customer struggles to find key details, they might miss out on daily deals or new seasonal drinks. They could even miss basic facts like store hours.

One often overlooked detail is how screen readers work. These tools read text out loud to users who can’t see the screen. If a website isn’t organized well, or if images don’t have good descriptions, screen reader users can miss key details. It’s crucial to keep everything labeled and clear. That could mean they never learn about your limited-edition pumpkin spice latte or your special buy-one-get-one-free deal. By making a few updates, you can share the joy of your coffee shop with everyone who visits online.

Missing Alt Text for Images

Coffee shops show off photos of their specialty drinks, pastries, and interiors. There’s nothing quite like seeing a perfectly steamed latte art design on the homepage. However, if these images don’t include a brief written description (often called “alt text”), a screen reader can’t share that info with someone who is visually impaired. That leaves them guessing what’s in the image.

What to do:
- Make sure each picture has short alt text that describes what’s shown. If you have a frothy cappuccino in a ceramic mug with a leaf design on top, write something like, “Cappuccino with leaf latte art in a white mug.”
- Keep it simple and clear. A few words can help everyone enjoy the same tasty-looking photos.
Hard-to-Read Text and Poor Contrast

Sometimes, coffee shop websites use warm and earthy color palettes to match the cozy vibe of a local café. But light brown text on a cream background can be hard for many people to read. Dark red lettering on a black background can cause the same problem.

If your text and background colors don’t have enough contrast, users might struggle to read menu items or promotions. They could also miss important contact details.

What to do:
- Pick colors with high contrast, so text stands out. You can use free online contrast-checker tools.
- Keep text large enough so visitors of all ages can comfortably read your menu and shop info. Test on a phone or tablet to see if users need to zoom in.
Unclear Headings and Structure

Have you ever looked at a website and felt lost because everything blended together? Using clear headings and labels helps both sighted users and people with screen readers navigate your site.

When your text is broken into sections like “Our Menu,” “About Us,” “Location,” and “Contact,” users can jump right where they need to go. This layout helps both sighted users and screen readers. Screen readers also rely on proper heading levels (like H1, H2, H3) to guide listeners in the right order. If headings aren’t used correctly, the page can feel disorganized for those who can’t see it.

What to do:
- Give each page a main heading (H1), then use H2s and H3s for subheadings.
- Don’t skip heading levels. Going from H1 to H3 can confuse people using screen readers.
Unlabeled or Unclear Links and Buttons

Buttons like “Order Now,” “Sign Up,” or “View Menu” should clearly say what they do. If a button only says “Click Here,” screen reader users might not know what “here” refers to. The same goes for links.

If many links are labeled “Learn More,” it’s tricky to figure out which page or product each link goes to. Users might have to guess or click blindly.

What to do:
- Use descriptive link and button text, like “Order a Latte” or “Learn About Our Pastries.”
- If you offer online ordering, label each step so people know exactly what to do next.
Forms Without Proper Labels

Some coffee shop websites have newsletter sign-up forms or contact forms for special orders. If these forms aren’t labeled well, a screen reader might say something like “edit box” instead of “email address.” That can leave users guessing what to type.

What to do:
- Label each form field clearly. For instance, use “Name” or “Email Address” so people know what goes where.
- Provide helpful error messages. If someone enters an invalid email, explain what happened and how to fix it.
Videos Without Captions or Transcripts

Video might not be the first thing that comes to mind for a coffee shop website. Still, some shops post video tours, latte art tutorials, or interviews with the barista. If these don’t have captions or transcripts, users who are deaf or hard of hearing could feel left out. Good website accessibility means making the site easy for everyone, not just folks with vision challenges.

What to do:
- Add captions to your videos or provide a simple transcript. This helps anyone who can’t hear or who’s watching in a quiet place (or a super noisy one).
How to Get Started

Improving coffee shop website accessibility doesn’t have to be complicated. You can start by using free online tools that scan your pages and highlight issues like missing alt text or low contrast. It also helps to ask a few friends or loyal customers to test your site and tell you what works and what doesn’t.

If you find bigger problems, think about working with a web developer who understands website accessibility. They can guide you through changes and help you meet standards commonly used in the United States. Even small fixes can create a smoother online experience for everyone, from a busy parent ordering pastries for the weekend to a coffee enthusiast searching for a new blend to try.

A Warm Welcome, On and Offline

When people walk through your coffee shop’s door, you greet them with a smile. Why not do the same online? A website that’s easy to use creates that same feeling of warmth and belonging. Whether someone’s checking your menu for gluten-free treats, ordering a bag of beans for home, or simply browsing the specials, clear labels and good navigation make them feel included.

By focusing on coffee shop website accessibility, you open your digital doors to everyone. It’s a great way to build community, grow your business, and show off what makes your café special. After all, everyone deserves to enjoy that perfect cup of coffee—no matter how they get there.

If you’re ready to make your coffee shop’s website more accessible but aren’t sure where to start, 216digital can help. We specialize in website accessibility solutions tailored to small businesses, making sure your site is welcoming for everyone. Let’s work together to create a seamless online experience—just like the one you offer in your shop.
Greg McNeil

March 14, 2025

How-to Guides, WCAG Compliance

Accessibility, coffee shop, forms, Image Alt Text, videos and audio content, Web Accessibility

Relying on Color Alone

Poor Contrast Between Text and Background

Hover-Only Interactions

Hiding or Removing Focus Styles

Icon-Only Buttons Without Labels

Vague Link Text

Layouts That Fall Apart When Text Is Resized

Skipping Alt Text on Images

Hard-Coded Font Sizes

Overly Complex Navigation

Where Good Design Meets Real-World Impact

Why Accessibility Matters in E-Commerce

Making Your Shopping Cart Work for Everyone

Add Clear Labels (Yes, Even for Buttons)

Let People Update Cart Items Without Guesswork

Show Helpful Feedback When Things Go Wrong

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

Use Straightforward, Consistent Labels

Make Sure Users Can Tab Through Fields Logically

Show Errors Clearly and Offer Suggestions

Designing a Payment Flow That’s Smooth and Inclusive

Offer More Than One Way to Pay

If You Use CAPTCHAs, Make Them Accessible

Choose Accessible Payment Gateways

Don’t Let Product Filters Be a Barrier

Make Filters Keyboard-Friendly

Let Users Know What Filters Are Applied

Stick to Native HTML Controls When Possible

Testing and Validating Your Work

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

Test Manually with Real Assistive Tech

Get Feedback from Real Users

Small Fixes, Big Impact

What Is Alt Text?

What Are Image Descriptions?

Alt Tags vs. Image Descriptions: Key Differences

How Image Descriptions Support Both Accessibility and SEO

Tips

SEO Pitfalls That Undermine Accessibility

Here’s What to Avoid

A Better Approach

Why Accessibility Must Come First

Best Practices for Writing Accessible Image Descriptions

The Role of Content Creators, Developers, and Marketers

A Better Internet Starts with Better Habits

Why Accordion Accessibility Matters

The Building Blocks of an Accordion Accessibility-Friendly Component

1. Structure: Header and Panel

Header (Trigger)

Panel (Content)

2. Keyboard Navigation

3. Use Semantic HTML

Best Practices for Accordion Accessibility

Why <button> and not <div> or <a>?

4. Implementing ARIA Attributes

ARIA Attributes for Accordion Accessibility

Implementation Examples

Option 1: Native HTML with <details> and <summary>

Pros

Cons

Option 2: Custom JavaScript Accordion with ARIA

HTML Structure

JavaScript snippet

Best Practices to Keep in Mind

Testing Accessibility

Final Thoughts

What Is Audio Description?

How Is Audio Description Created?

Writing the Script

Voicing the Description

How Is Audio Description Published?

Benefits of Audio Description

Alternative to Audio Description

Why Audio Description Is Worth Prioritizing

Why Accessibility Matters in Marketing

Grow Your Audience—Organically

Improve Your Brand’s Credibility

Get a Natural SEO Boost

Stay Compliant and Reduce Risk

Website Accessibility Tips

Why `<button>` and not `<div>` or `<a>`?

Option 1: Native HTML with `<details>` and `<summary>`