Accessibility Statement

Our commitment

GetFloristPOS (the legal entity named on your invoice) wants every florist, shop manager, driver and customer to be able to use this website and our point-of-sale software, whatever device, browser or assistive technology they rely on. A shop owner reading on a phone between deliveries, a manager who uses a screen reader, a staff member who navigates by keyboard only, or a customer who needs larger text should all be able to get the job done.

This statement covers the marketing website at getfloristpos.com and, where noted, the hosted GetFloristPOS application and the online stores it generates for florists. It explains the standard we aim for, what we have done, what we know still falls short, and how to tell us about a problem.

The standard we aim for

Our target is conformance with the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, published by the World Wide Web Consortium. WCAG 2.2 AA is the widely used benchmark for accessible web content and is referenced, directly or indirectly, by accessibility expectations in the United States, the United Arab Emirates and many other places.

“Target” is the honest word. We have not had this site or the application formally audited or certified by an independent body, and we do not claim full conformance. We test as we build and fix problems as we find them, and this statement will be updated as that work moves forward.

What we have done on this website

When building and reviewing this marketing site we work to the following practices:

• Structure. Pages use real headings in order, landmark regions (header, navigation, main content, footer) and lists where content is a list, so screen readers can move around quickly.
• Keyboard use. Menus, buttons, the language and country selectors, the search box and forms can be reached and used with a keyboard, and the focus indicator stays visible.
• Color and contrast. Text and interactive elements are designed to meet AA contrast ratios in both the light theme and the dark theme. Information is not carried by color alone.
• Text alternatives. Meaningful images and icons carry text alternatives; decorative paper textures and botanical illustrations are hidden from assistive technology.
• Motion. Our design uses gentle motion (sheets settling, petals drifting). If your device is set to reduce motion, we honor that setting and keep animation to a minimum.
• Accessibility preferences. The site includes a small accessibility panel that remembers choices such as larger text or reduced motion in your browser’s local storage (the gfp-a11y entry described on our cookies page). It stores no personal information.
• Languages and direction. Pages in Arabic and Urdu are marked with the correct language and right-to-left direction, and use fonts chosen for legibility in those scripts.
• Forms. Form fields have visible labels, errors are described in text, and we avoid time limits on filling in a form.
• Target size. We aim for touch targets that are comfortable on a phone, in line with WCAG 2.2 target-size guidance.
• Zoom and reflow. Content reflows to a single column and remains usable when zoomed to 400 percent or viewed on a narrow screen.

The application and generated online stores

The GetFloristPOS application is a busy working tool: a till, order book, stock screens and reports. We apply the same target to it, but it is a large product and some older screens were not designed with WCAG 2.2 in mind. We prioritize the screens staff use most, such as checkout, order entry and delivery scheduling.

Online stores that the application generates from a florist’s catalogue use accessible templates as a starting point. Each florist controls their own product photos, descriptions and any custom content, so the accessibility of a particular shop also depends on the choices that florist makes. If you are a customer of a florist and run into a barrier on their store, please tell the florist and, if you like, tell us too.

Known limitations

We would rather tell you about problems than have you find them. At the time of the date above, we know of the following:

• Security check on forms. Our forms are protected by Cloudflare Turnstile. In most cases it runs invisibly, but on occasion it may show a challenge. If that challenge is a barrier for you, use another route listed in the “Report a problem” section and we will help you directly.
• Data-heavy screens in the application. Some reports and wide tables in the application are hard to use at high zoom or on small screens, and some table headers are not yet announced consistently by screen readers.
• Drag-and-drop. A few application features, such as reordering items, rely on drag-and-drop. We are adding keyboard and single-pointer alternatives; until then our support desks can make those changes for you.
• Printed and PDF documents. Receipts, van sheets and invoices are designed to be printed. PDF versions may not yet be fully tagged for screen readers.
• Third-party content. Embedded booking calendars, payment pages run by a florist’s own card processor, and other services we do not control may not meet the same standard.
• Translations. Interface translations into Arabic, Urdu and Spanish are reviewed by people, but some less-used screens may still mix languages, which can confuse assistive technology.

Compatibility

This site is built to work with current versions of major browsers (Chrome, Edge, Firefox and Safari) on desktop and mobile, and with common assistive technologies such as NVDA and JAWS on Windows, VoiceOver on macOS and iOS, and TalkBack on Android. It relies on HTML, CSS and JavaScript; core content stays readable if scripts fail to load.

Report a problem or ask for help

If something on this site or in the application stops you from doing what you came to do, please tell us. Use the contact form at /contact and choose accessibility as the subject, or use the address shown via the Show email button on /contact. Our support desks can also be reached by phone or WhatsApp during their local hours, as listed on the contact page.

It helps if you tell us:

• the page address or the screen in the application;
• what you were trying to do and what happened;
• the browser, device and any assistive technology you use.

You do not need to give technical detail. A plain description is enough.

How we respond

We will acknowledge your report and give a substantive response within 5 business days. Where we can fix the problem quickly we will; where it needs more work, we will tell you what we plan to do and roughly when. In the meantime, if a barrier stops you from completing a task, such as requesting a demo, starting a trial or placing information into your account, we will offer an alternative way to get it done, for example over the phone with one of our support desks.

Legal context

In the United States, the Americans with Disabilities Act and related guidance are generally understood to apply to many businesses’ websites and digital services, and WCAG is the most common reference point. In the United Arab Emirates, Federal Law No. 29 of 2006 on the rights of people of determination, as amended, and national digital accessibility policies encourage accessible digital services. Pakistan’s national policy and provincial laws on persons with disabilities support equal access. We follow WCAG 2.2 AA as a practical standard across all three markets.

This statement describes our approach and is not legal advice. Florists who run their own online store through GetFloristPOS remain responsible for the accessibility of the content they add and should take their own advice on their obligations.

Updates to this statement

We review this statement when we make significant changes to the site or application, and at least once a year. The date at the top shows when it was last updated.