Accessibility Statement

Our commitment

We believe privacy-first tools should be accessible tools. Zapptic is built with:

• Semantic HTML5 elements and landmark regions
• ARIA labels and roles on interactive elements
• Keyboard navigability — all tools can be operated without a mouse
• Visible focus indicators meeting WCAG 2.1 AA contrast requirements
• Sufficient colour contrast for text and UI elements in both light and dark modes
• Screen-reader-compatible file-drop zones with descriptive labels
• Progress and status announcements for conversion results via ARIA live regions
• No time limits on tool interactions
• No flashing or strobing content

Technical standards

We rely on the following technologies to achieve accessibility:

• HTML5
• CSS (Tailwind CSS v4 with CSS custom properties)
• JavaScript / React (Next.js 15 App Router)
• WAI-ARIA 1.2

Known limitations

While we strive for full WCAG 2.1 AA conformance, some limitations exist:

• File output previews: Converted image thumbnails include descriptive alt text (file name and format), but the visual preview is inherently limited for users relying on screen readers.
• PDF output: Generated PDF files from the HEIC converter are image-based and are not searchable or screen-reader navigable within the PDF.
• Zip downloads: Batch downloads are delivered as a .zip file; navigating the zip contents requires your OS file manager.

We are actively working to address these limitations.

Feedback and contact

If you encounter an accessibility barrier on Zapptic — a tool that is difficult to use with a keyboard, a missing label, or a contrast issue — please tell us. We take accessibility reports seriously and aim to respond within 5 business days.

Formal complaints

If you are not satisfied with our response to an accessibility complaint, you may contact the relevant accessibility enforcement body in your jurisdiction. In the EU, this is typically your national supervisory authority. In the UK, you may contact the Equality and Human Rights Commission.