Accessibility Policy

1. Policy Statement

Online Policing Solutions (OPS), the OPS Network, and all of its public safety partners are committed to ensuring that all OPS and agency managed community interfaces, web applications, and public-facing websites are accessible to all users, including individuals with disabilities.

OPS conforms with Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, consistent with the requirements of the Americans with Disabilities Act (ADA), Section 508 of the Rehabilitation Act (as applicable), and applicable U.S. Department of Justice (DOJ) digital accessibility enforcement guidance.

OPS recognizes that digital accessibility is a civil rights obligation and an essential component of equitable access to public safety information systems.

2. Scope

This policy applies to all OPS-managed digital assets, including but not limited to:

• Community policing portals and dashboards
• Public safety websites and informational portals
• Mobile and responsive web applications

3. Accessibility Standard

OPS targets conformance with:

• WCAG 2.1 Level AA

These standards ensure that content is:

• Perceivable - Information is presented in ways users can perceive
• Operable - Interface elements are usable via keyboard and assistive technologies
• Understandable - Content and navigation are clear and consistent
• Robust - Compatible with current and future assistive technologies

WCAG 2.1 Level AA compliance means a website is accessible to all users, including those using assistive technologies. The OPS platform meets these standards through the following:

• Full keyboard accessibility for all navigation and interactive elements
• Clear, visible, and consistent focus indicators on all clickable components
• Proper use of semantic HTML and ARIA labels for accurate screen reader support
• Sufficient color contrast ratios for text and visual elements
• Descriptive alt text for images and properly labeled form fields
• Content that reflows and remains usable at 200–400% zoom without horizontal scrolling
• Consistent and predictable navigation and layout structure
• Ability to skip repetitive content (e.g., “skip to main content” links)
• No reliance on color alone to convey important information

These measures align with WCAG 2.1 Level AA and support compliance with the Americans with Disabilities Act.

4. Keyboard Navigation & Input Accessibility

All OPS digital interfaces are designed to support full keyboard operability, including:

• Sequential navigation using Tab / Shift + Tab
• Activation of controls using Enter / Spacebar
• Logical focus order aligned with visual structure
• Visible focus indicators for all interactive elements
• Bypass mechanisms such as Skip to Content links where applicable

No functionality shall require a mouse or pointer device as the sole means of operation.

5. Screen Reader & Assistive Technology Support

OPS systems are developed using semantic HTML and, where appropriate, ARIA (Accessible Rich Internet Applications) attributes to ensure compatibility with screen readers and assistive technologies.

This includes:

• Proper labeling of form fields and controls
• Use of ARIA roles, states, and properties where native HTML is insufficient
• Logical heading structures and landmarks
• Descriptive link and button text
• Dynamic content updates communicated to assistive technologies when applicable

OPS acknowledges that assistive technology performance may vary by user environment and version.

6. Accessibility Statement & User Support

OPS provides an accessible means for users to request assistance or report barriers to access.

Users encountering accessibility issues may contact OPS or the supporting public safety agency through designated support channels to receive assistance or request alternative formats.

OPS is committed to responding to accessibility-related inquiries and making reasonable efforts to resolve identified issues in a timely manner.

7. Accessibility Testing & Maintenance

OPS follows a continuous improvement model for accessibility, including:

• Periodic audits against WCAG 2.1 AA standards
• Manual testing with keyboard navigation
• Screen reader compatibility testing (e.g., NVDA)
• User-reported issue tracking and remediation workflows

Accessibility is treated as part of the software development lifecycle, not a one-time compliance effort.

8. Third-Party Content & Integrations

OPS may integrate third-party services or content. While OPS strives to ensure accessibility across all integrations, third-party content outside of OPS’s direct control may not fully conform to WCAG 2.1 AA standards.

OPS will take reasonable steps to:

• Select accessible vendors where possible
• Encourage remediation from third-party providers
• Provide alternative access paths when feasible

9. Limitations & Disclaimer

Despite OPS’s commitment to accessibility, a user may find something that they believe does not yet fully conform to WCAG 2.1 AA due to ongoing development, system updates, or third-party dependencies.

OPS is always actively working to identify and remediate such issues as part of its continuous compliance program.

OPS and all its partner agencies value all users and members of our disabled community and work hard to accommodate in all ways possible. As part of this commitment, OPS will remediate and correct any verifiable issue brought to its attention within 48 hours.

10. Enforcement Alignment

This policy is designed to align with:

• Americans with Disabilities Act (ADA), Title II and III principles
• U.S. Department of Justice digital accessibility enforcement guidance
• Section 508 (where applicable for public sector integrations)
• WCAG 2.1 Level AA success criteria

OPS acknowledges increasing federal enforcement focus on digital accessibility for public-facing services, particularly in public safety and government-adjacent platforms.

11. Contact for Accessibility Issues

For accessibility assistance, feedback, or accommodation requests, users may contact:

OPS will make reasonable efforts to respond promptly and resolve barriers to access.