# EAC method

> EAC combines automated checks, expert manual testing and real process verification because one tool cannot show the full accessibility problem.

## Principle

Automated tools are useful for clear structural problems, but they do not fully judge keyboard interaction, focus behavior, dynamic components, form logic, user journeys or assistive-technology experience. EAC therefore treats accessibility testing as layered verification.

## Four testing perspectives

1. Automated control: checks code, semantics, names, structure and contrast signals where these can be reliably detected.
2. Expert review: evaluates keyboard navigation, focus, forms, dynamic behavior and context-dependent WCAG interpretation.
3. EAC Sentinel: repeats agreed user scenarios at defined intervals or around releases to detect regressions in key processes.
4. EAC Replay: documents how screen readers, keyboard navigation or other assistive-technology setups move through a process on a specific device.

## Evidence model

EAC findings are intended to be actionable. A confirmed issue should include user impact, location, recommendation and retest criterion. The goal is to move from a detected signal to a clear product task.

## Retesting

Retesting checks whether a specific fix works. Ongoing protection is broader: it watches the effect of continued product changes, identifies new barriers and keeps a backlog of accessibility work current.

## Regulatory context

EAC content refers to WCAG, EAA, Polish Accessibility Act obligations, public-sector accessibility duties and accessibility statements. Public website content is informational and should not be treated as a legal opinion or certification unless a separate engagement says so.

## Source pages

- [Method](https://eacenter.eu/metoda/)
- [Accessibility audits](https://eacenter.eu/audyty/)
- [Ongoing protection](https://eacenter.eu/stala-ochrona/)
- [European Accessibility Act](https://eacenter.eu/european-accessibility-act/)