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.<\/p>\n\n
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.<\/p>\n\n
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.<\/p>\n\n
wp relyo scan --all<\/code>, wp relyo report<\/code><\/li>\n<\/ul>\n\nFix<\/h4>\n\n\n- 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<\/li>\n
- 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<\/li>\n
- 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<\/li>\n<\/ul>\n\n
Accessibility statement<\/h4>\n\n\n- 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), United Kingdom (WCAG 2.2 AA, Equality Act 2010) or United States (WCAG 2.1 AA, ADA)<\/li>\n
- Filled from Relyo's findings when you ask: non-compliances found by the automated checks, pages checked, technologies and tools<\/li>\n
- 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<\/li>\n
- The
[relyo_statement_link]<\/code> shortcode shows the link every page should carry, e.g. \"Accessibilit\u00e9 : non conforme\"<\/li>\n<\/ul>\n\nRelyo Pro<\/h4>\n\n
Relyo Pro<\/a> 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.<\/p>\n\nRelyo 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).<\/p>\n\n
Third-party code<\/h3>\n\n
Relyo bundles axe-core<\/a> 4.13.0 (Mozilla Public License 2.0, compatible with the GPL), in assets\/vendor\/axe-core. It runs in your browser, on your own pages; nothing is sent anywhere. Unminified source: https:\/\/unpkg.com\/axe-core@4.13.0\/axe.js<\/p>\n\n\n\nIs Relyo an overlay?<\/h3><\/dt>\nNo. Overlays add a widget on top of the page and leave the page as it is. Relyo finds the problems in your pages and corrects them, in the page's code or in your content.<\/p><\/dd>\n
Will Relyo make my site compliant?<\/h3><\/dt>\nNo tool can on its own. Relyo checks 61 of the RGAA's 106 criteria automatically (69 with Relyo Pro); 37 can only be checked by a person (is this alternative relevant, does this video have a transcript). The score shows how much of what Relyo can check is correct, not an RGAA compliance rate.<\/p><\/dd>\n
Does Relyo send my pages anywhere?<\/h3><\/dt>\nNo. Relyo loads your pages from your own site to check them, and axe-core runs in your browser, on your own pages.<\/p>\n\n
Images are the one exception, and only if you use AI alternatives: Relyo sends an image to the AI service you chose only when you ask for its alternative (Relyo Pro: also the media library's images without alternative, from the Images screen), with your own key: OpenAI<\/a> (terms<\/a>), Google Gemini<\/a> (terms<\/a>) or Mistral AI<\/a> (terms<\/a>).<\/p><\/dd>\nDoes it work with page builders?<\/h3><\/dt>\nRelyo checks the page as displayed, so it sees what Elementor and other builders produce. For an image in an Elementor layout, Relyo updates its alternative in the media library, which Elementor uses unless the widget sets its own.<\/p><\/dd>\n
Can I undo a correction?<\/h3><\/dt>\nDisplay corrections: turn them off in Relyo \u2192 Corrections. Content corrections: WordPress keeps a revision of the content before each one, which you can restore from the editor.<\/p><\/dd>\n\n<\/dl>\n\n\n
0.2.3<\/h4>\n\n\n- Relyo Pro: new prices, for 1, 3 or 10 sites, and a 14-day free trial with no card<\/li>\n
- Relyo Pro: Relyo AI gives 2,000 images a month for each site of your plan<\/li>\n<\/ul>\n\n
0.2.2<\/h4>\n\n\n- 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\"<\/li>\n
- English accessibility statements list the WCAG success criteria of each non-compliance<\/li>\n
- New name and screenshots on WordPress.org<\/li>\n<\/ul>\n\n
0.2.1<\/h4>\n\n\n- Relyo Pro: Freemius SDK 2.13.5<\/li>\n<\/ul>\n\n
0.2.0<\/h4>\n\n\n- Accessibility statement: Relyo \u2192 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<\/li>\n
- 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<\/li>\n
- Show on page: opens the page with the faulty element outlined and what is wrong with it<\/li>\n
- Ignore a problem on every page, and count it again from the problems list<\/li>\n
- 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<\/li>\n
- Dashboard: what to fix first, the statement's status, best practices, the score over time, and the 37 criteria a person must check<\/li>\n<\/ul>\n\n
0.1.2<\/h4>\n\n\n- 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<\/li>\n
- Relyo Pro: OpenAI, Google Gemini and Mistral AI keys keep working for sites that use them<\/li>\n<\/ul>\n\n
0.1.1<\/h4>\n\n\n- 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<\/li>\n
- Skip link and focus styles added as an inline style of the page, not printed in it<\/li>\n
- Translations from translate.wordpress.org<\/li>\n<\/ul>\n\n
0.1.0<\/h4>\n\n\n- 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<\/li>\n
- 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<\/li>\n
- French translation<\/li>\n
- Content corrections: image alternatives and empty paragraphs, with a revision saved first and a log of corrections per page<\/li>\n
- 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)<\/li>\n
- Admin: dashboard, problems list, page detail, score column, editor panel<\/li>\n
- Background scans (Action Scheduler or WP-Cron), REST routes for the browser checks, WP-CLI commands<\/li>\n
- 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)<\/li>\n
- Pro: 8 more criteria \u2014 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)<\/li>\n
- 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)<\/li>\n
- 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<\/li>\n<\/ul>","raw_excerpt":"Check and fix accessibility against RGAA 4.1 and WCAG 2.1, criterion by criterion, and publish your accessibility statement. No overlay.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/bs.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/380797","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bs.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/bs.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/bs.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=380797"}],"author":[{"embeddable":true,"href":"https:\/\/bs.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/delsuza"}],"wp:attachment":[{"href":"https:\/\/bs.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=380797"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/bs.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=380797"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/bs.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=380797"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/bs.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=380797"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/bs.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=380797"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/bs.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=380797"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}