Accessibility Statement

Describes RESOLVE’s current accessibility practices — an honest snapshot, not a compliance certification.

1. Our commitment

RESOLVE is used by agents at their desk and on the road, often on a phone between calls. Making the platform usable regardless of how someone navigates it — keyboard, screen reader, touch, or mouse — is treated as a real product requirement, not an afterthought. This statement describes what’s in place today.

2. Keyboard navigation

The platform is built to be operable from a keyboard: interactive elements follow a logical tab order, dialogs trap focus while open and return it on close, and a skip-to-content link lets keyboard users jump past repeated navigation on every page.

3. Semantic HTML & assistive technology

RESOLVE uses real HTML elements for their intended purpose — buttons, links, form labels, and headings — rather than generic elements styled to look interactive, so assistive technology can identify what’s on the page. ARIA labeling is applied to navigation, dialogs, and data tables. This coverage is stronger in some parts of the app than others today; extending it consistently across every screen is ongoing work, described in Section 6.

4. Color contrast

RESOLVE’s design system uses a defined set of color tokens rather than ad hoc colors, which makes contrast something that can be checked and fixed systematically. Every text token’s contrast ratio against every surface it can appear on has been computed directly from the underlying color values (not estimated) and meets WCAG 2.1 AA’s 4.5:1 minimum for normal text. This is one specific, verified piece of accessibility, not a claim that the platform meets WCAG 2.1 AA as a whole — see Section 6 for what’s still in progress.

5. Responsive design

Every screen in RESOLVE — including data tables, dialogs, and forms — is built to work on a phone or tablet browser, not just a desktop monitor. There is no separate “mobile app” with reduced functionality; it’s the same interface, responsive to the device.

6. Ongoing improvements

Accessibility coverage in RESOLVE today is real but not yet comprehensive — it’s stronger in navigation, dialogs, and newer screens than in some older ones. We do not currently claim conformance with a specific standard such as WCAG 2.1 AA, and we’re not going to claim it here until it’s actually true. Closing that gap consistently across the platform is active, ongoing work rather than a finished state.

7. Reporting an issue

If you use assistive technology and run into something in RESOLVE that doesn’t work the way it should, tell us directly — see Contact. Specific, reproducible reports (what page, what you were trying to do, what happened) are the fastest way to get something fixed.

Note: this statement describes RESOLVE’s accessibility practices as they exist today, honestly rather than aspirationally. It intentionally does not claim a WCAG conformance level or other certification that hasn’t been independently verified.