Accessibility Statement
Last updated 2026-10-18
In plain words
We aim to meet WCAG 2.2 Level AA across retailposstudio.com. We test keyboard use, contrast in every theme and palette, reduced motion and right-to-left layouts. If something gets in your way, tell us through the contact form and we'll fix it or give you the information another way.
1. Our commitment
Shop owners run their businesses on phones, old laptops, bright shop floors and late-night screens, often in a second language. We want everyone to be able to read about RetailPOS Studio, compare plans and get in touch, whatever device, ability or language they use.
2. Conformance target
Our target is the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. We consider the site partially conformant: most content meets the target, and the known gaps are listed in section 5.
3. What we have done
- Keyboard. Every menu, panel, dialog, tab set, slider and form can be used with a keyboard. A skip link jumps to the main content. Focus is visible on every surface and returns to the control that opened a panel when it closes.
- Closing overlays. Every panel, search overlay and dialog has a visible close button of at least 44 by 44 pixels, closes with Escape on desktop and closes when you tap outside it.
- Contrast. We check text, buttons, borders and focus rings programmatically against every combination of light mode, dark mode and each colour palette, aiming for at least 4.5:1 for body text and 3:1 for large text and interface parts.
- Motion. If your device asks for reduced motion, the scroll-zoom story, particles and animated headings are replaced by static content. You can also switch motion off in the accessibility panel.
- Accessibility panel. Change text size, turn on higher contrast, reduce motion and highlight links. Your settings are remembered on your device.
- Languages and direction. Pages declare their language. Arabic and Urdu pages use a real right-to-left layout with mirrored icons and arrows, and Urdu uses a Nastaliq font.
- Structure. One main heading per page, headings in order, landmarks, labelled form fields with clear error messages, and descriptive alternative text for meaningful images.
- Zoom and reflow. Pages are designed to work at 320 pixels wide and at 200% zoom without sideways scrolling.
4. How we test
We test with keyboard only, at screen widths from 320 to 1920 pixels, with browser zoom up to 200%, in light and dark mode with each palette, and with reduced motion switched on. We use automated checks for contrast and markup. We have not yet completed testing on a physical iOS or Android device with a screen reader; that is planned before launch.
5. Known limitations
- Scroll-zoom story. The home page tells its story by zooming out across one illustrated scene as you scroll. It is visual by nature. Each chapter’s text is also available as plain headings and paragraphs, and with reduced motion on you get a static, chapter-by-chapter version.
- Localized pages. Arabic, Urdu, Spanish and Chinese currently cover the home, pricing and contact pages. Other pages are in English for now; more translations are planned.
- Illustrations. Some decorative illustrations carry no alternative text on purpose because they repeat what the text already says.
- Third-party content. The spam check on forms (Cloudflare Turnstile) and any embedded maps are provided by third parties and may not fully meet our target.
6. The RetailPOS Studio app
This statement covers the marketing website. The POS app itself is a separate product. Tell us about any barrier you meet in the app and we will work with you on it.
7. Report a barrier
If you can’t use part of this site, or you need information in a different format, send us the contact form and choose “Accessibility” as the topic, or message us on WhatsApp in your market. Tell us the page, what you were trying to do, and the device or assistive technology you use. We aim to reply within two business days and to fix confirmed issues as quickly as we can.
8. Formal complaints
If you are not satisfied with our response, you can contact the relevant authority in your country. In the United States, accessibility complaints may be raised with the U.S. Department of Justice.
9. Technical details
The site is built as static HTML pages with CSS and a small amount of JavaScript. Content, headings, links and forms are present in the HTML before any script runs, so the pages remain readable if JavaScript fails or is switched off. Interactive parts such as the menu panel, search, the country switcher and the focus-ring step dial are built with standard HTML controls and ARIA attributes where they add meaning, and they are tested in current versions of Chrome, Firefox, Safari and Edge.
10. Review of this statement
We review this statement whenever the site changes significantly and at least once a year. The date at the top shows the last review.
Questions about this policy? Contact us.