Accessibility
Effective 20 August 2026 · Last updated 20 August 2026 · Version 1.0
File Conversion aims to meet WCAG 2.2 Level AA basics for the primary workflow: keyboard use, visible focus, labels, contrast on the dark theme, and respect for `prefers-reduced-motion`. This statement describes what is implemented, what is not claimed, and how to report a barrier.
1. Commitment
The operator wants a visitor to finish a conversion without a pointer-only control and without a desktop-only layout. Accessibility is a product completion criterion, not a marketing badge. This page does not claim a formal third-party certification or a completed audit of every browser, including WebKit.
2. Scope
This statement covers https://convert.alexjungean.com: the homepage converter, the six published pair routes, legal pages, and the not-found page. It does not cover alexjungean.com.
3. Conformance target
The target is WCAG 2.2 Level A and AA success criteria that apply to a static, client-side tool: perceivable text, operable keyboard paths, understandable errors, and robust names/roles. Automated axe checks with tags `wcag2a`, `wcag2aa`, and `wcag22aa` run on `/`, each published pair, every legal document route, and the unpublished-pair 404.
Passing axe is necessary evidence, not a full manual audit. A full manual keyboard review on WebKit remains an open product gate.
4. Implemented features
- Semantic headings, labelled controls, and a primary navigation landmark.
- Visible focus rings using the brand colour.
- Keyboard reachability for Add images, target, Download, and Remove.
- Pair routes move focus to Add images.
- Source and selected target are announced; `aria-live` is used for the source indicator.
- Per-file errors are specific, not a generic “Something went wrong.”
- Dark theme tokens chosen for contrast; `color-scheme: dark`.
- Motion is functional and is shortened when `prefers-reduced-motion` is set.
- Self-hosted fonts with `font-display: swap` and system fallbacks.
- Images that are part of the chrome have text alternatives; user previews are the user’s own files.
5. Known limitations
- Conversion depends on the browser’s image pipeline. A disabled pair is a capability failure, not an alternative format.
- Colour input for JPEG background is a native control; its accessibility varies by browser.
- Very large files are rejected at measured ceilings; that can surprise users of camera photos above 2048 px on the long edge.
- Legal pages are long. A contents list is provided; a dedicated reading-mode stylesheet is not.
- WebKit system libraries are not assumed on the maintainer’s WSL environment; WebKit proofs are opt-in.
- The European Accessibility Act may apply to some economic operators from 28 June 2025. This Service is a free tool without checkout. The operator still targets WCAG 2.2 AA basics and will update this statement if the legal characterisation changes.
6. Compatibility
The converter is written for current Chromium and Firefox releases used in product evidence. Assistive technologies that work with those browsers and a standard OS accessibility stack are the intended combination. Zoom and browser text-size controls are supported through ordinary HTML/CSS; the layout is narrow-viewport capable.
7. Feedback and contact
If you cannot complete a conversion or read a legal page, email alex.jungean@gmail.com with the page URL, browser, assistive technology if any, and what you expected to happen. The operator will reply and, where a fix is required, treat it as a product defect.
8. Preparation of this statement
This statement was prepared on 20 August 2026 from the implemented product contract, automated accessibility tests, and the public routes listed above. It will be revised when routes, components, or known limitations change.
