Keyboard use
Primary workflows should be operable without a mouse, with logical focus order and visible keyboard focus.
Accessibility
RSearch Accessibility Program
RSearch is being developed toward WCAG 2.2 Level AA accessibility. We are publishing the target and current status before making a formal conformance claim.
Current status: structured review in progress. A formal Accessibility Conformance Report, including a VPAT-based report if required for procurement, has not yet been issued.
Engineering expectations
Names and instructions
Controls should use programmatic labels, meaningful headings, status messages, and instructions that do not rely only on visual position.
Color and contrast
Meaning should not depend on color alone. Text, controls, status indicators, and focus treatment are reviewed for sufficient contrast.
Responsive use
Core research workflows are designed for zoom and responsive layouts without forcing a single desktop configuration.
Errors and status
Validation errors, asynchronous status, and blocked actions should be understandable to assistive technology and should explain how to recover.
Complex research interfaces
SEM diagrams, tables, data-review surfaces, and other dense interfaces receive additional keyboard, screen-reader, zoom, and focus testing.
Conformance work before institutional claims
- Automated accessibility checks across representative routes and themes.
- Manual keyboard-only testing of the complete Research Pilot workflow.
- Screen-reader testing of navigation, forms, results, tables, dialogs, feedback, Data Readiness, and SEM alternatives.
- 200% and 400% zoom/reflow review where applicable.
- Contrast, focus appearance, target-size, error-identification, and accessible-authentication review against WCAG 2.2.
- Document exceptions and remediation dates.
- After evidence is complete, prepare an Accessibility Conformance Report for institutional review.
Important boundary
This page describes RSearch's accessibility target and program. It does not claim that every current screen conforms to every WCAG 2.2 Level AA success criterion. Known gaps should remain visible until they are tested and remediated.
If you encounter an accessibility barrier, use Send feedback from the affected page and describe what you were trying to do, what you expected, and what happened.