We want every boutique owner, staff member and shopper to be able to use our website, whatever device, browser or assistive technology they use. This statement covers getboutiquepos.com. It explains what we aim for, what we have built, what we know still needs work and how to tell us about a problem.
What standard do we aim for?
We target the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. These guidelines are published by the World Wide Web Consortium (W3C) and are the standard most accessibility laws and policies point to, including guidance under the Americans with Disabilities Act in the United States.
We describe our status as “aiming for” rather than “fully conforming” because we have not yet had an independent audit. We test as we build and fix problems as we find them.
What have we built in?
Keyboard use
Every link, button, menu, form and price toggle can be reached and used with a keyboard alone. A “skip to content” link appears first, so you can jump past the header. Menus and dialogs can be closed with the Escape key, and focus returns to where you were.
Visible focus
When you move through the page with Tab, the item in focus has a clear outline that meets WCAG 2.2 contrast and size rules. We do not hide focus outlines.
Reduced motion
If your device is set to reduce motion, animations are turned off or replaced with simple fades. You can also turn motion off in the site’s display settings, whatever your device setting is.
Text size and zoom
You can make text larger in the display settings, and the site works with browser zoom up to 400% without content being cut off or needing sideways scrolling on most pages.
Contrast and color
Text and controls meet AA contrast ratios in both light and dark themes. A higher-contrast option is available in display settings. We never use color alone to show meaning; for example, the selected plan and form errors also use text and icons.
Right-to-left languages
Arabic and Urdu pages are set to read right to left, with the layout, menus and icons mirrored where that makes sense, and the correct language set on the page so screen readers pronounce it properly.
Structure for assistive technology
Pages use real headings in order, landmarks (header, navigation, main, footer), labelled form fields, clear error messages linked to the field they belong to, and descriptive link text. Images that carry meaning have text alternatives; purely decorative images are hidden from screen readers.
Touch targets
Buttons and links are large enough to tap comfortably on a phone, with at least 24 by 24 pixels and usually 44 by 44 pixels of target space.
Display settings are remembered
Your display choices (text size, contrast, motion and theme) are saved in your own browser so they stay the same on your next visit. The Cookie Policy explains how this storage works.
What are the known limits?
We would rather tell you about these than have you find them by surprise.
- Fabric animation: some pages show a decorative fabric animation. It does not carry any information, it has a text alternative describing it, and it stops when reduced motion is on.
- Third-party embeds: some features come from other companies, such as the spam check on forms (Cloudflare Turnstile), booking calendars or embedded videos. We choose providers with accessibility in mind, but we cannot fully control how their parts work. If one blocks you, contact us and we will help another way.
- Screenshots of the app: product screenshots have descriptions, but they cannot show everything a sighted visitor sees in the image. A live demo is the best way to explore the app; we can run it at your pace.
- PDF and downloaded files: older downloadable files may not be fully tagged for screen readers. We will send an accessible version on request.
- The POS app: this statement covers the website. The BoutiquePOS app has keyboard support and translated interfaces, including Arabic and Urdu, but we have not yet audited it against WCAG 2.2 AA. We are working through it.
How we test
We check pages with automated tools, then by hand: keyboard-only navigation, screen readers on desktop and mobile, browser zoom, high-contrast and reduced-motion settings, and right-to-left layouts. New pages are checked before they go live.
How do I report a problem?
If you cannot use part of the site, or you need information in another format, please tell us using the form on our contact page. Choose “Accessibility” as the topic if it is offered, or mention it in your message.
It helps if you include:
- the page address (URL);
- what you were trying to do;
- the device, browser and any assistive technology you use.
We will reply within 5 business days. If the fix takes longer, we will tell you when to expect it and, in the meantime, give you the information or service another way, for example by phone, WhatsApp or a guided demo.
Is there anything else?
If you are not happy with our response, reply to our message and ask for it to be reviewed by someone else on the team. You may also have the right to complain to the authority that handles accessibility or equal access complaints in your country.
This statement was last reviewed on 18 October 2026. We review it at least once a year and whenever we make large changes to the site.
