Accessibility

The target

FileSlimmer is built against WCAG 2.2 level AA. That is a target with a test suite behind it, not a certification: an automated scan finds a well-defined subset of barriers, and the rest is found by people using the site.

What is implemented

• A skip link to the main landmark on every page, visible as soon as it takes focus.
• A file control that is a real <input type="file"> inside a <label>, so it works with the keyboard and with a screen reader before any JavaScript has run. Drag and paste are added on top of it, never instead of it.
• Semantic progress elements, and status updates announced at most every ten percentage points or on a phase change — not on every frame.
• Cancel controls on running tasks, and errors linked to the task they belong to.
• Status shown by text as well as colour, never by colour alone.
• Touch targets of at least 44 by 44 pixels.
• Layouts that hold together at 200% zoom without a horizontal scrollbar on the page; wide tables scroll inside their own box.
• Right-to-left layouts for Arabic, Hebrew and Urdu, with file names and byte sizes kept in their own direction.
• Reduced-motion preferences respected.
• File sizes announced in the units of your language.

How it is tested

An axe-core scan runs against the built output — not the development server — for the root page, a tool workspace in English, the same workspace in a right-to-left language, a legal document, a guide article and the offline page. Alongside it, an automated check asserts one h1 per page, a heading outline with no skipped level, a label on every form control, and a visible focus indicator. A violation fails the build rather than producing a warning.

Known limitations

• Product and interface text has been reviewed by a native speaker in English only. Other languages fall back to English where a reviewed string does not exist, so a screen reader may encounter mixed languages on those pages.
• The before-and-after result comparison is a visual aid. The numbers beside it — the original size, the new size and the reduction — carry the same information as text for anyone who cannot use the visual comparison.
• Some browser-supplied controls, such as the operating system's own file picker, cannot be styled or relabelled by a web page.

Reporting a barrier

If something here blocks you, write to info@zenitgroup.com.co with the page address and what you were trying to do. A description of the barrier is more useful than a suggested fix, and you do not need to name a WCAG criterion. See the contact page for what else that address handles.