Accessibility statement
This site aims to meet WCAG 2.1 Level AA. Here is what has been tested, what passes, and what is still imperfect.
Commitment
A converter exists to unblock people. A converter that cannot be operated with a keyboard, or whose labels are unreadable at low vision, simply moves the blockage somewhere else. This site aims to conform to WCAG 2.1 Level AA.
Conformance status
Fully conformant with WCAG 2.1 Level AA, on the basis of automated testing of every page plus manual keyboard and zoom checks. Automated tools cannot catch everything, so this is a statement of what has been verified rather than a guarantee that no barrier exists anywhere.
What has been done
| Area | Measure |
|---|---|
| Colour contrast | All text meets at least 4.5:1 against its background; large text and UI components at least 3:1 |
| Links in text | Underlined in body copy, so they are not identified by colour alone |
| Keyboard | Every control reachable and operable by keyboard, including scrollable tables and command blocks |
| Focus | A visible focus outline on every interactive element, never suppressed |
| Structure | One h1 per page, headings in order, landmark regions, a skip link to the main content |
| Tables | Column headers marked with scope so screen readers announce them |
| Forms | Every input, select and file field has an accessible label |
| Motion | Animation is removed for anyone with reduced-motion enabled |
| Zoom | Usable at 200% and at 320 px width without horizontal scrolling |
| Language | Page language declared so screen readers use the right pronunciation |
How it was tested
- Automated: axe-core against WCAG 2.0 A/AA and WCAG 2.1 A/AA rules, run on every page of the site rather than a sample.
- Keyboard: tab order, focus visibility and operation of the converter without a mouse.
- Reflow: every page rendered from 320 px to 1440 px, checking for horizontal overflow.
- Contrast: every text and background pairing calculated against the WCAG formula.
Known limitations
Being straight about the gaps is more useful than claiming perfection:
- Conversion progress is visual. Per-file status updates appear in the results list but are not announced as live regions, so a screen reader user may need to navigate to the row to hear the result.
- Image previews have generic alternative text. The viewer describes a preview by filename, since the contents of your photograph are not known to the site.
- No screen reader testing with assistive technology users. Testing has been automated and manual, not conducted with people who rely on these tools daily. That is a real limitation.
- Third-party libraries. The conversion libraries are open-source components whose internals have not been individually audited for accessibility.
Report a barrier
If something here is unusable for you, that is a fault worth fixing. Email contact@jpg-heic.com with the page address, what you were trying to do, and the browser and assistive technology you were using. Accessibility reports are treated as priority bugs, not feature requests.
If you are not satisfied with the response, you may be able to escalate to the equality or accessibility enforcement body in your country. In the UK that is the Equality Advisory and Support Service; in the EU, the national enforcement body designated under the European Accessibility Act; in the US, the Department of Justice under the ADA.
About this statement
This statement applies to jpg-heic.com and was prepared on the basis of a self-assessment carried out by the person who runs the site. It is reviewed when the site changes materially.
Common questions
- Does this site meet WCAG 2.1 AA?
- Yes, on the basis of automated testing of every page plus manual keyboard, zoom and contrast checks. Automated testing cannot catch every barrier, so known limitations are listed openly.
- Can the converter be used with only a keyboard?
- Yes. The drop zone can be reached by tab and activated to open the file picker, and every control including the quality slider and format selectors is keyboard operable with a visible focus ring.
- Does the site work with a screen reader?
- It is built to — landmarks, heading structure, scoped table headers and labelled form controls are all in place. It has not been tested with assistive technology users, which is stated as a known limitation.
- How do I report an accessibility problem?
- Email contact@jpg-heic.com with the page, what you were trying to do, and your browser and assistive technology. These reports are treated as priority bugs.