Skip to content

Accessibility

Accessibility ensures your website can be used by everyone, including people who rely on screen readers, keyboard navigation, or other assistive technologies. Fixing accessibility issues improves usability for all visitors and helps you meet WCAG 2.1 compliance requirements.

Critical

Color Contrast

Color contrast is the difference in luminance between foreground text and its background. WCAG 2.1 requires a minimum contrast ratio of 4.5:1 for normal text and 3:1 for large text (18px bold or 24px regular). Insufficient contrast makes content difficult or impossible to read for users with low vision, color blindness, or those viewing screens in bright sunlight.

Read more →
Critical

Image Alt Text

Alt text (the HTML alt attribute) is a short text description of an image that screen readers announce to visually impaired users. It also displays when an image fails to load and is used by search engines to understand image content. Every non-decorative image on a page must have meaningful alt text that conveys the image's purpose or information.

Read more →
High

Heading Hierarchy

Heading hierarchy refers to the logical nesting of HTML heading elements (H1 through H6) on a page. A well-structured hierarchy starts with a single H1, followed by H2s for major sections, H3s for subsections, and so on without skipping levels. Screen readers use headings as a navigation shortcut, allowing users to jump between sections.

Read more →
Critical

Keyboard Navigation

Keyboard navigation means that every interactive element on a page — links, buttons, form fields, menus, and custom widgets — can be reached and operated using only the keyboard (typically via the Tab, Enter, Space, and arrow keys). This is a fundamental accessibility requirement because many users cannot use a mouse.

Read more →
High

ARIA Violations

ARIA (Accessible Rich Internet Applications) attributes provide extra semantic information to assistive technologies when native HTML elements are insufficient. ARIA violations occur when these attributes are used incorrectly — for example, applying an invalid role, using aria-labelledby to reference a non-existent ID, or adding redundant ARIA roles to elements that already have implicit semantics.

Read more →
High

Focus Management

Focus management controls which element on the page currently receives keyboard input, indicated by a visible focus ring or outline. Proper focus management means interactive elements show a clear visual indicator when focused, focus moves logically through the page, and focus is programmatically moved to the right place when content changes (e.g., opening a modal should move focus into it).

Read more →
Medium

Link Text

Accessible link text clearly describes the destination or purpose of a link without relying on surrounding context. Screen reader users often navigate by pulling up a list of all links on a page, so each link must make sense in isolation. Generic phrases like "click here", "read more", or "learn more" provide no information about where the link leads.

Read more →
Critical

Form Labels

Form labels are HTML <label> elements that programmatically associate a text description with a form input (text field, checkbox, select, etc.) using the for attribute matched to the input's id. Without a label, screen readers announce a form field as just "edit text" or "checkbox" with no indication of what information the user should enter.

Read more →
Medium

Alt Text vs. Title Attribute

The alt attribute and the title attribute serve different purposes on HTML images. The alt attribute provides a text alternative that screen readers announce to visually impaired users and that displays when an image fails to load. The title attribute generates a tooltip on mouse hover and provides supplementary information. Alt is required by WCAG for non-decorative images; title is optional and not reliably accessible.

Read more →
Medium

Accessibility Benchmarking

Accessibility benchmarking is the practice of measuring and comparing WCAG compliance metrics across multiple websites to establish baselines, track progress, and identify competitive gaps. Rather than auditing a single site in isolation, benchmarking uses normalized metrics like errors per page and health scores to make fair comparisons between sites of different sizes. A site with 50 accessibility errors across 500 pages (0.1 errors/page) is performing better than one with 20 errors across 10 pages (2.0 errors/page).

Read more →

Scan your site for accessibility issues

No credit card required. Start scanning in under two minutes.