Accessibility Analyzer Roadmap

From multi-tool accessibility evidence to component intelligence, root causes, and meaningful repairs.

Roadmap

The Systemic Accessibility Analyzer is evolving from a multi-tool reporting platform into an accessibility intelligence engine.

Rather than simply aggregating reports, the project is focused on turning accessibility evidence into actionable insight.

Don't count findings. Find consensus.

Current focus: Phase 1 has successfully established the robust multi-tool evidence layer, PostgreSQL job data orchestration, engine-family badges, the Fix Once, Benefit Many prioritization engine, user-defined WCAG target levels (A/AA/AAA), and the new Color Vision Deficiency (CVD) simulation tool. Phase 2 will expand deeply into automated component intelligence, deeper confidence weighting, and root-cause mapping.

Current

Phase 1 — Evidence Engine

Collects, normalises, compares, and visualises accessibility evidence from multiple engines with interactive drilldowns and companion visual tools.

Next

Phase 2 — Accessibility Intelligence

Moves from individual findings towards advanced component grouping, confidence scoring, repeated patterns, and root-cause identification.

Future

Phase 3 — Guidance

Explores suggested code repairs, long-term regression trends, design-system insights, and prioritised remediation tracking.


Phase 1 — Accessibility Evidence Engine

Phase 1 focuses on gathering accessibility evidence from multiple independent sources and presenting it in a unified, meaningful way.

Instead of manually comparing reports from numerous accessibility tools, the analyzer normalises findings, removes duplication where possible, and highlights where tools independently agree.

Phase 1 asks: What did the tools find, and where do they agree?

Current capabilities

Supported evidence sources

Tool / viewPurpose
axe-coreAutomated WCAG testing and widely used accessibility rule coverage.
axe-scanAxe-derived reporting through an additional scan pathway.
IBM Accessibility CheckerConfirmed, potential, and advisory accessibility findings.
HTML CodeSniffer / HTMLCSWCAG technique-style rule evidence and review-oriented findings.
LighthouseBrowser-based accessibility audit metadata and failures.
OobeeCrawl-style accessibility evidence and axe-family results.
UUVFlow-based and heuristic accessibility evidence.
AlfaACT-style outcomes including failed and needs-review results.
Nu HTML CheckerMarkup, validation, and standards-level evidence.
Pa11y Axe / Pa11y HTMLCSAdditional axe and HTMLCS evidence through Pa11y runners.
Visual ExplorerClean page previews and keyboard tab-order maps from the same capture flow.
Virtual Screen ReaderStructured reading-order and semantic output.
Contrast CheckerVisual contrast evidence and colour-pair analysis.
CVD SimulatorColor Vision Deficiency (colorblindness) simulation to evaluate visual accessibility barriers and color reliance.

Benchmark suite

The analyzer is continually tested against a growing benchmark suite representing different kinds of real-world accessibility evidence.

Benchmark typeWhy it matters
Government / reference-quality sitesUseful baseline where stronger accessibility implementation is expected.
Retail / ecommerceTests product pages, navigation, imagery, forms, and transactional patterns.
Modern SPA / Next.jsExercises component-heavy, JavaScript-rendered, creative and animation-rich websites.
Legacy / malformed HTMLTests old markup patterns, validation failures, frames, and structural oddities.
Deliberately poor UXUseful for hostile interaction design, keyboard problems, confusing forms, and regression testing.
Authenticated flowsValidates login, storage state, protected-page analysis, and real application journeys.

Phase 2 — Accessibility Intelligence

Phase 2 shifts the focus away from individual findings and towards understanding accessibility at a higher level.

Instead of answering:

How many issues were found?

the analyzer will begin answering:

What needs fixing?

Component analysis

Findings will be associated with likely interface components rather than grouped only by page or WCAG rule.

The goal is to identify repeated design-system issues rather than isolated page defects.

Root cause analysis

Many accessibility reports contain hundreds of repeated findings. Phase 2 aims to identify the underlying repair.

Instead ofThe analyzer identifies
63 button findingsA shared Button component pattern.
41 contrast failuresA shared colour token or visual treatment.
82 missing label findingsA repeated Form component issue.
Many image-alt issuesA repeated Image or Gallery component problem.

Confidence scoring

Not every accessibility finding carries the same weight. Future scoring can consider:

Accessibility heatmaps and visual layers

Future visualisations may include:

These visual layers build naturally on the current Visual Explorer, Virtual Screen Reader, and Contrast Checker outputs.


Phase 3 — Accessibility Guidance

Phase 3 is intentionally more exploratory. The broad idea is to help teams move from understanding evidence to planning repairs.

Potential ideas include:

Scope reminder: The analyzer is not intended to replace manual accessibility expertise. It organises automated and companion-tool evidence so that human review and remediation decisions can be better targeted.

Long-term vision

Accessibility tools already identify problems. The Systemic Accessibility Analyzer is focused on understanding those problems.

Ultimately the goal is to help answer questions such as:

From findings to evidence. From evidence to consensus. From consensus to meaningful repairs.