Aware Components

Aware Components is an unstyled React component library focused on accessibility (a11y). It provides enhanced versions of common HTML elements like <a>, <button>, <div>, <h1>-<h6>, <img>, and more. These components are designed to automatically check for accessibility issues and display console warnings during development as needed.

The goal is to improve accessibility by ensuring proper usage of naming conventions, color contrast, ARIA labeling, and the correct nesting of elements.

Features

• Built-in Accessibility Checks: Each component provides real-time accessibility feedback, including warnings about heading levels, contrast issues, ARIA labels, and more.
• Common HTML Elements: Components are based on familiar HTML elements, making them easy to integrate into existing projects.
• Customizable Warnings: Developers receive accessibility warnings during development, enabling quick fixes and improvements.
• Standalone Accessibility Checks: In addition to components, several standalone accessibility checks are exported for broader use.
• Expandable: While currently focused on accessibility, the library is designed to expand in the future.

Stability Warning ⚠️

Note: This is an early version of and is still under active development. Features may change, and some components may not be fully stable. Use with caution.

Usage

For optimal accessibility monitoring, wrap your entire application with the A11yProvider:

import React from 'react';
import { A11yProvider } from './context/a11y';
import { H1, Button } from './components';

function App() {
  return (
    <A11yProvider>
      <div>
        <H1>Welcome to Aware Components!</H1>
        <Button onClick={() => alert('Hello')}>Click me</Button>
      </div>
    </A11yProvider>
  );
}

export default App;

The A11yProvider is required for checks that depend on the presence or number of components, such as ensuring proper heading levels or unique landmarks like <main>. Wrapping your app in A11yProvider allows these context-aware checks to function correctly.

Examples

Accessibility issues logged in the console

Example 1: Button with insufficient contrast and size issues

import { Button, Div } from 'aware-components';
import React from 'react';

function MyButton() {
  const [count, setCount] = React.useState(0);

  return (
    <Div>
      <Button
        style={{
          backgroundColor: '#000', // Insufficient contrast with text color
          color: '#333', // Low contrast for readability
          width: '1em', // Minimum touch target size not met
        }}
        onClick={() => setCount((count) => count + 1)}
        // Missing visible text or aria-label
      />
    </Div>
  );
}

Example 2: Incorrect use of heading elements

import { H1, H3 } from 'aware-components';

function Headings() {
  return (
    <>
      {/* Repeated <H1> elements, breaking the proper heading structure */}
      <H1>Guide to Cooking</H1>
      <H1>Basics of Cooking</H1>

      {/* <H3> used without an <H2>, skipping heading levels */}
      <H3>Choosing the Right Flour</H3>
      <H3>Essential Cooking Tools</H3>
    </>
  );
}

Example 3: Standalone Accessibility checks

In addition to the components, some standalone accessibility checks are exported.

import { isRatioOk, canHaveAriaHidden } from 'aware-components';

console.log(isRatioOk('white', 'black', 'AAA', 18)); // Checks if the contrast ratio between text and background colors meets WCAG level AA or AAA, based on text size.
console.log(canHaveAriaHidden(SomeComponent())); // Checks if the aria-hidden attribute can be applied to the component.

Mix and Match

Most components can be used alongside standard HTML elements. This flexibility allows for easy integration, but for the most comprehensive accessibility insights, consider using aware-components for all core elements in your component tree.

Example: The following mix of <Div> components and HTML <div> elements will still correctly detect and count nested divs.

import { Div } from 'aware-components';

export function Container(props: React.PropsWithChildren) {
  return (
    <Div>
      <Div>
        <div>
          <Div>
            <div>{props.children}</div>
          </Div>
        </div>
      </Div>
    </Div>
  );
}

Current Focus

• Ensuring accessibility by default for the most common HTML components.
• Catching common a11y issues like:
  • Heading level misuse (e.g., too many h1 elements)
  • Color contrast issues
  • Proper use of ARIA labels
  • Nesting and structure of semantic elements

Future Plans

• Expand to more specialized components
• Offer deeper customization for a11y checks

Contributing

Create a branch on your fork, add commits to your fork, and open a pull request from your fork to this repository.

Changelog

To check full changelog click here

License

MIT