Skip to main content
Version: Next

Accessibility

In short. Flexy is audited against RGAA 4.1, the French reference built on WCAG 2.1 level AA. On 30 October 2026, 24 of the 70 criteria that apply to the theme are decided: 23 conforming, 1 not conforming (the border colour of the form fields). The other 46 still need a manual check. The core runs an automated measure on every pull request so that what has been fixed stays fixed. A theme derived from Flexy keeps these results only if it follows the rules below and runs the same measure.

Accessibility statement of the theme​

This statement covers the Flexy theme as shipped. A shop publishes its own statement: its content, its modules and its changes to the theme are its own.

Conformance status​

Flexy is not yet assessed as a whole against RGAA 4.1. The audit below is partial: it decides every criterion that an automated tool or a keyboard test can settle, and leaves to a manual audit the criteria that need a screen reader or a judgement on content.

Criteria
Conforming23
Not conforming1
Not applicable on the audited pages36
Not tested yet (manual check)46

The grid, criterion by criterion with the evidence for each status, is on the audit grid page.

Not conforming​

  • RGAA 3.3, colour of interface components. The border of the text fields, the selects and the search box uses --color-medium (#ffb698), at 1.69:1 against a white background where 3:1 is required. Changing it changes the look of every field of every theme derived from Flexy; the new colour is to agree with the design of the theme before it ships.

No derogation is claimed.

Fixed during this audit​

DefectCriterion
No link to skip to the main content, and nothing for it to target12.7
The logo link of the checkout header had no accessible name6.2
The copyright line of the checkout footer, the crossed-out price of the cart and the product details of the order confirmation were at 4.2:13.2
The variant selector of the product page took the focus without showing it, and stayed a tab stop on desktop where it does nothing10.7
The account page was 330px wide in a 320px viewport10.11
The home page, the filled cart and the order confirmation had no level 1 heading; sign-in, sign-up and contact started at level 29.1
The name field of the contact form did not declare its purpose for autofill11.13

How the audit was made​

Date30 October 2026
ReferenceRGAA 4.1, 106 criteria, WCAG 2.1 A and AA
ThemeFlexy main (1.4.x-dev), demo data
Toolsaxe-core 4.13 through Playwright 1.59, Chromium; keyboard and reflow tests of tests/Playwright/specs/accessibility.spec.ts
Viewports1440px, and 320px for reflow

Pages audited: home, a category (/chairs.html), a product (/barbara-1.html), search results, a content page (/a-propos.html), contact, sign-in, sign-up, the account, its addresses, orders and purchase lists, then the cart, delivery, payment and confirmation steps of the checkout.

The payment and confirmation steps are measured by the core's accessibility workflow on every pull request, which also places an order with the keyboard alone; they were not part of the manual pass of this audit.

Report a problem​

Open an issue on thelia-templates/flexy and name the page, the browser and, when there is one, the assistive technology. A problem met on a shop goes to that shop first: its statement gives its own contact and the means of redress.

Rules for a theme derived from Flexy​

What Flexy guarantees holds as long as a child theme does not undo it.

  1. Keep the skip link at the top of base.html.twig and id="main-content" tabindex="-1" on <main>. A layout that overrides the body of the base template has to carry both.
  2. Start every page on one h1, visible or sr-only, then title each section with a heading of the next level. A styled div is not a heading.
  3. Give every link and button a name a screen reader can read. A link or button that only shows an icon carries an aria-label; the icon itself stays aria-hidden.
  4. Never remove the focus outline without replacing it. outline: none is allowed only next to a :focus-visible rule that draws something at least 3:1 against its background.
  5. Keep text at 4.5:1 against its background (3:1 from 24px, or 18.66px bold), and borders and icons that identify a control at 3:1. Check a new colour on each background it is used on: --color-grey passes on white and fails on --color-lightest.
  6. Let content shrink. A grid that changes column count at a breakpoint declares its single column below it (grid-cols-1 md:grid-cols-2). Molecules:Button never grows wider than its container; a button of your own that sizes to its text gets max-w-full.
  7. Render form fields through the theme's form theme: it associates the label, marks the field aria-invalid and points aria-describedby at the error, and Molecules:FormErrors moves the focus to the error summary. Give each personal data field its autocomplete value.
  8. A control that only exists on mobile (a drawer trigger) is a <button> and is hidden with display: none where it does nothing, so that it leaves the tab order.

What the core checks on every pull request​

The accessibility workflow of thelia/thelia serves a demo shop and runs tests/Playwright/specs/accessibility.spec.ts against it, on every pull request.

  • axe runs with the WCAG 2.1 A and AA rules, the base of RGAA 4.1. The spec fails on a serious or critical violation. It runs on the sign-in and sign-up forms, on the pages of setup/audit/lighthouserc.default.yaml and on each step of the checkout, up to the confirmation.
  • axe waits until Turbo has finished its visit and the live components have rendered again. Otherwise it would read a half-transparent text as a contrast failure.
  • A page where no rule reached its content fails. A URL of the sample that no longer exists, or that redirects elsewhere, fails too.
  • The same spec checks the skip link, places an order with the keyboard alone, and checks that nothing sticks out of a 320px viewport.

The workflow starts PHP's built-in server with a router script, so that it hands rewritten URLs to Symfony. The page list of lighthouserc.default.yaml follows the routes Flexy serves.

Measure a derived theme​

The spec of the core runs against any served shop. From a checkout of thelia/thelia, with your theme active on the shop:

cd tests/Playwright
npm ci
npx playwright install chromium
BASE_URL=https://my-shop.ddev.site npx playwright test specs/accessibility.spec.ts

The helpers that read the database run ddev exec mysql by default. When the shop is not served by DDEV, set MYSQL_COMMAND to your own client, for example MYSQL_COMMAND="mysql -h127.0.0.1 -uroot -proot thelia".

The page list comes from setup/audit/lighthouserc.default.yaml; point it at your own URLs if your catalogue differs from the demo. Each page logs a line such as a11y /chairs.html: 25 rules checked (20 on the content), 39 not applicable, 0 rules violated, 0 blocking node(s). A page where no rule reached the content fails: the rules on <html> and <head> (language, title) run whatever is excluded, and an audit that measured nothing else is not a pass.

The measure settles only part of RGAA. The criteria marked NT in the grid still need a person, a keyboard and a screen reader.