Qudini Accessibility Audit
Web Accessibility Remediation for Qudini website to make it conforms with the WCAG technical standards and comply with the ADA.
This Qudini accessibility audit and WCAG 2.1 AA remediation covered a queue-management and appointment-scheduling platform used by retailers and banks to manage customer visits.
Queue and booking tools are used by the public, often on the spot. If a customer using a screen reader or a keyboard cannot join a queue or book an appointment, they are turned away from a basic service everyone else can use.
Table of Contents
Why accessibility is critical for a booking platform
Software and SaaS companies are not exempt from accessibility expectations. In the United Kingdom the Equality Act 2010 requires services not to discriminate, and WCAG 2.1 Level AA is the standard, and for a product company it applies twice over — to the public marketing site and to the application itself. When the public books or queues through the tool, it must work for disabled customers too. A sign-up or demo form a screen-reader user cannot complete, or a product UI a keyboard user cannot operate, shuts paying customers and their own users out.
Scope and standard
Our Qudini accessibility audit assessed the platform against WCAG 2.1 Level AA, mapped to the Equality Act 2010, across the journeys that matter: the customer-facing queue and booking flows, confirmation and status screens, the staff dashboard, and navigation.
How we ran the Qudini accessibility audit
- Screen-reader testing with JAWS and NVDA on Windows, VoiceOver on macOS and iOS, and TalkBack on Android
- Automated audits with Deque axe, Google Lighthouse and WAVE
- Keyboard-only operation of every step, with attention to focus order and a clearly visible focus indicator
- Colour-contrast analysis, plus 400% zoom and reflow testing for low-vision users
What accessibility means on each part of the site
Because Qudini is a product-led site, our Qudini accessibility audit focused on the marketing site and the path into the product:
- Feature, solution and pricing pages need a clear heading structure and readable text, so a screen-reader user can evaluate the product.
- Sign-up, login and demo-request forms need programmatic labels, clear instructions and announced errors, so getting started never depends on sight or a mouse.
- Any interactive demo or product UI needs keyboard operability, managed focus and names and states that assistive technology can read.
- Documentation and support content needs correct heading levels, readable code or examples, and link names that make sense out of context.
- Navigation and content need visible focus, sufficient colour contrast and clean reflow at 400% zoom.
Outcome
This Qudini accessibility audit, combining manual and automated testing with remediation, brought the site into line with WCAG 2.1 AA expectations, so people using a screen reader or a keyboard can use it without barriers. Every fix was verified with assistive technology rather than assumed from an automated pass, so the result holds up in real use.