Accessibility is not an edge case for IRIS. It's part of how we build.
Many of the organizations that use IRIS serve people with disabilities — including workforce development, education, nonprofit and human services organizations. Because of that, accessibility shapes how we design, test and improve the platform.
Our mission is to put ability to work — connecting people with disabilities to meaningful employment and supporting them long after they’re placed. IRIS gives us a behavioral science foundation we rely on to understand each person’s strengths and readiness, match them to the right role, and guide their development over time. It helps us place people with confidence and coach them toward lasting success.
Built for the people our customers serve.
Accessibility is a high priority for MIRRIM and for the ongoing development of the IRIS platform. Our customers serve a wide range of people, and we want IRIS to support their work responsibly.
We do not view accessibility as a one-time compliance exercise. IRIS continues to evolve, and accessibility is part of that continuing development process — reviewed with every new feature and improved as we receive feedback.
We use the Web Content Accessibility Guidelines (WCAG 2.0) as an important reference point in the design and development of IRIS.
Automated testing alone is not sufficient. Assistive technologies interact with software in ways automated tools cannot always evaluate — which is why screen-reader behavior, keyboard navigation and the real user experience matter to us.
How we build IRIS for accessibility
Significant development effort goes into making IRIS usable with assistive technologies and aligned with established web accessibility standards.
Screen-reader support
IRIS is developed and tested to work with screen readers, including JAWS. We add nonvisual information where needed so assistive technology can communicate what would otherwise only be apparent on screen — without changing the visual experience for others.
Accessible survey interactions
The IRIS assessment asks participants to interact with words, choices and interface elements. We ensure those interactions can be understood and navigated with assistive technology rather than relying solely on visual placement.
Color and contrast
Color is central to IRIS reports and data visualization. We select and review colors with WCAG 2.0 contrast requirements in mind, and work to ensure meaning is never communicated through color alone.
Keyboard accessibility
We continue to improve the ability to navigate IRIS without a mouse or touch interface — including keyboard navigation, focus states, interactive controls and a logical sequence of information.
Accessible labels and structure
We use semantic structure, labels and accessibility attributes so assistive technologies can interpret controls, forms, navigation and content. Where the visual interface is insufficient, we add nonvisual context.
Readable and responsive interfaces
IRIS supports different screen sizes and viewing conditions. We consider text readability, interface scaling, responsive layouts and use at increased browser zoom levels as part of our accessibility work.
Reports and results
Because IRIS presents behavioral information through scores, patterns, charts and written interpretation, we make those results understandable beyond their visual presentation for users relying on assistive technology.
Our objective is simple: the technology should help people understand and use their IRIS information — not create an unnecessary barrier to doing so.
When a customer or participant identifies an accessibility barrier, we want to know about it. That feedback helps us improve the experience not only for that individual, but for everyone who may encounter the same barrier.
Have accessibility questions about IRIS?
We're happy to discuss how IRIS works with assistive technology and your accessibility requirements.