Accessibility at Roster Flow
Roster Flow is used on a busy floor, on small phones, by people in a hurry. What has been done to make it usable by everyone, what is known not to work well yet, and how to tell us.
What has been built in
- Every form field has a visible label, and errors are written out in words rather than shown only in colour.
- Tables are real tables with row and column headings, including the calculator and the reports.
- Moving a shift on the roster has a keyboard path as well as drag and drop.
- Tabs move with the arrow keys, and the product pictures on the website carry a description a screen reader reads out.
- Nothing needs to be installed: the staff app runs in the phone’s own browser, with its own zoom and text size.
What is known not to work well yet
- Placing a venue on a map needs a pointer. The address search is the keyboard route, and it can be less precise.
- Shifts cannot be dragged on a phone. On a small screen a shift is moved by opening it and changing its times.
- A clock in photo needs a camera. A business that needs another route can switch photos off.
How it is checked
Changes are checked with a keyboard and at phone widths as they are made. A full manual test against the Web Content Accessibility Guidelines has not been published yet.
Tell us what gets in your way
If something in Roster Flow is hard to use, email hello@rosterflow.com.au and say what you were trying to do. It is treated as a fault, not a feature request.