OCRS Accessibility Statement

OCRS aims to provide an equivalent experience for people who use screen readers, keyboard navigation, magnification, speech input or other assistive technology, and for people using the platform on small screens or with limited connectivity.

The product targets the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as its design and development standard. Targeting a standard is not the same as certifying conformance, and OCRS does not claim a conformance level on this page.

Pending legal/owner review: A formal conformance claim, or an Accessibility Conformance Report / VPAT, will be published only after an independent audit is completed and approved by the policy owner.

• A skip-to-main-content link on every public page.
• Semantic page structure with a single page heading and ordered heading levels.
• Labelled form controls, with validation errors programmatically associated with their field and announced to assistive technology.
• Dialogs that manage focus, trap it while open and return it on close.
• Keyboard operability for navigation, menus, dialogs and data controls, with visible focus styles.
• Text alternatives for meaningful images, and decorative images hidden from assistive technology.
• Colour and contrast handled through a single design token system rather than per-page colour values.
• A minimum interactive target size of 44 by 44 pixels and a minimum text size of 12 pixels.
• Responsive layouts verified without horizontal scrolling at mobile, tablet and desktop widths, with wide data tables placed in scrollable regions that remain keyboard reachable.

These behaviours are covered by automated accessibility and mobile checks that run against the live site as part of the OCRS release verification process.

• Automated testing cannot detect every barrier. Areas that depend on human judgement — including screen-reader task walkthroughs and cognitive load — have not been independently audited.
• Complex data views such as the occupancy map and large reporting tables convey information visually; equivalent information is available in tabular and exported form, but these views are harder to use at high magnification.
• Documents generated by OCRS, such as exported spreadsheets and PDF report artifacts, are not yet verified for accessibility.
• Third-party embedded content and email rendering are outside our direct control.

If you encounter a barrier, email admin@ocrsportal.org with the subject line "Accessibility" or use the contact form. Please include the page address, what you were trying to do, the assistive technology and browser you were using, and what happened. Reports are logged and triaged with product defects.

If you are not satisfied with the response, reply to the same address and ask for the issue to be escalated to the OCRS policy owner, who reviews unresolved accessibility reports. Users acting on behalf of a state agency may also raise the matter through their agency's own accessibility complaint process.

Pending legal/owner review: A named accessibility coordinator, a committed response timeline and any statutory complaint route (for example a state ADA or Section 508 process) require owner confirmation before being published.

If a barrier prevents you from completing a required occupancy or capacity submission, contact support so an authorized administrator can assist. Reporting obligations should never fail because of an accessibility barrier in the platform.