ToolsTemplatesPricingBlog
Start free
ToolsTemplatesPricingBlog
Start free
Glevu
Launch your business online today
The AI-native commerce OS for local business. Store, salon, or restaurant, live in minutes, run by chat.
Get started

Product

  • Tools
  • Templates
  • Pricing
  • Restaurants
  • Salons
  • Shops

Company

  • Blog
  • Help
  • Contact

Legal

  • Privacy policy
  • Terms of service
  • Cookie policy
  • Imprint
  • Accessibility
2026 Glevu. Built in Europe. All rights reserved.
Commitment

Accessibility statement

How Glevu approaches accessibility: the standard we target, how we test it, and why we build it in rather than rely on overlay widgets.

Last updated: 3 July 2026

Contents

  1. 1.Our commitment
  2. 2.The standard we work to
  3. 3.The European Accessibility Act
  4. 4.Why we do not use overlay widgets
  5. 5.Accessibility on merchant sites
  6. 6.Tell us about a problem

1.Our commitment

We want Glevu, and the sites people build with it, to be usable by everyone, including people who use assistive technology. Accessibility is something we build in from the start rather than bolt on afterwards.

2.The standard we work to

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We test against automated accessibility checks in our continuous integration, so regressions are caught before they ship, and we review the interface by hand as we build it. Accessibility is a continuing effort, and there will be areas we can still improve.

3.The European Accessibility Act

The European Accessibility Act has applied since June 2025. Many of the small businesses that use Glevu qualify as microenterprises and are exempt from parts of it, but the sites they publish should still be accessible to their customers. We give merchants a platform that starts from an accessible baseline so they are not left to solve this alone.

4.Why we do not use overlay widgets

We do not use accessibility overlay widgets, the pop up tools that claim to make any site compliant automatically. They often make the experience worse for the people they claim to help, and they attract legal complaints rather than prevent them. We build accessibility into the product itself instead.

5.Accessibility on merchant sites

Sites built on Glevu inherit our accessible components and templates. A per business accessibility statement can be generated for a merchant site, describing its posture and a contact for accessibility issues. Content a merchant adds, such as images and documents, remains that business's responsibility.

6.Tell us about a problem

If you hit an accessibility barrier on glevu.com, we want to hear about it so we can fix it. Please contact us with the page and what went wrong:

  • Email: accessibility@glevu.com

For how we handle any personal data in your message, see our Privacy policy.