Company

Accessibility

A store owner using a screen reader, a keyboard or a magnifier should get as much out of Feedara as anyone else. This page says how close we are, and where we are not there yet.

Last updated 23 September 2026

On this page

What we aim for

We work to the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, the standard most of the world uses. We treat it as a floor, not a finish line.

How we test

  • An automated check of every public page, including real audit reports, in light and dark themes, at desktop and phone widths, against WCAG 2.2 AA. It last ran on 23 September 2026. It found two problems, faint text a fraction too pale on shaded panels and table marks a screen reader could not describe, and both were fixed the same day.
  • A contrast check of every colour pairing the interface uses, in both themes, which runs whenever a colour changes.
  • Checks by hand with a keyboard, and of the screens behind sign-in, which an automated tool cannot reach.

An automated check finds perhaps a third of real accessibility problems. Passing one is where we start, which is why the next section exists.

What works today

  • Every page can be used with a keyboard alone, and the first key press offers a link past the menu.
  • The item in focus always shows a clear outline.
  • Text meets contrast requirements in both the light and the dark theme, and the theme you choose is remembered.
  • Colour never carries meaning on its own: every pass, warning and failure also has its own shape and its own words.
  • Pages zoom to 200% without losing content, and fit a phone screen without sideways scrolling.
  • Animation is minimal, and switches off when your device asks for reduced motion.
  • Every page has a clear structure of headings and landmarks for screen readers to move through.

What is not right yet

  • The visibility chart tells a screen reader which assistant it shows, but not the numbers month by month. The grid below it carries every reading in words, and we plan to give the chart a proper text version.
  • Downloaded PDF reports are generated with the structure screen readers use, but we have not yet tested them with one.
  • We have not yet had people who rely on assistive technology test Feedara. We intend to before we grow, because no checklist replaces them.

Telling us about a problem

If any part of Feedara is hard to use, or you need a report in another format, write to hello@feedara.ai. Tell us the page and what went wrong, and we will reply within two working days, fix what we can, and find another way to get you the information in the meantime.

If you are not happy with our response, the Equality Advisory and Support Service can advise you.