Accessibility
Built for everyone.
Filum is built to work for every user regardless of how they interact with a computer. This page describes what we have built, what we are working on, and how to reach us if you find something that does not work.
Standards we target
All tools and pages aim to meet WCAG 2.1 Level AA. This means every interactive element is keyboard-operable, every non-text element has a text alternative, and no content is conveyed by colour alone.
Keyboard navigation
Every interactive control — file pickers, buttons, sliders, sort handles, tabs, and navigation links — is reachable and operable by keyboard alone. Focus is visible at all times: a 2-pixel ring in the brand colour appears on focus. No mouse is required for any core function.
Screen reader support
File status, conversion progress, and error messages are announced via ARIA live regions. Every icon that conveys meaning has an accompanying text label. Form controls have explicit labels, not placeholder-only labels. Sort handles and icon buttons carry aria-label values that describe the action.
Colour and contrast
Text contrast ratios meet WCAG AA: body text is 7:1 on the default dark background. Colour is never the only means of conveying information — status (error, success) is paired with icons and text. A high-contrast preference detected via the OS switches to the highest-contrast available palette automatically.
Motion
All animations respect the prefers-reduced-motion system preference. When reduced motion is on, transitions are replaced with immediate state changes — no decorative movement occurs. The animated thread on the homepage is hidden under this preference.
Tool-specific notes
Drag-and-drop in the image-ordering and page-organising tools is supplemented by arrow-key controls. File upload is always also available via a button that opens the system file picker. Preview thumbnails carry meaningful alternative text describing the page or image content.
Known limitations
PDF preview thumbnails are generated at runtime — the generated image alt text describes position (e.g. "Page 1") rather than content. Screen readers cannot read the visual content of a PDF page without OCR. The OCR tool produces a text-selectable PDF output, but this output is downloaded, not presented inline.
How to report an issue
If you find an accessibility barrier on any tool or page, please contact us via the contact page. Include the page URL, the assistive technology you use, and a description of the barrier. We will investigate and respond within 5 business days.