Audit accessibility without leaving the page

Inkluo is an extension for Chrome and Firefox. It inspects an element, checks the page, measures contrast and produces the report, against the RGAA, the RAWeb or WCAG 2.2.

Coming soon on the Chrome Web Store and Firefox Add-ons.

The analysis runs entirely inside your browser. No data from the audited pages is transmitted, and the report itself is produced on your own machine.

Standards covered

The three standards switch throughout the interface. Verdicts that diverge from one standard to another follow whichever is active.

Standards and authoring guide that Inkluo rules against
Standard	Scope
RGAA	The French référentiel général d’amélioration de l’accessibilité. It applies to public digital services and to certain private organisations.
RAWeb	Luxembourg’s référentiel d’évaluation de l’accessibilité web, aligned with the European norm EN 301 549.
WCAG 2.2	Web Content Accessibility Guidelines, the international W3C standard. Inkluo rules at level AA.
ARIA APG	The W3C ARIA Authoring Practices Guide. Non-normative, it serves as the reference for components.

The six tabs

They follow the order of the work: inspect an element, check the page, walk its structure, measure contrast, then produce the report.

Inspector

One element at a time, explained end to end.

The accessible name and above all where it comes from: which attribute wins, which is ignored, and why.
The computed role, the ARIA attributes and the states, each with its own verdict.
The component’s ARIA lineage up to its root, clickable to walk back up the context.
Five options: target highlighting, inspection popover, DOM explorer, contextual DOM tree, live region monitoring.

27 diagnostic tools, 18 of them per component. Each lays its overlays on the page, one per instance, and reports its issue count before you even switch it on.

Links, images, buttons, lists, form fields, checkbox, radio and switch, groups, figures, tables, tab systems, iframes, menus, comboboxes, listboxes, sliders and spinbuttons, grids, trees, toolbars.

And beyond components: presentation through HTML, abusive spacing, unstructured text, disabling CSS, keyboard shortcuts, pointer and touch, text spacing, colour declarations, keyboard event viewer.

Page analysis

What is judged at document scale, not at a single node.

Foundations: doctype, declared language, document title, zoom allowed by the viewport tag.
Landmarks: missing main content, unnamed landmark, misplaced, duplicated, or with a broken association.
Navigation: skip link, search function, explicit roles expected by the RGAA.

Headings

The hierarchy as it will actually be traversed.

Every heading in document order, with its real level.
Skipped levels, empty headings, structures that do not start at h1.
One-click highlighting on the page, to locate each heading.

Landmarks

The regions of the page, and what names them.

Each ARIA landmark with its role, its label and where that label comes from.
Labels that fail to distinguish when several regions of the same type look alike.
Highlighting on the page, to see where each region starts and ends.

Contrast

Every text measured, grouped by colour pair.

One faulty pair often affects dozens of elements and is fixed by a single rule: the report counts elements but organises by pair.
Alpha, opacity groups, field placeholder text, shadow DOM and same-origin iframes are all taken into account.
Whatever cannot be measured is stated as such, with its reason, never assumed to pass.

Full audit

The exhaustive report, ready to hand over.

The whole page in one pass, grouped by section: page, headings, components, contrast.
Display filters across the four levels — errors, warnings, points to check, conformant — without re-running the audit.
Export to HTML, CSV or Markdown, each issue pinned by its code, its selector and its XPath.

Solo or as a team

Inkluo works just as well solo as within an established team. Every auditor keeps their own account and their own workstation; the team simply gathers them under one organisation. Signing in is done by email or with a Google account.

What team management allows
Seats	Four team sizes, from five to twenty places, changeable at any time.
Invitation	A colleague joins the team by email, with their own Inkluo account, and can be removed again.
Roles	Owner and member. The owner manages the places, invites, removes and renames the team.
Tracking	The count of occupied seats stays visible, and the team is renamed when the organisation changes.

Three commitments

Nothing leaves your browser: No data from the audited pages is transmitted. The report itself is produced on your own machine.
Three standards, one tool: RGAA, RAWeb and WCAG 2.2 switch throughout the interface, and verdicts that diverge follow whichever is active.
Chrome and Firefox, alike: The same extension and the same analyses on both engines.