Accessibility statement
Last updated 14 September 2026 · Applies to app.rara.recipes, rara.recipes and rara-recipes.no
What this covers
This statement covers the RaRa application at app.rara.recipes — the private, invitation-only recipe archive — and the public pages on rara.recipes, including these legal pages. RaRa Recipes (“RaRa”) is operated by Backroad AS, org. no. 934 341 929, Bergen, Norway.
The standard we build to
Backroad AS builds RaRa to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. That is our target for every screen, in both the light and the dark theme and in both interface languages (Norwegian Bokmål and English): semantic structure, headings that describe each page, keyboard operability with a visible focus, a skip link past the navigation, colour contrast of at least 4.5:1 for text, touch targets of at least 24 pixels, and reduced motion when your device asks for it.
The accessibility obligations that apply to RaRa arise under Norwegian law — the Equality and Anti-Discrimination Act and the Regulation on universal design of ICT solutions, supervised by the Norwegian Authority for Universal Design of ICT (UU-tilsynet). For private-sector services that regulation requires a defined set of WCAG 2.0 Level A and AA criteria; WCAG 2.2 AA contains all of them, so our target exceeds the minimum. The European Accessibility Act (Directive 2019/882) applies in EU member states since 28 June 2025 but has not been incorporated into the EEA Agreement or Norwegian law; we treat it as a reference point, not as a claim of conformance.
Where we stand
We consider RaRa partially conformant with WCAG 2.2 Level AA: it has been built to the standard from its first screen, an automated review of the public pages and the source code runs every week, and confirmed findings are fixed on a fixed cadence — major findings within two weeks, minor findings within one month. A full assessment of the signed-in application as rendered on a phone, with a screen reader, has not yet been completed, so barriers we have not found may still exist.
Known limitations
- Page titles — until 3 September 2026 every screen shared the same browser title, so a screen reader gave no confirmation that the page had changed. Fixed: every screen now carries its own title.
- Page structure — until 13 September 2026 the header of several screens sat inside the main content, so the skip link did not skip past it and screen readers did not find it as a separate area. Fixed: every screen now has one header, outside the main content.
- Settings headings — until 14 September 2026 the section names on the Settings screen were styled text rather than headings, so a screen reader could not list them or jump between them. Fixed: Settings is replaced by You and a page for each collection, and every group on those pages has a heading.
- Signed-in screens not yet audited as rendered — the recipe editor, the photo and voice capture screens and the assistant conversation have been checked in code but not yet with assistive technology on a real device. This is the next planned review.
- Voice capture depends on your device — dictation uses the speech recognition your phone or browser provides. Where that is unavailable, typing and photographing a recipe give the same result.
How this statement was prepared
This statement was first prepared on 3 September 2026 by Backroad AS as a self-assessment: manual review of the source code, keyboard-only navigation, colour-contrast verification and a weekly automated review of the public pages. Open and resolved findings are tracked in the RaRa source repository under the label “accessibility”. An external audit has not been commissioned yet.
Tell us what got in your way
If something in RaRa is hard or impossible for you to use — a control the keyboard cannot reach, text that fights your screen reader, contrast that disappears — write to [email protected]. We answer within seven working days, and if the fix takes longer than that we tell you when to expect it. If you need a recipe or a page in another format, ask and we will provide it.
If you are not satisfied
If you are not satisfied with our answer, you can complain to the Norwegian Authority for Universal Design of ICT, UU-tilsynet, at uutilsynet.no.