Building Accessible UI Components

Accessibility is not optional—it's essential for creating inclusive web applications.

Why Accessibility Matters

• 15%+ of the global population has some form of disability
• Legal requirements: WCAG 2.1 AA compliance
• Better UX for everyone: Accessibility features help all users

Key Principles

1. Semantic HTML

Always use the correct HTML elements:

<!-- Good -->
<button>Click me</button>

<!-- Bad -->
<div onclick="handleClick()">Click me</div>

2. ARIA Attributes

When HTML isn't enough, use ARIA:

<div
  role="dialog"
  aria-modal="true"
  aria-labelledby="dialog-title"
  aria-describedby="dialog-description"
<blockquote><p></p></blockquote>
  <h2 id="dialog-title">Confirm Action</h2>
  <p id="dialog-description">Are you sure?</p>
</div>

3. Keyboard Navigation

Ensure all interactive elements are keyboard accessible:

function CustomButton() {
  return (
    <div
      tabindex="0"
      role="button"
      onKeyDown={(e) => {
        if (e.key === "Enter" || e.key === " ") {
          handleClick();
        }
      }}
      onClick={handleClick}
    >
      Custom Button
    </div>
  );
}

4. Focus Management

Manage focus for modals and dynamic content:

import { useEffect, useRef } from "react";

function Modal({ isOpen, onClose }) {
  const modalRef = useRef(null);
  
  useEffect(() => {
    if (isOpen && modalRef.current) {
      modalRef.current.focus();
    }
  }, [isOpen]);
  
  return (
    <div ref={modalRef} tabindex="-1">
      {/* Modal content */}
    </div>
  );
}

Testing Accessibility

Use these tools:

• axe DevTools: Browser extension
• Lighthouse: Built into Chrome DevTools
• NVDA/JAWS: Screen readers for testing

Conclusion

Building accessible components from the start is easier than retrofitting accessibility later. Make it a habit!