Accessibility

1. Commitment

DwumaPOS aims to make the marketing site, merchant admin, point of sale, buyer portal, rider and supplier portals, and shop storefronts usable by people with disabilities. We design against WCAG 2.2 Level AA and the EN 301 549 expectations customers ask for in 2026 procurement.

2. What we support today

Keyboard operation on primary flows, visible focus rings, skip links to content and Help, labelled form fields with page-level error summaries on major commerce and settings forms, dialogs that trap and restore focus, reduced motion and forced-colors focus rings, 24px minimum targets (44px on shop and POS primaries), chart data tables for screen readers, and automated axe checks (including WCAG 2.2 tags) on login shells, dashboards, POS, checkout, buyer orders, platform billing, rider jobs, and supplier orders.

3. Conformance summary (ACR / VPAT-style)

This section is our public Accessibility Conformance Report summary for procurement. Evaluation methods: axe-core in Playwright CI, keyboard contracts, 320px reflow checks, and scripted screen-reader landmark/focus paths. Scope: DwumaPOS web products listed above. Desktop Electron register shares the same POS UI components and is covered by the web register scans.

| Standard | Level | Status | | --- | --- | --- | | WCAG 2.2 | A | Supports (primary flows) | | WCAG 2.2 | AA | Supports with exceptions (hover-only chart tips; merchant theme overrides) | | EN 301 549 | Align | Partial — statement + feedback channel published; formal lab audit optional |

Exceptions: visual chart tooltips remain mouse-oriented (numeric data is also in a screen-reader table). Optional VoiceOver/NVDA screen recordings can be attached for an RFP on request; the official AT evidence pack is the CI script suite below.

4. Known limits

We do not claim every historical merchant customization meets AA without exception. Theme skins that override contrast should keep using the built-in brand contrast helpers.

5. How we test

Playwright + axe-core (wcag2a / wcag2aa / wcag21 / wcag22aa) fails the build on critical, serious, and moderate findings across login shells, dashboards, POS, checkout, buyer, platform, supplier, and rider jobs. Keyboard, skip/Help, Escape dismiss, 320px and 400%-equivalent reflow, and official SR Scripts A/B/C (POS, checkout, rider jobs) run in CI. Visual baselines cover 375, 768, and 1280 widths. eslint-plugin-jsx-a11y interaction and ARIA rules fail the build.

6. Feedback

If you hit a barrier, email platform support from the contact details on /status or use Ask support / Help in the app. Include the page URL, the assistive technology you use, and what you expected to happen. We prioritise blockers on checkout, POS payment, and sign-in. For a signed ACR tailored to your RFP, contact platform support.

7. Updates

This statement was last reviewed on 12 October 2026. We refresh it when the accessibility scorecard or launch gates change.