Accessibility

This page covers the public pages of anym.fr. It describes an approach and measures in place; it is not a declaration of compliance issued after an RGAA audit.

It is intended to make the approach clear and direct reports to the right place. A full compliance audit remains separate from this information.

Accessibility is used here in its practical sense: being able to consult information, understand the cues and use essential actions with different navigation methods. Configurations, browsers, assistive technologies and individual preferences vary, so this page does not claim to describe every possible use. It explains the visible choices and shows how to report a concrete issue where the result does not meet a need.

The measures below concern the structure and behaviour of the public site. They do not replace the settings of your browser, system or assistive technology: those settings remain the most direct way to adapt text size, contrast, zoom, speech output or reduced motion to your own circumstances.

• Reach the content directlyFrom the first keyboard navigation, a skip link takes you to the main content without making you go through the whole navigation and header. This shortcut is intended to avoid repeating the same navigation items on every page and to reach the title and useful content more quickly.
• Keep a visible point of referenceLinks and controls have a visible focus state. The journey is designed to stay understandable by keyboard and finger, with no information reserved for hover. Navigation order follows the reading order so that a person using Tab can understand where they are and what action is available next.
• Read without depending on 3DHeadings, text, navigation markers and important actions remain available in HTML. 3D and visual effects support the reading; they are not its only medium. A scene may enrich the atmosphere of a page, but it should not be the only way to reach information, understand an offer or continue a journey.
• Reduce motion and loadWhen reduced motion or data saving is enabled, the relevant visual experiences switch to a more static and lighter composition. This adaptation aims to preserve access to content and actions while limiting effects that might trouble someone sensitive to motion or penalise a constrained connection.

These measures are designed together. A skip link is useful only when it leads to a genuinely reachable area; a focus indicator helps only when it remains visible in its context; HTML content is an alternative only when it carries the information that is needed. That is why presentation changes need to preserve the page structure, its labels, its links and its fallback paths at the same time.

Your browser and system accessibility settings remain the best tools for adapting reading to your needs. Here are the useful cues on the site.

With a keyboard

Tab moves forward from one link or control to the next; Shift + Tab moves back. The first useful stop lets you skip straight to the main content.

With zoom

Text and essential information remain available on the page without requiring the visual scene to be enabled. Browser zoom and text-size settings can therefore be used freely.

With your system preferences

Reduced motion and data saving are considered by experiences that display a scene or animation. Editorial content remains the same.

No essential action should depend exclusively on pointer precision, a complex gesture, hover or the ability to perceive an animation. If you meet a barrier, simply describe what you were trying to do and what happened: that is more useful than a general assessment because it identifies the page, component and context that need correction.

Changes to public journeys should preserve the cues described here: a coherent heading structure, access to the main content, reading possible without a 3D scene and an interface that rearranges on a narrow screen.

This page is updated when those measures change significantly. It does not replace either expertise with affected people or a formal RGAA audit.

Checking a journey is not limited to a screenshot or a successful build. It also means observing the rendering at different screen widths, checking for horizontal overflow, moving through links and controls with a keyboard, and ensuring important information remains available when visual effects are reduced. These checks are useful, but by themselves they do not produce an RGAA compliance rate.

If a piece of content or a journey gives you trouble, write to contact@anym.fr and tell us the page, the action involved and, if you can, the browser, assistive technology or tool used.

A screenshot, the message encountered or the steps that lead to the issue are also useful. These details help reproduce the problem and address it in the right context.

You do not need to know technical vocabulary to report an issue. Saying that the keyboard cannot reach a button, that text becomes difficult to read after zooming, that an animation interferes with reading, or that information is absent from a screen reader is enough to start the conversation. Where an answer or workaround is possible, it is sought from the details provided.

This page is not an RGAA accessibility statement and it does not display a compliance percentage. Such a statement relies on a representative, documented and current evaluation; it must distinguish satisfied criteria, any non-compliances, exemptions and content outside the scope. Without that formal audit, presenting the measures described here as a certification or measured compliance would be misleading.

The choice here is therefore to document the concrete measures already visible on the site, explain their limits and keep a contact route. This transparency avoids confusing a continuous improvement approach with a regulatory attestation. If an official statement is published in the future, it will need to rely on an audit and set out its scope, date, method and results.