Accessibility

Accessibility

Appetune's accessibility commitment, what has been done so far, what is known to be incomplete, and how to report a barrier.

A large share of Appetune’s readers are unwell, tired, or reading on a phone while doing something else. Accessibility is not a compliance exercise here — it is most of the audience.

What we are working to

WCAG 2.2 Level AA as the target standard.

What is in place

  • Semantic structure. Real headings, lists, and definition lists, in reading order, with one <h1> per page.
  • Keyboard operation. Every interactive element is a real button or link, reachable and operable by keyboard, with a visible focus outline.
  • Skip link. The first focusable element on every page skips the header.
  • Reduced motion. Animation and transitions are disabled for anyone whose system requests it.
  • Text that scales. Layouts use relative units and reflow rather than break when text is enlarged.
  • No motion-triggered content, no carousels, no auto-playing media.

Known gaps

We would rather list these than claim full conformance.

  • A formal audit against WCAG 2.2 AA has not yet been carried out.
  • Photography is still placeholder artwork; alternative text will be written with the images.
  • Interactive tools are not built yet. Each will need its own keyboard and screen-reader testing before it publishes.
  • Colour contrast has been designed against the standard but not yet verified across every component and state by a third party.

Reporting a barrier

[email protected]

Tell us the page, what you were trying to do, and the assistive technology and browser you were using if you know them. We treat access barriers with the same priority as factual corrections, and we will tell you what we are doing about it rather than closing the report silently.

Last updated

Hit a barrier? That is a bug.

Access problems are treated with the same priority as factual errors.