Skip to content
  • There are no suggestions because the search field is empty.

Accessibility Resources

unDrawPlus_1765326785354_bbrb8o

Our Commitment to You     

InfoReady is committed to providing equal access to information and services for all users of its platform. We aim to provide resources that meet accessibility standards and that align with legal requirements and industry best practices. Support and accommodation are available for users with disabilities. Review of and remediation of accessibility issues with the platform are part of our regular product development process. 

Compliance Status

InfoReady seeks to meet WCAG 2.2 AA criteria using VPAT version 2.5.

Processes for Accessibility

InfoReady prioritizes accessibility within the scope of the development of new features and enhancements. Within our product roadmap, we also prioritize addressing accessibility concerns for areas of the platform used by the greatest number of users (e.g., issues for applicants are prioritized over issues for administrators). We strive to address accessibility issues in areas of our platform as we work through release cycles along our product roadmap. 

Accessibility at InfoReady begins with the product design process. Our internal accessibility specialist is a member of our Design Team; this individual helps ensure that new features and enhancements address accessibility issues before development begins. Accessibility issues are included in requirements for development. 

The InfoReady Development Team is trained by our accessibility specialist at least annually. This includes training on computer testing tools to review their work, as well as guidance on manual testing. Individual developers are responsible for ensuring that their work meets accessibility requirements.  

Before each release, our accessibility specialist tests new features and enhancements through computer and manual testing to confirm requirements have been met. If issues are discovered, they are either remediated before release or scheduled for remediation during a future product release cycle. Updates are made to the VPAT with major releases. 

InfoReady has engaged an independent third-party vendor to audit the platform for its accessibility and provide recommendations on improvements. Future engagements will occur as needed based on industry trends and technology requirements.   

Our product roadmap does not touch all areas of the platform annually.  As such, our accessibility specialist performs a thorough review of accessibility across the platform annually using computer and manual testing. After this review, we dedicate time to remediation of issues that may not have been touched during the development of new features and enhancements. The VPAT is updated after this annual remediation. 

Product Usage Information for Users with Disabilities 

Through our accessibility process, InfoReady strives to support users who utilize assistive technologies. For best experience, it is recommended to use the latest browser versions of Chrome, Safari, or Edge.  The InfoReady Platform is designed to work with assistive technologies including speech recognition software, and assistive input devices.  

Client Responsibilities for Accessibility

Though the platform itself strives to meet WCAG 2.2 AA criteria using VPAT version 2.5 standards, complete adherence requires InfoReady clients to ensure the content they contribute to the platform is also accessible. This content includes, but is not limited to, graphical assets (including Alt Text language), uploaded supporting documentations, and content submitted via rich text data entry fields. Such content is not reviewed for accessibility by InfoReady personnel, software, or auditors. 

Providing Feedback

Questions or concerns about accessibility may be directed to the InfoReady Support Team


Accessibility is not an “exact science”; it evolves with changes in regulations, best practices, and technologies. We welcome feedback and engagement from our clients’ accessibility specialists to review our platform, processes, and training. Our clients are an essential partner in helping us work toward a platform accessible to all. 

VPAT

InfoReady's most recent assessment is available for download.

DOWNLOAD

Accessibility Roadmap

InfoReady's plans for product enhancements to meet or exceed accessibility requirements.

DOWNLOAD

FAQs

InfoReady follows both the WCAG 2.1 AA and the WCAG 2.2 AA criteria. WCAG 2.1 AA is the technical standard for state and local governments’ web content and mobile apps, while WCAG 2.2 AA is a newer standard that we support as a part of our ongoing commitment to accessibility.

WCAG, the Web Content Accessibility Guidelines, is a set of internationally recognized guidelines that say what is needed for web accessibility. WCAG is developed by the World Wide Web Consortium (W3C).

Title II of the ADA requires state and local governments to make sure that their services, programs, and activities are accessible to people with disabilities.

Most public entities, including state and local governments, must meet WCAG 2.1 Level AA standards by April 24, 2026.

There are a few, limited exceptions to content covered by the new requirement. Exceptions are listed below, but be aware that content needs to meet specific criteria to qualify for an exception.

For more information, visit https://www.ada.gov/resources/2024-03-08-web-rule/#summary-of-the-exceptions

  1. Archived web content

  2. Preexisting conventional electronic documents

  3. Content posted by a third party where the third party is not posting due to contractual, licensing, or other arrangements with a public entity

  4. Individualized documents that are password-protected

  5. Preexisting social media posts

For rich text fields:

  • Ensure sufficient color contrast between text and its background.

  • Include alternative text on meaningful images, or an empty alt text attribute on decorative images.

  • Only use tables for data, not for layout.

  • Use heading styles for structure, not for visual styling.

  • Don’t skip heading levels.

  • Use meaningful text for links.

In addition to the tips listed here, there are a lot of great resources with additional information, such as:

W3C Tutorials - 
https://www.w3.org/WAI/tutorials

Accessibility on the web - 
https://developer.mozilla.org/en-US/docs/Learn_web_development/Core/Accessibility

How to Meet WCAG (Quick Reference) - 
https://www.w3.org/WAI/WCAG22/quickref/?versions=2.1