Accessibility Statement·Last reviewed April 2026

Software that works for everyone.

OnePointe is committed to digital accessibility. Title IX coordinators, deans of students, conduct administrators, and the people they serve include individuals with a wide range of abilities. The Service must be usable by all of them.

At a glance
✓

WCAG 2.1 Level AA

Verified by independent audit (Deque Systems, January 2026).

✓

Keyboard & screen reader

Tested every release with NVDA, JAWS, VoiceOver, and TalkBack.

✓

Honest about gaps

Three known limitations are documented with timelines for remediation.

✓

1-day response SLA

Accessibility reports acknowledged within one business day.

1. Our standard

We design and build OnePointe to conform with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. Our most recent independent audit was conducted by Deque Systems in January 2026; the conformance report is available under NDA via your account manager.

Keyboard navigation

Every interactive element is reachable and operable using a keyboard alone. Focus order is logical. Visible focus indicators meet WCAG 2.1 contrast requirements.

Screen readers

Tested with NVDA, JAWS, and VoiceOver. Proper semantic markup, ARIA where appropriate, and meaningful labels for every form field, button, and live region.

Color contrast

Text contrast ratios meet or exceed WCAG AA: 4.5:1 for body text, 3:1 for large text and UI components. Color is never the sole means of conveying information.

Magnification & zoom

Layouts remain functional at 200% zoom and reflow correctly down to 320px viewport width. Text can be resized without loss of content or functionality.

Reduced motion

We honor prefers-reduced-motion system settings. Non-essential animations are minimized; critical motion is brief and never auto-playing.

Captioning & alt text

All product video and tutorial content is captioned. Images have meaningful alternative text. Decorative imagery is properly hidden from assistive technology.

2. How we work

A feature that isn't accessible isn't done. Five things happen before a single line of accessibility-affecting code ships.

  1. 01

    Design review

    Every new component is reviewed against WCAG criteria before development begins. Accessibility is part of the design system, not a checklist at the end.

  2. 02

    Automated testing

    Axe-core runs on every pull request. Builds fail when accessibility violations are introduced.

    Tooling Axe-core · GitHub Actions · Playwright
  3. 03

    Manual testing

    Major features are validated with screen readers, keyboard-only navigation, and reduced-motion settings before release.

  4. 04

    User research

    We work with users who rely on assistive technology to test new workflows. Their feedback directly shapes the product.

  5. 05

    VPAT documentation

    Voluntary Product Accessibility Templates are maintained for current and recent versions of the Service.

    Available On request, via your account manager

3. Known limitations

The most useful accessibility statement is an honest one. Three areas of the Service do not yet meet our internal standard. Each has a status and a date.

Interactive heat map

Q3 2026

The geographic map view in Reports relies on visual clustering that does not yet have a fully equivalent table-based alternative.

Planned fix Tabular companion view with the same data, sortable and screen-reader friendly.

Drag-and-drop reordering

Q2 2026

Some workflow configuration screens use drag-and-drop. Keyboard alternatives exist but are less efficient.

Planned fix Full parity for keyboard, switch, and voice users with up/down move buttons.

Legacy embedded reports

In progress

A small set of legacy report templates predate our current accessibility standards.

Status New report exports already meet WCAG 2.1 AA. Older templates are being remediated.

Please tell us if you encounter other issues. Your reports help us prioritize.

4. Compatible technology

The Service is designed to work with the following combinations. Others likely work but aren't formally tested every release.

Browsers Current + previous major
  • ChromeWindows · macOS · ChromeOS
  • EdgeWindows
  • SafarimacOS · iOS
  • FirefoxWindows · macOS
Screen readers Tested every release
  • NVDAWindows · Chrome & Firefox
  • JAWSWindows · Chrome & Edge
  • VoiceOvermacOS Safari · iOS
  • TalkBackAndroid
Other AT Voice, magnification, switch
  • Dragon NaturallySpeakingVoice control
  • ZoomText, MAGicScreen magnification
  • Switch accessKeyboard, switch interface

5. Get in touch

If you encounter an accessibility barrier in OnePointe, please reach out. We aim to acknowledge accessibility reports within one business day and to provide a remediation plan within five.

Email hello@onepointe.ai with a description of the issue, the page or feature affected, your assistive technology, and your browser. Screenshots or a recording are helpful but never required.

For general questions, see our Contact page.