About this plugin
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.
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.
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).
Third-party code
0, compatible with the GPL), in assets/vendor/axe-core. It runs in your browser, on your own pages; nothing is sent anywhere. js