Learning mode: issues are grouped by topic and explained in plain words. Start with the critical ones, then try each problem yourself: it is the best way to understand it.
What to fix
CRITICAL
1. Form control is missing a label
RGAA 11.1 — Chaque champ de formulaire a-t-il une étiquette ?
- Why
- Form fields without labels are difficult or impossible to understand with assistive technologies.
- Who is affected
- Blind people using a screen reader
- People using voice control
- People with attention or cognitive disorders
- See it for yourself
- Click on the text next to the field: if the cursor does not move into the field, the label is not linked.
- Fix
- Associate a visible or programmatic label with each form control.
Before<input id="email" type="email">
After<label for="email">Email</label><input id="email" type="email">
Where : 1 page(s), 1 element(s)
CRITICAL
2. Button has no accessible name
RGAA 11.9 — Dans chaque formulaire, l’intitulé de chaque bouton est-il pertinent (hors cas particuliers) ?
- Why
- Assistive technologies cannot announce the purpose of the button.
- Who is affected
- Blind people using a screen reader
- People using voice control
- See it for yourself
- Turn on the screen reader of your device (VoiceOver: Cmd+F5 on Mac; NVDA, free, on Windows) and listen to the element.
- Fix
- Add visible text, aria-label, or an accessible name linked to the button.
Before<button><svg aria-hidden="true"></svg></button>
After<button aria-label="Close dialog"><svg aria-hidden="true"></svg></button>
Where : 1 page(s), 1 element(s)
MAJOR
3. Document has no title
RGAA 8.5 — Chaque page web a-t-elle un titre de page ?
- Why
- A meaningful page title helps users understand where they are.
- Who is affected
- Blind people using a screen reader
- People with attention or cognitive disorders
- See it for yourself
- Open several tabs: can you tell which tab is this page?
- Fix
- Ensure each page has a descriptive title element.
After<title>Contact – Example Company</title>
Where : 1 page(s), 1 element(s)
MAJOR
4. HTML element has no lang attribute
RGAA 8.3 — Dans chaque page web, la langue par défaut est-elle présente ?
- Why
- Assistive technologies need the page language to pronounce content correctly.
- Who is affected
- Blind people using a screen reader
- See it for yourself
- Listen to the page with a screen reader: is the French read with an English accent?
- Fix
- Set the lang attribute on the root html element.
Where : 1 page(s), 1 element(s)
MAJOR
5. Insufficient color contrast
RGAA 3.2 — Dans chaque page web, le contraste entre la couleur du texte et la couleur de son arrière-plan est-il suffisamment élevé (hors cas particuliers) ?
- Why
- Low contrast makes text difficult to read for many users, including people with low vision.
- Who is affected
- People with low vision
- Everyone, on a phone or in bright sunlight
- See it for yourself
- Read the page on your phone outdoors, or lower the screen brightness.
- Fix
- Increase the contrast ratio between foreground and background colors.
Before.muted { color: #777; background: #888; }
After.muted { color: #1f2937; background: #ffffff; }
Where : 1 page(s), 1 element(s)
MAJOR
6. Iframe has no title
RGAA 2.1 — Chaque cadre a-t-il un titre de cadre ?
- Why
- Users need a clear title to understand embedded content.
- Who is affected
- Blind people using a screen reader
- See it for yourself
- Turn on the screen reader of your device (VoiceOver: Cmd+F5 on Mac; NVDA, free, on Windows) and listen to the element.
- Fix
- Add a concise and meaningful title attribute to the iframe.
Before<iframe src="https://example.com/embed"></iframe>
After<iframe src="https://example.com/embed" title="Video player"></iframe>
Where : 1 page(s), 1 element(s)
MAJOR
7. Alternative text missing on image
RGAA 1.1 — Chaque image porteuse d’information a-t-elle une alternative textuelle ?
- Why
- Screen reader users cannot understand the purpose of the image.
- Who is affected
- Blind people using a screen reader
- See it for yourself
- Disable images in your browser (or read the page with a screen reader): is the information still there?
- Fix
- Add a meaningful alt attribute, or alt="" for decorative images.
Before<img src="/team.jpg">
After<img src="/team.jpg" alt="Team gathered in the Lyon office">
Where : 1 page(s), 1 element(s)
RGAA 4.1.2. Automated checks only: "No issue detected" does not mean compliant, most criteria also need a manual check.