216digital.
Web Accessibility

Phase 1
Web Remediation for Lawsuit Settlement & Prevention


Phase 2
Real-World Accessibility


a11y.Radar
Ongoing Monitoring and Maintenance


Consultation & Training

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

Web Design & Development

Marketing

PPC Management
Google & Social Media Ads


Professional SEO
Increase Organic Search Strength

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

About

Blog

Contact Us
  • 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
  • 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>
    <!-- Header, Navigation, and other repeated content -->
    
    <main id="main-content" tabindex="-1">
        <!-- Main content -->
    </main>
    Or, if you want to move focus to the first heading:
    <a href="#first-heading">Skip to Main Content</a>
    <!-- Header, Navigation, and other repeated content -->
    
    <h1 id="first-heading" tabindex="-1">Welcome to Our Site</h1>
    <!-- Main content -->

    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
  • Keyboard Accessibility: A Guide for Web Developers

    Think about the last time you visited a website with a complex menu or a long list of links. If you tried navigating without a mouse—maybe because you found it faster to use the Tab key—you might have encountered invisible outlines, a random tab order, or even getting stuck in a popup with no clear way out. These problems highlight why keyboard accessibility is essential.

    When websites are built so that every button, link, and form field is accessible via keyboard, it becomes easier for everyone to navigate and complete tasks.

    What Is Keyboard Accessibility?

    At its core, keyboard accessibility ensures that everything on a website can be reached and used without a mouse. This is crucial for people with motor impairments who rely on keyboards or assistive devices, as well as users with visual impairments who navigate with screen readers. Even power users benefit, often finding keyboard shortcuts and navigation faster than using a mouse.

    Beyond improving usability, proper keyboard accessibility leads to better-organized code and a more logical page structure—benefits that search engines reward with better SEO rankings. Simply put, improving keyboard accessibility benefits both users and website owners. However, achieving it comes with challenges.

    Common Keyboard Accessibility Challenges

    Despite its importance, keyboard accessibility is often overlooked. Many websites suffer from poor focus visibility, illogical tab orders, and keyboard traps that frustrate users. Addressing these pitfalls is key to creating a smooth, user-friendly experience.

    Below are three of the most common keyboard accessibility issues—and how to fix them.

    1. Designing Effective Focus Indicators

    Focus indicators visually highlight which element is currently selected when navigating with a keyboard. They help users track their position as they move through a webpage using the Tab key.

    Why Focus Indicators Matter

    Imagine navigating a website solely by keyboard. If you press Tab but can’t see where you are because the focus highlight is too faint—or missing altogether—you’re left guessing. This creates confusion and frustration. Clear, high-contrast focus indicators ensure users always know where they are on the page.

    Best Practices for Focus Indicators

    • Outline thickness: At least 2 CSS pixels
    • Outline offset: Keep at least 2 CSS pixels between the outline and the element’s edge
    • Contrast ratio: A minimum of 3:1 between the focus indicator and the background

    Understanding the :focus-visible Pseudo-Class

    The :focus selector applies styles whenever an element gains focus, including when it’s clicked with a mouse. But :focus-visible applies focus styles only when an element is navigated via keyboard, keeping the interface clean for mouse users while ensuring keyboard users get clear visual cues.

    Example:

    *:focus-visible {
      border: 2px solid black; /* Ensure noticeable contrast */
      outline-offset: 2px;
    }

    2. Maintaining a Logical Navigation Order

    Users navigate websites sequentially using the Tab key. The focus order should match the visual layout to avoid confusion. A mismatch disrupts the browsing experience, making it difficult for users to predict what comes next.

    Tips for Logical Navigation

    • Use proper HTML structure: Semantic elements like headers (<h1> – <h6>), lists, and landmarks guide screen readers and browsers to interpret content correctly.
    • Avoid positive tabindex values: Manually setting a positive tabindex can force elements into an unnatural order, leading to confusion.
    • Provide “Skip to Main Content” links: These allow users to bypass repetitive navigation and jump straight to the main content.
    • Beware of keyboard traps: Ensure users can always navigate away from popups, modals, or embedded elements using only the keyboard.

    3. Proper tabindex Implementation

    The tabindex attribute controls how elements receive focus. While useful in some cases, it’s often misused.

    What tabindex Does

    • tabindex="0": Inserts the element into the default tab order based on its position in the DOM. Ideal for custom interactive elements like <div> buttons.
    • tabindex="-1": Removes an element from sequential keyboard navigation but allows focus via scripting. Useful for modals or hidden elements.
    • Positive values (e.g., tabindex="1"): Best avoided, as forcing a custom order can break the expected tab sequence and frustrate users.

    Best Practices

    • Use semantic HTML (<button>, <a>), which is naturally keyboard-accessible.
    • Avoid adding tabindex to non-interactive elements like text or static images.
    • Use negative tabindex for hidden or modal content that should only receive focus under certain conditions.
    • Stick to the natural tab order whenever possible—custom focus orders should be a last resort.

    Testing Your Website’s Keyboard Accessibility

    Even with best practices in place, testing is essential to catch issues before they impact users. A combination of manual and automated testing provides the most reliable results.

    Manual Testing

    • Navigate using only a keyboard: Use the Tab key to move through all interactive elements. Press Enter (or Space) to activate buttons and links.
    • Check focus visibility: Ensure focus indicators are always clear and meet contrast requirements.
    • Verify logical tab order: Does the sequence make sense based on how someone would naturally read or navigate your page?
    • Watch for keyboard traps: Ensure modals, dropdowns, and embedded content allow users to navigate away freely.

    Automated Testing Tools

    Browser-Based Tools

    • Firefox Accessibility Inspector: Displays how the browser interprets focusable elements.
    • Chrome DevTools (Accessibility Panel): Helps analyze the site’s structure.
    • WAVE Evaluation Tool: Flags potential accessibility issues directly in the browser.

    While these tools are powerful, nothing replaces real user feedback. Testing with people who rely on keyboard navigation often reveals hidden issues automated tools miss.

    Conclusion

    Keyboard accessibility is a fundamental part of inclusive web design. Making sure users can navigate your site without a mouse ensures better usability for everyone—including people with disabilities who rely on keyboard navigation. Plus, it improves SEO, usability, and compliance, making it a win-win for both users and businesses.

    The best practices covered here—such as customizing focus indicators, maintaining a logical tab order, and using tabindex responsibly—are essential steps toward a more accessible website. Regular testing, both manual and automated, helps ensure your site meets WCAG guidelines and delivers a smooth experience for all users.

    For expert guidance, consider working with accessibility professionals like 216digital. Specialists can help you implement strategies that go beyond basic compliance, ensuring long-term usability and inclusivity. When you prioritize keyboard accessibility, you create a more welcoming web for everyone—and that’s a goal worth striving for.

    Greg McNeil

    March 13, 2025
    How-to Guides
    Accessibility, keyboard accessibility, Keyboard Navigation, tabindex, Web Accessibility, web developers, web development
  • How to Make Mega Menus More Accessible

    A mega menu is typically a large, two-dimensional panel that appears when a user interacts with a top-level navigation item. It’s often used by eCommerce stores or websites with many different product categories or content sections. Because it can display a wide variety of links in a single view, a mega menu helps visitors explore your site quickly—no endless drilling down into submenus.

    But here’s the catch: while mega menus make navigation simpler for many users, they can also create barriers for some. For example, hover-triggered mega menus might be useless for someone relying on a keyboard. Or, if the menu isn’t properly labeled, a screen reader user might get stuck in a confusing loop of unlabeled links.

    These barriers matter because web accessibility is not just about following rules—it’s about ensuring everyone can use your site. If you leave people out, you risk alienating customers who want to purchase your products or read your content. So, let’s dive into some common accessibility issues and how to fix them.

    Overcoming Common Accessibility Challenges

    Improving Hover Functionality

    Most mega menus open when you hover your mouse over the navigation item. However, hover-based menus can cause big problems for keyboard users (or anyone who can’t use a mouse).

    • Inaccessible for Keyboard Users: People who navigate with the keyboard use the Tab key to move from link to link. If a menu only opens on hover, these users can’t open the submenu.
    • Overly Sensitive Interactions: Sometimes, mega menus can pop open or shut at the slightest movement of your mouse. This makes them frustrating to use for everyone.
    • The “Diagonal Problem”: If you move the mouse at an angle, you can sometimes trigger submenus you didn’t intend to open.

    Best Practice: Use a click to open the submenus instead of relying on hover. This way, both mouse and keyboard users have a more predictable experience. A click is a clearer signal of intention, reducing accidental openings or closings.

    Making Menus Easy to Close

    A menu that’s hard to dismiss can trap users, especially if it covers a large portion of the screen. On the other hand, a menu that closes too quickly can frustrate users who accidentally hover away for a split second.

    Solutions:

    1. Escape Key Support: Let users close the menu by pressing the Escape key. This is a standard expectation in many UI patterns and helps keyboard users exit quickly.
    2. Delayed Closing: If you decide to keep some hover functionality, add a slight delay before the submenu disappears. This grace period prevents the menu from closing by mistake if a user’s pointer drifts outside the panel for a moment.

    Enhancing Keyboard Accessibility

    Logical Keyboard Navigation

    Keyboard navigation is a critical part of web accessibility. You want the user’s Tab key presses to move in a clear, intuitive order:

    1. First Tab: Highlight the first top-level navigation item.
    2. Enter Key: If the focused top-level item has a submenu, pressing Enter opens that submenu. Pressing Enter again on any submenu item activates the link.
    3. Tab Within a Submenu: Moves focus to the next item in the submenu.
    4. Escape Key: Closes the submenu and returns focus to the parent menu item.
    5. Shift + Tab: Moves backward through the items, letting users navigate in reverse.

    This logical flow ensures that people who rely on the keyboard won’t get lost or stuck.

    Providing Clear Focus Indicators

    When users press Tab, they should be able to see exactly which menu item is highlighted. This means using visible focus indicators:

    • A change in background color, an underline, or a bold outline helps users quickly spot the focused item.
    • Make sure the color contrast meets accessibility guidelines. Avoid using color alone—some users might not see color differences clearly. An underline or border is a more reliable visual cue.

    Optimizing Screen Reader Support with ARIA

    Choosing the Right ARIA Roles

    Using role= "menu" for all navigation is a common mistake introduced in development. This role should only be used if your navigation behaves like a desktop application menu. For most website mega menus, it’s better to use simpler roles.

    Recommended roles and attributes:

    • role= "navigation": Declares that this section is a navigation landmark, which helps screen reader users quickly find or skip it.
    • role= "menuitem": If you have interactive items that function like menu items (though for basic links, standard <a> elements might be enough).
    • aria-haspopup= "true": Indicates that a button or link has a submenu.
    • aria-expanded= "false": Tells screen readers if a section is closed. Switch it to true when the submenu opens.

    Labeling and Describing Elements Properly

    Screen readers need helpful labels to convey what the link or button does. If your button opens a “Products” submenu, label it clearly:

    • Use aria-label= "Products Menu" or aria-labelledby=" [ID_of_label]" to associate a descriptive label with the menu.
    • Provide descriptive link text. Instead of “Click here,” use something like “View our latest products.” This helps all users know exactly where the link leads.

    Implementing Accessible Mega Menus with HTML, CSS, and JavaScript

    Using Semantic HTML for Proper Structure

    Below is a simple example showing how to structure an accessible mega menu:

    <nav aria-label= "Main Menu">
      <ul>
        <li><a href="#">Home</a></li>
        <li>
          <button aria-expanded="false" aria-haspopup="true">Products</button>
          <ul>
            <li><a href="#">Product 1</a></li>
            <li><a href="#">Product 2</a></li>
          </ul>
        </li>
      </ul>
    </nav>

    Here’s why this works:

    • <nav aria-label= "Main Menu">: The <nav> element is a semantic way to mark the navigation area. The aria-label helps screen readers identify it.
    • <button> vs. <a>: Using a button for expandable menus is more accessible because it’s an interactive element by default and can easily handle the aria-expanded state.
    • aria-expanded: Indicates whether the submenu is open or closed (true or false).

    Styling Menus for Visibility & Interaction

    Accessible styling goes beyond making things “look nice.” It ensures that focus states are clear. For instance:

    nav button:focus {
      outline: 2px solid #005ea2;
      background-color: #f1f1f1;
    }
    nav ul ul {
      display: none;
    }
    nav button[aria-expanded="true"] + ul {
      display: block;
    }
    • The outline property and background-color change help users see the focused button.
    • By default, submenus are hidden (display: none).
    • When aria-expanded= "true", the submenu appears (display: block).

    Enhancing Usability with JavaScript

    A small amount of JavaScript can make your menus more accessible. Here’s how you can toggle the aria-expanded attribute:

    document.querySelectorAll('nav button[aria-haspopup]').forEach(button => {
      button.addEventListener('click', () => {
        const expanded = button.getAttribute('aria-expanded') === 'true';
        button.setAttribute('aria-expanded', !expanded);
      });
    });
    • This code finds every button with aria-haspopup.
    • When clicked, it checks if aria-expanded is currently true, then toggles it.
    • This prevents menus from randomly opening on hover and gives users control.

    Accessible Navigation Is an Ongoing Commitment

    Building an accessible mega menu isn’t a one-and-done project. It takes careful planning, coding, and constant testing to make sure all users can move through your site with ease. However, the payoff is huge: better usability for everyone, including people with temporary or permanent disabilities, and compliance with accessibility standards like WCAG.

    Remember, accessibility benefits everyone. Even a user with a short-term injury or someone on a small mobile device can benefit from keyboard-friendly and screen-reader-friendly menus. By making small changes to HTML, CSS, ARIA attributes, and JavaScript, you can open up your site to a larger audience and provide a smoother experience for all.

    If you need expert guidance on web accessibility or want a thorough audit of your online store, 216digital can help. We specialize in creating inclusive, user-friendly experiences that keep your customers coming back and keep your website on the cutting edge of accessibility best practices. Don’t let your mega menus become mega barriers—start making them accessible today!

    Greg McNeil

    March 11, 2025
    How-to Guides
    Accessibility, accessible code, How-to, mega menu, web developers, web development, Website Accessibility
  • 6 Ways to Improve Icon Accessibility in Web Design

    Icons are everywhere in web design—on navigation menus, buttons, and even instructional graphics. They help users navigate, take action, and understand content at a glance. But just because an icon looks great doesn’t mean it’s effective for everyone. When it comes to creating inclusive websites, icon accessibility is crucial. If an icon is confusing or too small, it can frustrate users, create barriers, and even cost you traffic or conversions. That’s why accessibility and usability should be top priorities.

    In this article, we’ll explore six actionable ways to improve icon design so that your icons are clear, usable, and accessible to all users, including those with disabilities. Whether you’re a website owner, content creator, or web developer, these tips will help ensure your icons work well for everyone, including people with visual, motor, or cognitive impairments.

    1. Make Your Icons Easy to See

    Contrast Matters

    When designing icons, it’s significant that they stand out from the background rather than blend in. The Web Content Accessibility Guidelines (WCAG) recommend a contrast ratio of at least 4.5:1 for text and images of text. Icons, especially those carrying critical information, should meet or exceed this contrast standard.

    Why It’s Important

    Low-contrast icons can be almost invisible to users with vision impairments, complicating navigating or completing tasks on your site.

    How To Do It

    Tools like the WebAIM Contrast Checker can help you confirm that your color choices meet accessibility guidelines. If your background is light, ensure your icons are noticeably darker, and vice versa.

    Size Counts

    Just as crucial as contrast is icon size. Small icons can be a nightmare for users with poor vision or those who rely on assistive technology like screen magnifiers. They can also pose a challenge for people with motor disabilities who struggle to tap or click small icons accurately.

    Recommended size

    Aim for an icon touch target of at least 44×44 pixels. This size gives enough space for a user’s finger or cursor to select the icon without accidentally triggering something else.

    Common pitfalls

    Anything smaller than 24×24 pixels is typically too small to be easily clicked or tapped. If you’re designing for mobile, remember that users’ fingers are bigger than a precise mouse pointer.

    2. Always Pair Icons with Text

    Relying solely on icons can create confusion, especially if your visitors aren’t familiar with certain symbols. A perfect example is the infamous “hamburger menu.” While common in modern design, not everyone recognizes what the three stacked lines represent. By adding a text label, you remove any guesswork.

    Why It’s Important

    Text labels make icons understandable for users who might not recognize specific symbols. They also provide additional context for screen readers, who may not interpret icons alone correctly.

    • Bad example: A search button that shows only a magnifying glass icon.
    • Good example: Pair the magnifying glass icon with the word “Search.” This ensures clarity for everyone.

    Including text labels is a simple but effective step toward better icon accessibility and can drastically improve user experience.

    3. Use Clear, Functional Alt Text

    Alt text (alternative text) plays a vital role in accessibility. It’s a description that screen readers read aloud for users who can’t see the images on a page. Regarding icons, the alt text should describe the icon’s function rather than its appearance.

    • Examples: Bad: alt= “Icon of a house”
    • Good: alt= “Go to homepage”

    If the icon is purely decorative and conveys no essential information, mark it as aria-hidden= "true" or use an empty alt="" to keep screen readers from reading irrelevant content.

    Use Proper Coding Techniques

    Depending on the format of your icon, there are slightly different approaches to ensure screen readers interpret them correctly:

    1. <img> elements → Use the alt attribute, like alt=”Search button”.
    2. SVG icons → Provide a <title> tag within the SVG file or inline code.
    3. Icon fonts → Sometimes, screen readers treat icon fonts as text characters. Use aria-hidden= "true" for the icon itself, and include hidden text (e.g., <span class= "visually-hidden">Search</span>) for accessibility.

    This attention to detail ensures that people using screen readers will know the icon’s function without having to interpret a cryptic or generic description.

    4. Be Consistent with Icons

    Consistency is key in web design, especially regarding icon accessibility. Each icon should have a clear meaning across your entire website or app.

    Why It’s Important

    If you use a magnifying glass icon to indicate “Search” in one area of your site, using the same symbol for “Zoom” somewhere else can confuse users. A confused user is more likely to leave your site or miss important content.

    Avoid Multiple Meanings

    Don’t use one icon to represent more than one function. This can break user trust and make them second-guess every click.

    By keeping your icons consistent, you help users develop familiarity with the symbols on your site. Reducing the cognitive load for everyone, including users with disabilities who rely on screen readers or keyboard navigation.

    5. Make Icons Keyboard & Assistive Tech Friendly

    Some users cannot use a mouse or touchpad and rely solely on their keyboard. Others use assistive technology like screen readers or voice control. Ensuring your icons work with these tools is essential for accessibility.

    Keyboard Navigation

    Every interactive icon should be reachable and operable using only a keyboard. Users should be able to tab to an icon and activate it with the Enter or Spacebar keys.

    • Tips: Use logical tab ordering in your HTML to ensure icons follow a coherent navigation sequence.
    • Ensure focus styles are visible (e.g., a visible outline or highlight around the icon when selected).

    Screen Reader Support

    Icons can easily confuse screen reader users if not labeled correctly. This is where ARIA labels or hidden text come into play. For instance, if an icon triggers a search action, you could include an ARIA label such as aria-label= "Search" on the button element, or you can nest a visually hidden <span> that says “Search.”

    Why It Matters

    Without ARIA labels or hidden text, a screen reader might read the icon as a “button” or, worse, give no information.

    How To Do It

    <button aria-label="Search">
      <svg aria-hidden="true"> ... </svg>
      <span class="visually-hidden">Search</span>
    </button>

    Ensure keyboard and screen reader users have the proper context to interact with your icon.

    6. Choose the Right Icon Format

    Icons can be added to a webpage in several ways, but SVG and PNG are two of the most popular image formats. Alternatively, some designers opt for icon fonts. Each has its pros and cons when considering icon accessibility.

    SVG & PNG Are Your Friends

    SVG (Scalable Vector Graphics)

    • Pros: These files are resolution-independent, meaning they scale well to any size without losing quality. They can also be easily styled with CSS and annotated with titles or labels for accessibility.
    • Cons: If you’re unfamiliar with SVG syntax, the setup process can be more involved.

    PNG (Portable Network Graphics)

    • Pros: Excellent for icons that don’t need to scale up drastically. PNGs offer high-quality images with transparency.
    • Cons: They’re not always the best for large or small displays, as they can become pixelated or blurry when scaled.

    Beware of Icon Fonts

    Icon fonts replace letters with symbols, so the text “A” might visually display as a house icon. While this can be convenient, it can create issues for screen readers who might read the text as a letter rather than a graphic. If you use icon fonts:

    • ARIA: Add aria-hidden= "true" to ensure the screen reader ignores the font.
    • Hidden text: Include a visually hidden <span> with the function of the icon, such as “Home” or “Search.”

    By choosing the right format, you help ensure users can see or interact with the icon regardless of their device or abilities.

    Team Up with 216digital for Better Accessibility

    Mastering icon accessibility is more than just following guidelines; it’s about providing an inclusive experience for everyone who visits your website. Clear, intuitive icons can significantly improve your site’s usability, particularly for users who rely on assistive technologies.

    If you’re unsure where to begin or want to ensure accessibility experts handle every detail, consider partnering with 216digital. Our team has extensive experience creating accessible, user-friendly websites that work seamlessly across different devices and for people of all abilities. We’ll help you fine-tune every aspect of your icons, from contrast ratios and alt text to keyboard navigation and consistent design.

    Ready to level up your website’s accessibility? Contact us for a quick briefing and see how we can help strengthen your site’s icon design. Together, we can create a web experience that welcomes everyone, reflecting your brand values and maximizing your reach in a diverse online world.

    Greg McNeil

    February 14, 2025
    How-to Guides
    Accessibility, How-to, Icon Accessibility, web developers, web development, Website Accessibility
  • Creating Accessible Data for Charts and Graphs

    Data drives decisions. A clear and easy-to-understand chart can speak volumes whether you’re showing sales figures, survey results, or scientific findings. However, not everyone interprets visual elements the same way. People with low vision, color blindness, or who rely on screen readers may face serious barriers if your charts aren’t designed with accessibility in mind.

    Beyond inclusivity, legal standards exist like the Americans with Disabilities Act (ADA) and the Web Content Accessibility Guidelines (WCAG). In this post, we’ll explore why accessible data visualizations matter, review common accessibility mistakes, and share practical techniques you can use to ensure that all visitors can understand your charts and graphs.

    Designing for Visual Accessibility

    Color Contrast in Charts and Visualizations

    Color contrast plays a crucial role in readability, especially for users with visual impairments. According to WCAG SC 1.4.3: Contrast (Minimum, the standard text should have a contrast ratio of at least 4.5:1, while large text (18pt or 14pt bold) requires a minimum of 3:1. These guidelines also apply to key chart elements, including labels, axes, and text within visualizations, ensuring that information remains clear and accessible to all users.

    To check your color choices, use tools like WebAIM’s Contrast Checker or Chrome DevTools’ built-in accessibility features. If your text lacks sufficient contrast, consider adjusting to darker text on lighter backgrounds or using bolder, larger fonts. Prioritizing accessible data in your visualizations not only enhances clarity but also improves the user experience for a wider audience.

    Avoiding Color-Only Differentiation

    When a chart relies on color alone to show differences in categories—like red for “loss” and green for “gain”—users with color blindness might not be able to tell them apart. WCAG SC 1.4.1 (Use of Color) emphasizes that color can’t be the only method used to communicate information.

    To fix this, you can:

    • Use patterns or textures in bar charts or pie slices.
    • Add direct labels or annotations next to the data points.
    • Include icons or distinct shapes to differentiate data series.

    Scalability and Zoom Support

    Many people need to zoom in to read small text or fine details. According to WCAG SC 1.4.4(Resize Text), users should be able to zoom up to 200% without losing content or functionality. Test how your charts scale on both desktop and mobile screens. This may involve using scalable vector graphics (SVG) or ensuring your chart library supports responsive resizing.

    Providing Text Alternatives and Descriptive Labeling

    Alt Text for Simple Charts

    For simpler charts—like a basic bar chart comparing two or three items—brief alt text can be enough. This alt text should include the following:

    • The overall trend or purpose of the chart (e.g., “A bar chart comparing monthly sales in January and February…”).
    • Key numbers or comparisons (if they’re crucial to understanding the data).

    Avoid including every detail if it’s not necessary. Alt text is meant to be concise yet informative.

    Breaking Down Complex Data with Text Summaries

    If your chart is more detailed—perhaps showing multiple data series or a longer timeline—alt text alone won’t cover it. In that case, it’s better to provide a text summary that covers the main insights:

    • Describe what the chart is measuring (“Average temperature trends across five cities…”).
    • Highlight any interesting data points or outliers (“City A had a significantly higher temperature in July…”).
    • Provide overall conclusions that help readers understand key takeaways.

    Using ARIA for More Detailed Descriptions

    If a simple alt text or summary doesn’t do your data justice, you can use aria-describedby to link your chart to a more extended description elsewhere on the page. This approach ensures screen reader users have access to more in-depth data without crowding the main alt text.

    When writing these extended descriptions:

    • Keep your text organized with headings or bullet points.
    • Clearly label each section so users know what information they’re accessing.
    • Make sure screen readers can announce the description properly by placing it in a logical spot on the page or using hidden text if necessary.

    Structuring Data Tables for Screen Readers

    Another highly accessible way to present data is through tables. If you can’t convey the full meaning of a chart in alt text, consider adding a well-structured HTML table. Be sure to:

    • Use <th> elements for headers.
    • Include a <caption> that describes the table’s purpose.
    • Provide a summary if the table is complex.

    For example:

    <table>
      <caption>Monthly Sales for Q1</caption>
      <thead>
        <tr>
          <th scope="col">Month</th>
          <th scope="col">Sales ($)</th>
        </tr>
      </thead>
      <tbody>
        <tr>
          <th scope="row">January</th>
          <td>10,000</td>
        </tr>
        <tr>
          <th scope="row">February</th>
          <td>12,000</td>
        </tr>
        <tr>
          <th scope="row">March</th>
          <td>9,500</td>
        </tr>
      </tbody>
    </table>

    Well-coded tables help screen readers identify the rows, columns, and header relationships.

    Making Interactive Charts and Graphs Accessible

    Keyboard Navigation and Focus Management

    If your chart is interactive—allowing filters, tooltips, or zoom functions—it’s crucial that all features are accessible by keyboard alone. This means:

    • Users should be able to tab through each interactive element.
    • The focus order should make sense, moving in a logical sequence.
    • Dropdowns, sliders, or filters must also be operable without a mouse.

    By implementing these best practices, you can guarantee accessible data interactions for all users, including those who rely on keyboard navigation.

    Ensuring Tooltips and Popups are Accessible

    A big challenge is making sure that tooltips triggered by hovering can also be triggered by keyboard actions, like pressing the Enter or Space keys. Also, make sure each tooltip has an accessible name and description so screen readers can announce it properly. WAI-ARIA attributes like role= "tooltip" and aria-hidden= "false" (when the tooltip is visible) can help.

    Using Semantic HTML and ARIA Roles

    Use semantic HTML elements like <svg> for vector graphics where possible. If you’re using <canvas> or more complex libraries, add proper ARIA roles and states so screen readers know how to interpret them. Clear focus indicators are also important so users can see where they are when tabbing through interactive features.

    Choosing Static vs. Interactive Charts

    Interactive charts can be powerful, but they’re not always the best choice for every audience. Sometimes, a well-labeled static chart is more accessible data and easier to understand. If you have users who need data quickly and without extra steps, offering both a static image and an interactive version can meet multiple needs.

    Selecting and Adapting Chart Types for Accessibility

    Accessible Bar Charts

    Bar charts are among the easiest to make accessible, as long as you:

    • Clearly label each bar.
    • Use more than color to differentiate bars—consider patterns or direct labeling.
    • Provide a descriptive axis label so users know what each bar represents.

    Accessible Line Graphs

    Line graphs can be tricky for those with low vision. To improve accessibility:

    • Use different line styles (solid, dashed, dotted) to distinguish multiple data sets.
    • Add shape markers at each data point so color-blind users can still tell them apart.
    • Make sure your axes and legends are clear, with sufficient contrast.

    Accessible Pie Charts

    Pie charts can be confusing when there are too many slices. Limit your chart to a small number of slices and label each piece directly. Also, add patterns or textures if you use color coding. If your data is too complex, think about using a different format, like a table or bar chart.

    Handling Complex Data Visualizations

    If your data is large or contains many variables, consider breaking it down into smaller charts. This approach, called “small multiples,” allows users to compare data across several simpler charts rather than one overwhelming visualization. Include thorough text explanations and summaries to give context and help users understand the bigger picture.

    Advanced Accessibility Techniques for Charts and Data Displays

    Providing Multiple Data Views

    Not everyone can interpret data in the same way, so offering a toggle between a chart view and a table view can be extremely helpful. For example, you could have a button labeled “Show Data as Table” that, when clicked, reveals an accessible HTML table with the same information.

    Supporting Screen Readers with Data Annotations

    For charts that update in real-time—like stock price tickers—add announcements with ARIA live regions if something significant changes. This way, screen reader users will be notified when new data appears, but be careful not to overload them with constant updates.

    Making Dynamic and Real-Time Data Accessible

    Real-time data can be challenging because it often changes so frequently. Focus on essential changes and clearly label them. If you’re running live dashboards or analytics that refresh, allow users to control the refresh rate or pause the updates. This helps users keep track of what’s changed without confusion.

    Testing and Validating Chart Accessibility

    Manual Testing with Assistive Technologies

    Always test your charts using real assistive tools such as:

    • Screen readers like  NVDA, JAWS, or VoiceOver.
    • Keyboard-only navigation for all interactive elements.

    This hands-on testing helps you catch issues that automated checkers might miss, like poor focus order or unannounced chart labels.

    Automated Testing Tools

    Tools like WAVE Accessibility Checker and Lighthouse’s Accessibility Audit in Chrome can highlight potential problems. However, automated tools can only find about 30% of accessibility issues, so don’t rely on them alone.

    User Testing and Real-World Validation

    Finally, the best way to confirm that your data visualizations are truly accessible is to test them with actual users who rely on assistive technology. Gather feedback and be prepared to iterate on your design. Accessibility is an ongoing process that benefits greatly from real-world input.

    Creating Data-Driven Experiences for All Users

    Inclusive data visualizations aren’t just a courtesy—they’re the key to truly understanding and acting on the information that drives our businesses, classrooms, and communities. By deliberately designing charts and graphs that everyone can parse, you’re ensuring your message resonates with the widest possible audience. You’re also upholding the principles of equality, transparency, and innovation that propel the web forward.

    Start your journey toward full web accessibility today—reach out to 216digital using the form below! Our team of accessibility experts is ready to assess your site and provide tailored solutions to ensure that all visitors can easily access your content.Don’t let accessible data remain an afterthought—take the first step toward a more inclusive online presence now.

    Greg McNeil

    February 12, 2025
    How-to Guides
    Accessibility, Accessible Data, How-to, Web Accessibility, web developers, web development, Website Accessibility
  • Accessibility Barriers: The Problem with Placeholders

    Form design might seem simple at first. You add text fields, maybe a dropdown or two, and call it a day. But when it comes to guiding users, many designers rely on placeholders to show instructions or examples inside the input fields. On the surface, this seems like a neat way to save space and keep the layout clean. However, those same placeholders can create big usability and accessibility issues.

    If you’ve been counting on placeholders to label your form fields, it might be time to rethink your approach. In this article, we’ll explore why placeholders cause problems, especially for people with disabilities, and how you can design forms that are clearer and easier for everyone to use.

    Why Placeholders Cause Problems in Forms

    1. They Disappear When Users Start Typing

    Picture this: a user clicks on a field that says “Enter your phone number,” the moment they begin typing, that instruction vanishes. If they suddenly forget the exact format or details required, they have to either clear the field to see the placeholder again or guess what was there in the first place. This can be annoying in simple fields, but it becomes a real headache in longer or more complex forms. Each additional step or moment of confusion can lead to higher drop-off rates and reduced accuracy.

    2. Not All Browsers Support Them

    Although modern browsers generally display placeholders, some older or less common browsers may not. When these browsers skip placeholders altogether, the user has zero guidance or instruction for the field. If your form is already barebones—meaning you’ve omitted labels or separate hint text—people on unsupported browsers are left to figure it out on their own. This can be especially problematic when international or low-tech audiences may rely on older systems.

    3. Once Filled, Fields Lose Context

    After a user inputs data into a field, the purpose of that field may not be obvious. This is especially true for details like phone numbers, ZIP codes, or other specialized information. Without visible labels, users who step away from their screens or return later might forget the exact context for each field and whether it requires a specific format (e.g., whether to include country codes or parentheses for phone numbers).

    4. Reviewing Answers Becomes a Hassle

    Many people like to review their answers before hitting the Submit button. However, if placeholder text disappears once the user types something in, they can’t quickly verify whether their entry meets the field’s requirements. This can lead to overlooked mistakes—like mixing up month and day in date fields or forgetting to include a state abbreviation in an address.

    5. Fixing Errors Gets Confusing

    When a form returns an error message, it often refers to a specific label or hint. Without a visible label, a user might only see a generic error message like “Invalid entry” without knowing how to fix it. They’re left guessing whether they must add a certain number of characters, switch from text to numbers, or follow a specific pattern. This guesswork can be frustrating and lead to abandoned forms.

    6. Some Browsers Hide Placeholders When the Field Is Focused

    In certain older browsers, clicking or tabbing into an input field removes the placeholder immediately. Suppose a user didn’t fully absorb the instructions beforehand. In that case, they’ll have to navigate out of the field and back in, or potentially delete any typed text, to see the placeholder again. It’s a minor issue but yet another piece of friction.

    7. They Can Be Mistaken for an Actual Answer

    Placeholder text usually has a lighter contrast to differentiate it from actual user input, but the difference can be subtle. Some users might assume the placeholder is pre-filled data and skip the field altogether. Or they might try to erase the text, only to realize it’s a placeholder, not a typed entry.

    8. Low Contrast Makes Them Hard to Read

    One frequent design choice is to make placeholders light gray. This aesthetic might look sleek but can be challenging to read for people with visual impairments or even those using a device in bright sunlight. Low contrast is a direct accessibility barrier and may violate the  Web Content Accessibility Guidelines (WCAG) guidelines, which recommend sufficient contrast between text and background.

    9. Some Screen Readers Don’t Read Placeholder Text

    Screen reader support for placeholders is inconsistent. Some devices or assistive tools ignore placeholders entirely, leaving users no context. If you rely on placeholders to communicate critical instructions, this group of users may miss out on the information they need.

    10. Smaller Clickable Area Without Labels

    When you have a label element associated with a form field, clicking the label sets focus on that field. This feature is handy, especially for people with motor impairments who benefit from a larger clickable target. Without a proper label, users might have to click precisely on the field, which can be more complicated.

    11. Placeholder Text Gets Cut Off

    Long placeholder text often doesn’t fit in the space provided, so it gets truncated. If the most crucial part of the instruction is at the end—like a date format or suffix—it may not be visible. Mobile users, in particular, have limited screen space, making it even more likely that critical instructions get chopped.

    12. Some Browsers Don’t Translate Placeholders

    If you depend on browser-based translation (like Google Translate in Chrome), remember that these tools don’t always translate placeholder text. International users might see fields with instructions in a language they don’t understand, putting them at a disadvantage.

    13. Auto-Complete Can Mess Things Up

    Browsers often auto-fill fields such as name or email based on saved user information. When that happens, the placeholder text is never shown. If the user doesn’t recall the exact format needed—like whether the phone number should include a dash or parentheses—they might submit the wrong thing without even realizing it.

    14. High Contrast Mode Makes Placeholders Look Like User Input

    High Contrast Mode in Windows can shift placeholder text to the same color as regular text. In that situation, a placeholder might appear identical to actual input, confusing users who think the field is already filled in or assume it’s a default value.

    What You Should Do Instead

    Rather than relying on placeholders, consider these best practices:

    Use a Visible Label

    Make sure every form field has a label that stays on the screen. Labels tell users—sighted, low vision, or blind—what the field is for. They also help screen reader users navigate more easily.

    Put Hint Text Below the Label

    If you need to offer more guidance, place this text below or next to the label. This way, the hint stays visible all the time. It won’t disappear once someone starts typing.

    Provide Clear Formatting Instructions

    Instead of relying on placeholders, add clear examples outside the input field. For instance, you could show “MM/DD/YYYY” under the “Date of Birth” label. Users can see the format without losing the prompt.

    Test for Accessibility

    Test your forms with screen readers and try them in high-contrast mode. Check that the labels are clear, that hint text stands out, and that the form works well even if placeholders don’t show up at all. Tools like WAVE or Google Lighthouse can help identify accessibility barriers.

    Consider Better UX Patterns

    Inline validation, tooltips, or progressive disclosure can guide users in a more reliable way. These methods let users see error messages or instructions at just the right time, without losing any important label text.

    Clear Forms, Better Experiences

    Using placeholders might seem like a clean and modern design choice, but it often causes more trouble than it’s worth. From disappearing instructions to accessibility issues, placeholders can leave users frustrated and unsure. Instead of relying on placeholders, give each field a clear label and keep helpful guidance visible. By doing so, you’ll create a smoother, more inclusive experience for everyone who visits your site.

    Need help making sure your forms are user-friendly and accessible? 216digital specializes in improving digital experiences for all users. Reach out to us today to learn how we can help you design better, more inclusive forms—no placeholders needed.

    Greg McNeil

    February 6, 2025
    How-to Guides
    Accessibility, How-to, Web Accessibility Remediation, web developers, web development, Website Accessibility
  • Why No ARIA Is Better Than Bad ARIA

    It’s tempting to think of ARIA (Accessible Rich Internet Applications) as the one-stop solution for all your accessibility needs. After all, ARIA exists to help developers create web content that works better for people who use assistive technology, like screen readers. But here’s the catch: if you misuse ARIA—or in places where it isn’t needed—you can end up making your site less accessible, not more.

    This post will explain why semantic HTML should always be your go-to approach, when and why ARIA is beneficial, the most common ARIA mistakes, and best practices for getting it right. By the end, you’ll see how “less is more” often applies to ARIA and why sticking to native elements can save you—and your users—a lot of trouble.

    What Is ARIA (and Why Does It Matter)?

    ARIA stands for Web Accessibility Initiative – Accessible Rich Internet Applications. Created by the World Wide Web Consortium (W3C), ARIA provides a set of roles, states, and properties that help assistive technologies (like screen readers) understand the meaning and function of different elements on a webpage. It’s beneficial for complex or dynamic interfaces that native HTML elements don’t fully cover—such as custom sliders or tab interfaces.

    However, the real power of ARIA depends on how it’s used. Applying ARIA roles in the wrong places or mislabeling states can lead to confusion and errors. Users relying on screen readers might hear incorrect information about what’s on the page or even miss out on essential controls. If you’re not cautious, you could do more harm than good.

    Why Semantic HTML Should Be Your First Choice

    Before jumping into ARIA, remember that semantic HTML is the foundation of accessible web design. Native elements, like <header>, <nav>, <button>, and <footer>, come with many built-in features that screen readers and other assistive tools already understand.

    What is Semantic HTML?

    It refers to HTML elements that clearly describe their meaning. For instance, a <nav> element signals that it contains navigation links. A <button> says, “I’m something clickable!” to both users and screen readers.

    Why Does it Matter?

    When you use semantic elements, you’re using markup that browsers and screen readers know how to interpret. This often means you don’t need ARIA at all—because everything is already handled for you.

    Real-world Example

    If you need a button, just use <button> instead of a <div> with role= "button". Screen readers automatically identify a <button> as a button, while a <div> is just a generic container. Adding a role= "button" to that <div> can work, but it’s extra code and is often less reliable than using a <button> in the first place.

    By relying on these built-in elements, your code is simpler and more intuitive. You’re also less likely to cause confusion when you mix ARIA roles with native roles.

    When (and Why) ARIA Is Actually Needed

    So, if semantic HTML is so powerful, why do we have ARIA at all?

    Filling the Gaps

    HTML is great, but it’s not perfect. Some interactive elements—like complex sliders, tab panels, or sortable tables—aren’t natively supported (or are only partially supported) by standard HTML tags. ARIA helps fill in these gaps by providing additional metadata.

    Roles, States, and Properties

    ARIA is split into three main categories: roles (what is this thing?), states (what is its current condition?), and properties (how does it behave?). These allow screen readers to give users a clearer picture of what’s happening on the page.

    Example: Tabs and sliders

    If you’re building a tab interface from scratch, you might rely on a series of <div> elements. You’d need ARIA attributes like role= "tablist", role= "tab“, and role= "tabpanel", plus properties like aria-selected= "true" or aria-hidden= "true" to show which tab is active.

    Ultimately, ARIA becomes crucial when the default HTML elements don’t cover the level of interactivity or complexity you need. That might be a custom widget or a specialized interface that doesn’t map neatly to existing HTML tags.

    The Most Common ARIA Mistakes (and Why They’re a Problem)

    Misusing Roles

    Sometimes, developers add ARIA roles to elements out of habit, without stopping to see if the native element would have worked better. If you set role= "button" on a <div>, you must also manually manage keyboard interactions and focus states. If you don’t, assistive technology users may be unable to click or navigate to this “button” effectively.

    Example

    <!-- Not so good -->
    <div role="button" tabindex="0" onclick="doSomething()">
      Click me
    </div>
    
    <!-- Better -->
    <button onclick="doSomething()">Click me</button>

    Using a <button> means you get keyboard focus, click events, and screen reader recognition by default—no extra ARIA or scripting needed.

    Redundant or Conflicting Roles

    Many elements come with built-in roles. A <nav> element is understood as “navigation,” and a <ul> is understood as a list. If you add role= "navigation" to a <nav>, you’re restating something already known. In some cases, overriding a native role with a custom role can even interfere with how assistive technologies interpret the element.

    Example

    <!-- Not so good -->
    <nav role="navigation">
      <!-- Navigation links here -->
    </nav>
    
    <!-- Better -->
    <nav>
      <!-- Navigation links here -->
    </nav>

    Here, adding role= "navigation" is unnecessary and could create confusion in some tools.

    Incorrect State Management

    ARIA states, like aria-expanded or aria-checked, must accurately reflect the element’s real condition. If your dropdown menu is closed but you have aria-expanded= “true”, a screen reader user will hear that the menu is open—even though it isn’t. This mismatch can be very disorienting.

    Example

    <!-- Not so good: says it's expanded when it's actually closed -->
    <button aria-expanded="true" onclick="toggleMenu()">Menu</button>
    
    <!-- Better: toggle the value dynamically with JavaScript -->
    <button aria-expanded="false" onclick="toggleMenu()">Menu</button>

    Make sure your script updates aria-expanded to reflect the actual state of the menu (true when open, false when closed).

    ARIA Overload

    Adding too many ARIA attributes can clutter the information that screen readers must process. For instance, overusing aria-live regions can cause screen readers to constantly read out changes that might not be important. This can frustrate users and cause them to miss critical content.

    Example

    <!-- Not so good: multiple live regions announcing frequent updates -->
    <div aria-live="polite">Update 1</div>
    <div aria-live="polite">Update 2</div>
    <div aria-live="polite">Update 3</div>
    
    <!-- Better: only announce genuinely important changes -->
    <div aria-live="polite" id="importantUpdates"></div>
    

    If you really need to announce multiple updates, try grouping them or letting users opt-in.

    Misusing aria-hidden

    aria-hidden= "true" tells screen readers to ignore an element. If you add this attribute to interactive content—like a button, form field, or link—you’re effectively locking out users who rely on assistive tech.

    Important: Hiding something visually is not always the same as hiding it from screen readers. Don’t use aria-hidden if the content is still necessary for some users.

    Example

    <!-- Not so good: Interactive element is hidden from screen readers -->
    <button aria-hidden="true" onclick="doSomething()">Buy Now</button>
    
    <!-- Better: If you need to hide it visually for some reason, do so with CSS,
         but keep it accessible to screen readers. -->
    <button class="visually-hidden" onclick="doSomething()">Buy Now</button>

    (“Visually hidden” classes typically hide elements from sighted users but keep them available to assistive tech.)

    Why “No ARIA” is Often the Best Choice

    The golden rule is this: bad ARIA is worse than no ARIA at all. Why? Because at least with no ARIA, the user experience reverts to the default behaviors of native HTML, which assistive technologies are designed to understand. But if you add incorrect ARIA roles or states, you can mislead screen readers entirely.

    In many cases, the standard HTML element does everything you need. By default, a <button> is keyboard-accessible, announces itself as a button, and can have an accessible label. Adding role= "button" to a <div> only means more overhead for you and possibly less clarity for users.

    Best Practices for Using ARIA the Right Way

    Use Native HTML First

    Always check whether you can use a built-in HTML element. This approach is simpler to code, more reliable, and better for accessibility out of the gate.

    Example

    Instead of:

    <div role="button" tabindex="0">Submit</div>

    Use:

    <button>Submit</button>

    No extra attributes, no confusion—just a straightforward button.

    Be Precise with Roles and States

    If you must use ARIA, choose the exact role that matches the purpose of your element. Also, keep an eye on the current state—like aria-expanded, aria-checked, or aria-selected—and update it only when something changes.

    Example

    <button aria-expanded="false" aria-controls="menu" onclick="toggleMenu()">Menu</button>
    <ul id= "menu" hidden>
      <li>Home</li>
      <li>Services</li>
      <li>Contact</li>
    </ul>

    In this example, setting aria-expanded= "false" on the button shows it’s not expanded. When the user clicks, you can switch that to true in your JavaScript.

    Don’t Add ARIA Where It’s Not Needed

    If an element already serves a clear function, adding a role that duplicates it is just noise for screen readers.

    Example

    <!-- Not so good -->
    <ul role="list">
      <li>Item 1</li>
      <li>Item 2</li>
    </ul>
    
    <!-- Better -->
    <ul>
      <li>Item 1</li>
      <li>Item 2</li>
    </ul>

    A <ul> is already recognized as a list by assistive technology.

    Test with Real Assistive Tech

    Tools like automated accessibility checkers are helpful, but they can’t catch everything. The best way to confirm your site’s accessibility is to test it with screen readers (like NVDA, JAWS, or VoiceOver) and try navigating entirely with a keyboard. If you can, get feedback from people who actually use these tools every day—they can point out mistakes or obstacles you might miss otherwise.

    Conclusion

    Using ARIA incorrectly can do more harm than good. In fact, it can make websites less accessible and confusing for users who rely on screen readers. The first step to building an accessible website is to stick with semantic HTML wherever possible. If you need ARIA—especially for complex custom widgets—be sure to use it carefully, accurately reflecting each element’s true roles and states. Then, test your work with real users and assistive technologies to make sure you’re making things better, not worse.

    Following these guidelines helps create a smoother experience for every visitor, including those using assistive technology. Remember: if you can solve your problem with native HTML, do that first. If not, ARIA can be a fantastic tool—just be sure you’re using it correctly.

    Need Help with Web Accessibility?

    Making a website accessible can be tricky, especially when it comes to knowing how and when to use ARIA. 216digital specializes in web accessibility, from ARIA best practices to full WCAG compliance. If you’re ready to take the next step toward a more inclusive web experience, reach out to us today! Let’s work together to ensure your site remains welcoming—and functional—for every user.

    Greg McNeil

    February 4, 2025
    How-to Guides
    Accessibility, ARIA, How-to, WCAG, Web Accessibility, web developers, web development
Previous Page
1 2 3 4 … 6
Next Page
216digital Scanning Tool

Audit Your Website for Free

Find Out if Your Website is WCAG & ADA Compliant













    216digital Logo

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

    216 Digital, Inc. BBB Business Review

    Get in Touch

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

    Support

    Support Desk
    Acceptable Use Policy
    Accessibility Policy
    Privacy Policy

    Web Accessibility

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

    Development & Marketing

    eCommerce Development
    PPC Marketing
    Professional SEO

    About

    About Us
    Contact

    Copyright 2024 216digital. All Rights Reserved.