Relyo – RGAA Accessibility Checker, Fixer & Statement

Relyo checks your pages and products against the RGAA 4.1 (the French standard, built on WCAG 2.1, used for the European Accessibility Act) and tells you what to fix, in plain words. Then it helps you fix it, and writes your accessibility statement. Every problem shows both its RGAA criterion and the WCAG 2.1 success criteria behind it, so it reads the same whether you work with the RGAA in France, with EN 301 549 in the EU, or with WCAG in the UK and the US. Relyo also checks the criteria WCAG 2.2 added, which the RGAA 4.1 does not have yet: click targets too small (2.5.8) and password fields that block pasting or password managers (3.3.8); with Pro, the keyboard focus hidden under a sticky header or cookie banner (2.4.11) and help that moves from page to page (3.2.6). They are shown as WCAG criteria, apart from the RGAA's. No overlay widget: Relyo corrects the pages themselves. Your pages never leave your site; an image is sent to an AI service only when you ask for its alternative. Check

• 61 RGAA criteria checked automatically: 40 rules run inside WordPress, and axe-core runs in your browser for contrast, ARIA and 4 more criteria
• Every page is checked as a visitor sees it: theme, page builder and WooCommerce templates included
• Every problem is tied to its RGAA criterion and its WCAG success criteria, with the element at fault and what to do
• Show on page: open the page with the faulty element outlined, and what is wrong with it
• Best practices beyond the RGAA, kept apart from its criteria: links opening a new window without saying so, justified text, text smaller than 12 pixels, and bold lines that should be headings (RGAA 9.1)
• A dashboard with your site's score and its most frequent problems
• A list of every problem, filtered by problem, severity and content type, with bulk actions; ignore a problem once, or on every page
• A score column in your post, page and product lists, and a panel in the editor
• Scans run in the background after each change, and on the whole site on request
• Polylang and WPML: each page is checked against its own language
• WP-CLI: wp relyo scan --all, wp relyo report

Fix

• 10 corrections you turn on in one click, applied as pages are displayed: skip link, visible keyboard focus, zoom, page language, frame titles, video and audio controls, announced shop messages, image captions, form autofill. Nothing changes in your content: turn one off and the page is back as it was
• Content corrections from the problems list: write an image's text alternative (saved in the media library and in the page), or remove empty paragraphs. WordPress keeps a revision first, and every correction is logged on the page
• Image alternatives suggested by AI, with your own key for OpenAI, Google Gemini or Mistral AI: the model looks at the image and suggests an alternative in the page's language, which you check before saving

Accessibility statement

• Relyo writes your accessibility statement as a page of your site, in the official form of the model you choose: France (RGAA 4.1, in French), European Union (WCAG 2.1 AA, EN 301 549, European Accessibility Act), Germany (BFSG, in German), Spain (Ley 11/2023, in Spanish), Italy (d.lgs. 82/2022, in Italian), United Kingdom (WCAG 2.2 AA, Equality Act 2010), United States (WCAG 2.1 AA, ADA), Ontario (WCAG 2.0 AA, AODA) or Australia (WCAG 2.2 AA, Disability Discrimination Act)
• Filled from Relyo's findings when you ask: non-compliances found by the automated checks, pages checked, technologies and tools
• Honest by design: without an audit, the statement says "not compliant", as the official models require. Relyo's checks are automated and cover part of the criteria only
• The [relyo_statement_link] shortcode shows the link every page should carry, e.g. "Accessibilité : non conforme"

Relyo Pro Relyo Pro includes Relyo AI: image alternatives with no key to create, 2,000 images a month for each site of your plan (1, 3 or 10 sites). Its Images screen writes the alternatives of the whole media library in the background: you then review the suggestions one by one or accept a selection, and each accepted alternative is saved in the media library and in the pages that show the image. Relyo Pro also checks 8 more RGAA criteria: it compares each page with the rest of the site (same title as other pages, a main menu that changes, a search form or site map link that moves, a field labelled differently), and checks the page as the browser draws it (form field outlines too faint, content too wide at 320 pixels, labels far from their fields).

0.4.0

• Accessibility statement: models for Germany (BFSG), Spain (Ley 11/2023) and Italy (d.lgs. 82/2022), written in their language with the information the European Accessibility Act asks of a service (description of the service, how it meets the requirements, the market surveillance authority), and for Ontario (AODA, WCAG 2.0 AA) and Australia (Disability Discrimination Act, WCAG 2.2 AA)
• The model is chosen from the site's language; "Fill from Relyo's findings" writes the German, Spanish and Italian lines in their language

0.3.0

• WCAG 2.2: click targets smaller than 24 by 24 pixels (2.5.8, by axe-core) and password fields that block pasting or password managers (3.3.8), shown as WCAG criteria next to the RGAA's
• Pro, WCAG 2.2: keyboard focus hidden under a sticky header, footer or cookie banner (2.4.11) and help (contact link, e-mail, phone, chat) not at the same place on every page (3.2.6)
• "What a person must check" lists the two WCAG 2.2 criteria no program can judge (dragging movements, redundant entry)
• WCAG links go to W3C's WCAG 2.2 explanations

0.2.3

• Relyo Pro: new prices, for 1, 3 or 10 sites, and a 14-day free trial with no card
• Relyo Pro: Relyo AI gives 2,000 images a month for each site of your plan

0.2.2

• Every problem shows the WCAG 2.1 success criteria behind its RGAA criterion (from the RGAA's official correspondences), linked to W3C's explanation: in the problems list, the dashboard, the corrections and "Show on page"
• English accessibility statements list the WCAG success criteria of each non-compliance
• New name and screenshots on WordPress.org

0.2.1

• Relyo Pro: Freemius SDK 2.13.5

0.2.0

• Accessibility statement: Relyo → Statement writes it as a page of your site, after the model you choose (France RGAA 4.1, European Union, United Kingdom, United States), filled from Relyo's findings on request, "not compliant" until an audit says otherwise; the [relyo_statement_link] shortcode shows the footer link
• Image alternatives suggested by AI are free with your own OpenAI, Google Gemini or Mistral AI key; Relyo Pro keeps Relyo AI (no key) and the whole media library at once
• Show on page: opens the page with the faulty element outlined and what is wrong with it
• Ignore a problem on every page, and count it again from the problems list
• New checks: bold lines used as headings (RGAA 9.1); best practices kept apart from the RGAA criteria: links opening a new window without saying so, justified text, text under 12 pixels
• Dashboard: what to fix first, the statement's status, best practices, the score over time, and the 37 criteria a person must check

0.1.2

• Relyo Pro: Relyo AI is included and becomes the default service for image alternatives: no API key needed, 2,000 images a month, packs of 10,000 images from the AI settings
• Relyo Pro: OpenAI, Google Gemini and Mistral AI keys keep working for sites that use them

0.1.1

• Corrections applied on display go through WordPress's template enhancement output buffer (WordPress 6.9 or later), and keep working on sites where Elementor turns that buffer off
• Skip link and focus styles added as an inline style of the page, not printed in it
• Translations from translate.wordpress.org

0.1.0

• Pro: image alternatives suggested by AI (OpenAI, Google Gemini or Mistral AI, your own key) on the fix screen, in the page's language, checked by you before saving
• Pro: Images screen, to write suggestions for every image of the media library without alternative in the background, then accept, edit, mark as decorative or reject each one
• French translation
• Content corrections: image alternatives and empty paragraphs, with a revision saved first and a log of corrections per page
• Corrections applied on display: skip link, focus, zoom, page language, frame titles, media controls, shop messages, captions, autofill (RGAA 1.9, 2.1, 4.10, 4.11, 7.5, 8.4, 10.4, 10.7, 11.13, 12.7)
• Admin: dashboard, problems list, page detail, score column, editor panel
• Background scans (Action Scheduler or WP-Cron), REST routes for the browser checks, WP-CLI commands
• Browser checks with axe-core for 6 more criteria: contrast, ARIA, links told apart by colour only, hidden focusable elements, forced text spacing, locked orientation (RGAA 3.2, 7.1, 10.6, 10.8, 10.12, 13.9)
• Pro: 8 more criteria — each page compared with the rest of the site (titles, main menu, search form, site map link, field labels; RGAA 8.6, 11.3, 12.2, 12.4, 12.5), and checks of the page as the browser draws it (form field outlines, 320 pixels wide, labels next to their fields; RGAA 3.3, 10.11, 11.4)
• 10 more rules for 11 criteria: CAPTCHA, media player controls, complex table summaries, clickable elements out of keyboard reach, lists that change the page by themselves, right-to-left text, text written by the CSS, text and background colours, content shown on hover only, option groups (RGAA 1.4, 1.5, 4.13, 5.1, 7.3, 7.4, 8.10, 10.2, 10.5, 10.14, 11.8)
• Analysis engine and 30 rules covering 44 RGAA 4.1 criteria: images and captions, frames, media, tables, links, WooCommerce notices, document and language, headings, page regions and skip link, lists, zoom, keyboard focus, forms (labels, groups, buttons, required fields, autocomplete), navigation, tab order, refresh, documents to download, moving content