Accessibility

Making Reveu easier for everyone to use.

Reveu is committed to improving the accessibility and usability of its public website for people with different abilities, technologies, devices, and ways of navigating the web.

Last updated: 18 July 2026 Applies to: reveu.me

Our approach

Accessibility considered throughout the experience.

Reveu considers structure, navigation, readability, forms, responsive layouts, and assistive-technology support while developing the website.

01

Clear structure

Pages use headings, landmarks, labels, and consistent content organisation to help visitors understand and navigate them.

02

Keyboard access

Interactive controls are intended to remain available to people who navigate without a mouse or touchscreen.

03

Readable content

Content is written and presented with readable typography, spacing, contrast, and responsive layouts.

04

Useful feedback

Forms aim to provide clear labels, instructions, validation messages, status updates, and alternative contact methods.

Accessibility at a glance

Reveu aims to provide a website that can be used across different devices and with common assistive technologies.

  • The website uses semantic HTML and labelled controls.
  • Navigation and forms are intended to work with a keyboard.
  • Content is designed to adapt to smaller screens and browser zoom.
  • Form errors and submission results are presented in text.
  • Accessibility problems can be reported directly to Reveu.

01

About this statement

This accessibility statement applies to the public Reveu website at reveu.me.

It covers public pages including:

  • The homepage
  • Feature and pricing information
  • The early-access waitlist
  • The support centre
  • The contact form
  • Company and changelog pages
  • Privacy, legal, security, and accessibility information

The Reveu Shopify application may require a separate accessibility assessment because it is presented inside the Shopify administration interface and includes different controls, workflows, and third-party platform components.

02

Accessibility standard

Reveu aims to use the Web Content Accessibility Guidelines version 2.2 at Level AA as its technical accessibility benchmark.

WCAG is organised around four broad principles. Website content should be:

Perceivable

Information should be presented in ways that visitors can perceive using different senses and technologies.

Operable

Navigation and controls should be usable through different input methods.

Understandable

Content, navigation, instructions, and behaviour should be reasonably clear and predictable.

Robust

Content should work with a range of current browsers, devices, and assistive technologies.

Reveu does not currently claim that every page fully conforms to WCAG 2.2 Level AA. Formal testing and remediation work is still required before making that claim.

Read the WCAG 2.2 standard

03

What you should be able to do

Reveu intends for visitors to be able to:

  • Navigate the website using a keyboard
  • Move through page headings and landmark regions
  • Understand the purpose of links and buttons
  • Zoom and resize text without losing essential content
  • Use the website on desktop, tablet, and mobile screens
  • Complete the waitlist and contact forms using labelled fields
  • Understand form errors and submission results
  • Use common screen-reader and browser accessibility features
  • Access important information without relying only on colour
  • Contact Reveu through an alternative email method

04

Current accessibility measures

Measures currently used across the public website include:

  • Semantic headings and page sections
  • Header, navigation, main-content, aside, and footer landmarks
  • Descriptive page titles and metadata
  • Breadcrumb navigation on internal pages
  • Labels connected to form fields
  • Required-field and validation information presented in text
  • Live status regions for form submission results
  • Visible links and buttons with descriptive wording
  • Decorative images hidden from assistive technology where appropriate
  • Responsive page layouts
  • Relative and scalable typography
  • Focusable native HTML controls
  • Email alternatives for website forms

05

Forms and status messages

The waitlist and contact forms are designed to provide:

  • Visible labels and instructions
  • Appropriate input types
  • Required-field indicators
  • Maximum field lengths
  • Text-based validation messages
  • Focus movement to the first invalid field where possible
  • Loading, success, and failure messages
  • A direct email alternative

Visitors should not be required to understand colour alone to identify an error. Error messages should also explain what needs to be corrected.

Contact hello@reveu.me if a form cannot be completed using your browser, device, input method, or assistive technology.

06

Current limitations

Reveu has not yet completed a formal independent accessibility audit. As a result, we cannot currently confirm that every accessibility issue has been identified.

Areas still requiring continued review include:

  • Keyboard navigation across every page and responsive state
  • Focus visibility and focus order
  • Colour contrast for all text and interactive states
  • Browser zoom and text resizing at higher magnification levels
  • Screen-reader announcements for dynamic form updates
  • Mobile navigation behaviour
  • Reduced-motion preferences for reveal animations and transitions
  • Compatibility with a broader selection of assistive technologies
Not a full compliance claim

The statement that Reveu aims to follow WCAG 2.2 Level AA should not be interpreted as confirmation that every success criterion has already been independently tested and met.

07

Third-party content and services

Some parts of the Reveu experience may depend on third-party services or platforms, including:

  • Shopify
  • Google Firebase
  • Web browsers and operating systems
  • Email applications
  • Website hosting and network providers
  • External websites linked from Reveu

Reveu does not control every aspect of a third-party service’s interface, accessibility, availability, or assistive-technology compatibility.

We will still review accessibility problems where a third-party dependency affects an important Reveu workflow and will seek a reasonable alternative where practical.

08

Alternative formats and assistance

Contact Reveu if you need website information in a different format or require assistance accessing a particular page.

Depending on the request, we may be able to provide:

  • A plain-text version of website information
  • Information copied into an email
  • A clearer explanation of a feature or policy
  • Help completing an enquiry by email
  • An alternative route to important information

Include the page or content you need, the difficulty you experienced, and the format or adjustment that would help.

Alternative-format requests hello@reveu.me

09

Report an accessibility problem

Accessibility feedback helps Reveu identify problems that may not be visible during ordinary development and testing.

When reporting a problem, include:

  • The page or feature affected
  • What you were trying to do
  • What prevented you from completing the task
  • Your browser and device, where relevant
  • The assistive technology used, where relevant
  • The adjustment or alternative that would help
Accessibility feedback hello@reveu.me

10

Testing and review

Accessibility review should include a combination of automated testing and manual checks.

Planned and ongoing checks include:

  • HTML structure and landmark review
  • Keyboard-only navigation
  • Visible focus testing
  • Colour-contrast testing
  • Browser zoom and text-resizing checks
  • Responsive layout testing
  • Form-label and error-message review
  • Screen-reader checks for key workflows
  • Reduced-motion behaviour
  • Testing after significant website changes

This statement will be updated when a more complete accessibility audit has been performed or when significant accessibility issues are identified and resolved.