Accessibility

This is a statement of intent and a list of what we know is wrong. It is not a declaration of RGAA conformity: no independent audit has been carried out, so we make no conformity claim at all.

Where we stand legally

Article 47 of French law no. 2005-102 imposes an accessibility declaration on public bodies, on organisations delivering a public service, and on private companies above a turnover threshold set by decree. The European Accessibility Act (directive 2019/882) exempts microenterprises providing services. MeoWeo is neither a public body nor anywhere near either threshold, so it falls under no such obligation, whatever legal form it eventually takes. We publish this page because the tools should be usable, not because a regulator requires it, and we would rather say plainly what does not work than say nothing.

What we aim for

WCAG 2.1 level AA as the working target: text that meets contrast requirements, controls that carry a name, layouts that survive zoom and small screens, and no feature that depends on colour alone.

What works today

• Every slider in the audio editor is a native range input with a label, so it responds to the keyboard and reports its value to a screen reader.
• The cut markers and the fade handles on the waveform are focusable, are exposed as sliders, and can be moved with the arrow keys, not only by dragging.
• Animation on this site honours prefers-reduced-motion: the scroll reveal on these pages simply does not run when your system asks for reduced motion.
• Everything is laid out mobile-first and holds together down to a 375 px viewport.

What does not work yet

• Reordering pages in the PDF tools requires a pointer. The page grid at pdf.meoweo.com is a drag surface: the cards cannot be reached with the keyboard, and there is no alternative way to move or select a page. This is the most serious gap we know of and it makes that part of the suite unusable without a mouse or a touchscreen.
• Neither suite has been tested with a screen reader end to end. Individual controls are labelled, but we cannot claim the whole flow reads sensibly.
• The tools convey progress and errors visually. There is no audible or live-region announcement when a long export finishes.
• Reading an audio waveform or a page thumbnail is inherently visual, and we offer no textual equivalent for either.

Third-party content

The file pickers and the download prompts belong to your browser and are outside our control. The PDF you produce inherits the accessibility of the PDF you started from: our tools do not add structure or tags to a document that had none.

Tell us

If something blocks you, write to support@meoweo.com and say what you were trying to do and what stopped you. Reports about the audio editor at audio.meoweo.com and the PDF tools are equally welcome. This is a small project and we cannot promise a deadline, but a concrete report is worth more to us than a generic audit.