Zipflow is committed to making our service accessible to as many people as possible. We want tradespeople of all abilities to be able to generate quotes, manage jobs and invoice customers without barriers.
This statement covers the Zipflow web application at zipflow.co.uk. It was written in May 2026 and reflects our current state honestly — including where we still have work to do.
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. We are not fully compliant yet, but we are actively working towards it.
check_circle
What works well
check_circle
Keyboard navigationAll core flows — creating quotes, viewing jobs, sending links — can be completed using a keyboard alone.
check_circle
Form labelsAll form fields have visible labels. Key action buttons have accessible names via aria-label attributes.
check_circle
Images and iconsAll meaningful images have descriptive alt text. Decorative icons are hidden from screen readers.
check_circle
Colour contrastOur primary gold on dark background (#dab924 on #0a0a0a) meets WCAG AA contrast requirements for large text.
check_circle
Responsive designThe app works at all zoom levels up to 400% and on all screen sizes from mobile to desktop.
check_circle
Voice inputThe core quoting flow supports voice input as an alternative to typing, which benefits users with motor difficulties.
warning
Known limitations
We are aware of the following accessibility gaps and are working to address them:
warning
Form label associationSome labels are not programmatically linked to their inputs via htmlFor/id attributes. Screen readers may not correctly announce which label belongs to which field.
warning
Focus management in modalsWhen overlay screens open, focus is not always moved to the modal content or trapped within it, which can disorient keyboard and screen reader users.
warning
Calendar accessibilityThe schedule calendar does not have full ARIA grid markup. Day cells lack descriptive labels for screen reader users.
warning
Status colour relianceIn some places (job status badges, pipeline alerts) colour is the primary way information is conveyed, with no secondary indicator for colour-blind users.
warning
No skip navigation linkThere is currently no "skip to main content" link, which means keyboard users must tab through the navigation on every page.
warning
Live region announcementsDynamic content changes (new quote generated, status updated) are not always announced to screen readers via aria-live regions.
schedule
What we are working on
build
Linking all form labels to inputs with correct htmlFor/id attributes
build
Adding focus trapping and aria-modal to all overlay screens
build
Adding aria-live regions for dynamic content updates
build
Adding text labels alongside status colour indicators
build
Adding a skip navigation link to all pages
build
Full WCAG 2.1 AA audit planned before wider public launch
support_agent
Technical information
Zipflow is built using React and relies on standard HTML5 elements and ARIA attributes where appropriate. The application is delivered as a Progressive Web App (PWA) and can be installed on iOS and Android home screens.
The following technologies are used and their accessibility support relied upon:
HTML5 semantic elements
ARIA roles and attributes where native semantics are insufficient
CSS for visual presentation only — no CSS used to convey meaning
Google Material Icons (font-based, hidden from screen readers with aria-hidden where decorative)
mail
Contact us about accessibility
If you experience any accessibility barriers when using Zipflow, or if you need information in a different format, please contact us:
Zipflow is currently in beta and accessibility improvements are part of our active development roadmap. We have been honest in this statement about what works and what doesn’t, rather than overclaiming compliance we haven’t yet achieved. We believe this is the right approach and we are committed to continuous improvement. If something doesn’t work for you, please tell us — your feedback directly shapes what we fix next.
This statement was prepared in May 2026 and will be reviewed and updated as improvements are made.