Skip to main content

Accessibility Statement

Effective: 1 August 2026

Our Commitment

Savora is committed to ensuring that our website and mobile application are accessible to everyone, including people with disabilities. We believe that every person should be able to discover recipes, plan meals, and cook with confidence, regardless of ability. Accessibility is not an afterthought at Savora -- it is a core part of how we design and build our products.

Conformance Standards

We strive to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA published by the World Wide Web Consortium (W3C). These guidelines are the internationally recognised standard for web accessibility and address a wide range of recommendations for making web content more accessible.

While WCAG Level AA is our target, we go beyond these requirements wherever possible to provide the best possible experience for all users.

Measures We Take

We implement the following measures to ensure accessibility across the Savora platform:

Design and Development

  • Semantic HTML: We use proper HTML elements (headings, landmarks, lists, forms) to convey meaning and structure to assistive technologies.
  • Keyboard navigation: All interactive elements are accessible via keyboard. Users can navigate the entire site and app using the Tab, Enter, Escape, and arrow keys without requiring a mouse.
  • Focus management: Visible focus indicators are provided on all interactive elements. Focus is managed appropriately when modals, dialogs, and menus are opened or closed.
  • Colour contrast: All text and interactive elements meet or exceed WCAG AA contrast ratio requirements (4.5:1 for normal text, 3:1 for large text). We test both light and dark themes for compliance.
  • Responsive design: The website adapts to different screen sizes, orientations, and zoom levels up to 400% without loss of content or functionality.
  • Skip links: A "Skip to main content" link is provided to allow keyboard and screen reader users to bypass repetitive navigation.
  • Alternative text: All meaningful images, including recipe photos and icons, have descriptive alternative text. Decorative images are marked appropriately so they are ignored by assistive technologies.
  • Form accessibility: All form fields have associated labels. Error messages are clearly identified and announced to screen reader users. Required fields are indicated both visually and programmatically.
  • ARIA attributes: Where native HTML semantics are insufficient, we use WAI-ARIA roles, states, and properties to ensure that custom components (such as dropdowns, modals, and tabs) are fully accessible.

Content

  • Plain language: We write content in clear, concise language to make it understandable for the widest possible audience.
  • Structured content: Recipes use a consistent structure with clearly defined sections for ingredients, instructions, nutritional information, and cooking times, making them easier to navigate with assistive technologies.
  • Link text: Links use descriptive text that makes sense out of context. We avoid generic link text such as "click here" or "read more."

Testing and Quality Assurance

  • Automated testing: We use automated accessibility testing tools (including axe-core and Lighthouse) as part of our continuous integration pipeline to catch issues early.
  • Manual testing: We conduct regular manual testing with screen readers (VoiceOver, NVDA, TalkBack) and keyboard-only navigation to verify the user experience.
  • User testing: We seek feedback from users with disabilities to identify and address real-world accessibility barriers.
  • Ongoing audits: We perform periodic accessibility audits and address identified issues in a timely manner.

Known Limitations

While we strive to make all parts of Savora accessible, some areas may have limitations:

  • Ingredient scanning: The camera-based ingredient scanning feature relies on visual input and may not be fully accessible to users who are blind or have low vision. We are actively exploring alternative input methods, including voice-based ingredient entry, to provide an equivalent experience.
  • Third-party content: Some embedded content from third-party providers may not fully meet accessibility standards. We work with our providers to improve accessibility and seek alternatives when possible.
  • User-generated content: Recipes and reviews submitted by users may not always include alternative text for images or use proper formatting. We encourage accessible content creation and provide guidance to contributors.

Compatible Assistive Technologies

Savora is designed to be compatible with the following assistive technologies:

  • Screen readers: VoiceOver (macOS/iOS), NVDA (Windows), TalkBack (Android)
  • Screen magnification software
  • Speech recognition software
  • Keyboard-only navigation
  • Switch devices and alternative input methods
  • Browser zoom up to 400%

We recommend using the latest versions of modern browsers (Chrome, Firefox, Safari, Edge) for the best accessible experience.

Feedback and Contact

We welcome your feedback on the accessibility of Savora. If you encounter an accessibility barrier, have difficulty using any part of our website or app, or have suggestions for improvement, please contact us:

When contacting us about an accessibility issue, please include the following information to help us address it effectively:

  • A description of the issue you encountered
  • The URL or screen where the issue occurred
  • The device, operating system, and browser you were using
  • Any assistive technology you were using (e.g., screen reader, magnifier)

We aim to acknowledge all accessibility feedback within two business days and to resolve reported issues as quickly as possible.

Continuous Improvement

Accessibility is an ongoing effort. We are committed to continually improving the accessibility of Savora. Our team receives regular accessibility training, and accessibility requirements are integrated into our design and development processes from the start of every project.

This statement was last reviewed on 1 August 2026.