Accessibility
Bramblewood Regional Services Helpdesk runs on RequestCrew 1.34.0.
Everyone should be able to ask for help and follow along, whatever device or assistive technology they use. The helpdesk is built to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. That includes WCAG 2.1 AA, the standard U.S. state and local governments are held to under the ADA.
What that means here
- Everything works from the keyboard, with a visible focus outline, and a "Skip to main content" link at the top of each page. The one-key shortcuts (? for help, / to find a setting) can be turned off under Alerts and preferences.
- Pages have headings and landmarks a screen reader can jump between, and every form field has a label.
- When a form has a problem, the list of problems is announced, and each field says what's wrong with it.
- Text has enough contrast in light and dark mode, and color is never the only way something is shown.
- Pages fit a phone screen, still work zoomed to 400%, and nothing gets cut off when you widen the spacing between lines, letters, and words.
- Pictures in help articles can have a description for people who can't see them.
- Email from the helpdesk has a plain-text version.
How it's checked
The last full review was in October 2026, on version 1.24.1: an automated checker (axe) on every page as a requester, a tech, and an admin, in light and dark mode; keyboard-only walks through the main pages, checking that focus always shows and is never hidden; and checks at phone width and with wider text spacing.
Known gaps
- On screen, times like "3 hr ago" show the exact date and time only when you hover over them (screen readers hear the exact time). The ticket's printable view shows every exact time.
- Files people attach to tickets (photos, PDFs, spreadsheets) are only as accessible as the people who made them.
Tell us about a problem
If something in the helpdesk is hard to use with your setup, please tell your organization's IT team, and say which page and what happened. We'll get back to you and, where we can, fix it in the next version.