Headings in order
Page titles, section titles, and card titles follow in order, so a screen reader can move by heading and a sighted reader can scan the page in the same order.
Accessibility
How ChauffeurDesk works for everyone
Screens support keyboard use, screen readers, labels, headings, contrast, and phone use. This page states what is supported and how to report a barrier.
What is supported
Headings, labels, and readable text on every screen
Each page and app screen uses real headings in order, with one h1 per page. Field labels, button names, and status names use the same plain words as the guides.
Labels on every field
Every form field has a visible label. Booking, daily check, and service forms state what to enter and what happens after saving.
Alt text on pictures
Every picture carries alt text that states what the picture shows. Decorative icons are hidden from assistive tools.
Keyboard use
Menus, tabs, tables, and dialogs work by keyboard. Focus is visible, and a skip link moves straight to the main content.
Contrast and text size
Text and controls use good contrast against their background. Screens work with browser zoom and larger text, and status is stated in words, not by color alone.
Phone layouts
Tables stack on a small screen, forms ask one thing at a time, and the chauffeur status button stays large and reachable with one thumb.
Phone and desktop
One record set, two layouts
The same booking, schedule, and vehicle records appear on a computer and on a phone. The phone layout keeps call time first and the next status step at the top.
- Chauffeur phone view shows only own runs, with call time, pickup, customer, requests, and flight on each card.
- Daily check lists cleaning items, then safety items, with pass or fail stated in words for each item.
- Empty states say what to do first, such as opening a booking or completing a check, instead of showing a blank page.
What to try on a phone
Open My day, read the next run card, and tap the status button to move to the next step. Open the daily check, work through each item, and confirm the vehicle result before the first call time.
On a desktop, open the schedule and read a run row from call time through status and flags. Each flag states its reason in words, such as no chauffeur, chauffeur off, double booked, or vehicle not ready.
Report a barrier
Tell us what happened, and we will fix it
Note the page name and what happened, then contact the company. Include the device and browser you used, if you can.
Note the page and step
Write the page name, such as the booking detail or the daily check, and the step where the barrier appeared.
Describe what happened
State what you expected, what you heard or saw instead, and whether keyboard, screen reader, zoom, or touch was involved.
Contact the company
Send the note through Request a demo or ask a question on any guide. Staff record the report and reply with the next step.
Does the app work with a screen reader
Headings, labels, table headers, and status text are written for screen reader use. Lists and tables state their purpose before the rows, and buttons state their action in words.
Can I use the whole app by keyboard alone
Yes. Navigation, forms, tables, tabs, and dialogs can be reached and operated by keyboard, with visible focus at each step. The skip link moves to the main content first.
What if a guide does not match the screen
Note the guide name and the screen name, and send both through the contact form. Guides are updated when a screen changes, and a guide that no longer matches is corrected or retired.
Try the phone view and the guides
Read how to confirm a run, complete the daily check, and approve a message, then request a demo for a walkthrough.