Accessibility
Survivors, staff and buyers who need to know how SafeConnect meets accessibility needs
Standard aimed for and how screens are tested
Web interfaces aim to meet WCAG 2.2 Level AA. This page states the target and the test approach. It is not a certification claim, and conformance can vary with program configuration.
Built in order
Real headings in order with one heading level one per page, labels on every field, alt text on every picture, visible focus and good contrast. Error messages say which field is missing and what to do next.
Tested by keyboard
Every action works by keyboard alone, in a logical order, with the focus always visible. Menu, modal and form controls can be reached and used without a mouse.
Tested with assistive technology
Screens are checked with a screen reader, with zoom and reflow, and with large text. Launch-blocking defects are fixed before pilot acceptance, and remaining items need written approval.
What a test pass covers
- Keyboard path through sign-in, case search, intake, visit check-in, secure messages, consent and reports, with no keyboard trap.
- Screen reader pass for headings, labels, tables, status messages and the quick-exit control on every survivor-facing page.
- Contrast, text resizing and reflow on a phone and on a computer, and a check at the largest text size before a template is published.
- Plain language review, so steps use short sentences, name the exact button or field, and state what the person will see when the step is done.
Custom templates can change a screen. Program administrators preview each template on a phone and at the largest text size, and safety and consent wording stays fixed so customization never removes a label, a warning or the quick exit.
Language access, low bandwidth and shared device support
Access is not only a screen setting. It includes the language, the connection and the device a person actually has.
Language access
- A language picker appears on the first screen, before any private detail is asked.
- Translation is offered for platform content, forms and text messages. Interpretation is offered for phone and video visits.
- Supported languages, interpreter access and any separate costs are stated by the program before a visit, with confidentiality safeguards on every request.
- Staff can request an interpreter from a message thread or a visit, and the choice is recorded on the case without appearing in notifications or page titles.
Low bandwidth and shared devices
- SafeConnect is a mobile-first web app. Core pages work on a phone or computer browser with no app install and no large download.
- Video visits offer an audio-only path, a phone path where the program supports it, and a waiting room that can be left and rejoined with the same link.
- On a shared device, a PIN or access code is required each session, sign-out clears the view, page titles stay neutral and notifications carry no detail.
A phone screen with large text and a language choice.
Feedback route without an account and known limits
You do not need an account to report a barrier. A plain report with enough detail helps the team reproduce and fix the problem.
How to report a barrier
Use the demo and contact form to send a report. Share only what is needed to find the problem. Do not send survivor details, case notes or message content.
Name the page
Give the page address and the screen or step where the problem happened, in the words on the screen.
Describe what happened
Say what you tried to do, what you expected and what you saw or heard instead.
Name your setup
Add the device, browser and assistive technology you used, and whether you used keyboard only, large text or a screen reader.
Reports are triaged by severity. Launch-blocking defects are fixed before pilot acceptance. The team replies through the contact route you gave and records the fix in the test list for that screen.
Known limits
- Conformance depends on configuration. A custom template, a third-party telephone or video tool, or an interpreter service that the program has not yet enabled can change the result for that screen.
- Interpreter availability, supported languages and any separate costs depend on the program list published before a visit. They are not promised for every language on every visit.
- Low-bandwidth and audio-only paths reduce what can be shown. If video will not work, the visit offers a phone or audio path instead of asking for a download.
- Accessibility test evidence and a conformance report can be requested through the demo form. Ask for the version and date that match the screens you will use.
Answers in plain words
Can I use SafeConnect with a keyboard only
Yes. Every screen is designed to work by keyboard, with visible focus and labels on every field. If you find a step that needs a mouse, report it with the page name and the step.
Can I use a screen reader or large text
Screens are tested with a screen reader and with zoom and large text. Headings are in order, pictures have alt text and tables have header labels so the order a screen reader reads matches the order on screen.
What if I share a device with other people
Use a PIN or access code each session, use quick exit to leave at once, and sign out when you finish. The view clears on sign-out and the next person must enter the code again. Notifications never show private detail.
What if my connection is slow
Core pages are text-first and do not need an app install. For a visit, choose the audio-only or phone path at check-in and choose language support before joining.
Try the steps on a phone
Read the safety guide, then ask for a demo with sample records.