# Accessibility basics — fixing axe violations

> axe-core finds the most common WCAG failures automatically. Critical and serious ones block real people; fix those first.

Accessibility · HTML version: https://getreport.app/learn/accessibility-basics

## Critical accessibility issues

Passing looks like: No critical accessibility violations.

**Why it matters.** Critical issues stop some visitors from using the page at all, for example buttons a screen reader cannot name or forms that cannot be filled in.

**How to fix it.**

1. Open the technical detail to see each rule and the elements affected.
2. Fix the highest-count rule first; the same template usually causes most instances.

## Serious accessibility issues

Passing looks like: No serious accessibility violations.

**Why it matters.** Serious issues make parts of the page very hard to use with a screen reader, keyboard or zoomed-in display, so some visitors give up before they buy or get in touch.

**How to fix it.**

1. Open the technical detail to see each rule and the elements affected.
2. Fix the rule with the most elements first; it is usually one template or component.

## Moderate accessibility issues

Passing looks like: No moderate accessibility violations.

**Why it matters.** Moderate issues slow visitors down rather than stopping them, for example headings out of order or regions without a name. Fixing them makes the page easier for everyone to scan.

**How to fix it.**

1. Open the technical detail to see each rule and the elements affected.
2. Fix them in the shared layout or theme so every page benefits at once.

## Minor accessibility issues

Passing looks like: No minor accessibility violations.

**Why it matters.** Minor issues are small inconsistencies that rarely block anyone but add friction for people who rely on assistive technology.

**How to fix it.**

1. Open the technical detail to see each rule and the elements affected.
2. Fix them when you next touch the affected template.

Check your own page: https://getreport.app/