Accessibility

Standards We Target

We test against the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA and WCAG 2.2 Level AA standards. These guidelines cover a wide range of recommendations for making web content more accessible, including requirements for text alternatives, keyboard navigation, color contrast, and content structure.

How We Test

We run automated accessibility checks on every public page of the site as part of our continuous testing process:

• •Automated testing using axe-core, an industry-standard accessibility testing engine
• •Tests run across all public routes (currently 334 public pages) on every build
• •Both desktop and mobile viewport sizes are tested
• •We check for critical, serious, and moderate violations against WCAG 2.1 AA and WCAG 2.2 AA rulesets
• •These automated checks are part of a suite of over 1,500 end-to-end tests

Known Limitations

Automated testing identifies many accessibility issues but cannot catch everything. Some aspects of accessibility, such as the meaningfulness of alternative text or the clarity of content organization, require human judgment. We work to address issues as we discover them.

Specific automated-test gaps we are aware of: placeholder text contrast inside form fields cannot be inspected by axe-core (the testing engine we use). We darkened our placeholder color token in April 2026 to a value that meets WCAG AA on white backgrounds, but the test suite cannot verify this automatically. If you encounter a placeholder that is hard to read, please report it using the contact below.

Form input label verification: April 6, 2026. We manually audited all 9 public-facing form input components for visible or screen-reader-accessible label elements (WCAG 2.1 AA Success Criterion 1.3.1 and 3.3.2). Two search inputs were updated to include explicit aria-label attributes. All other form inputs already had visible label elements above the field, with placeholder text serving as supplemental example only.

Report an Issue

If you encounter an accessibility barrier on any page, we want to know about it. Please contact us:

• •Email: hello@inventoryready.com
• •Subject line: “Accessibility Issue”

When reporting an issue, it helps to include the page URL, a description of the problem, and the assistive technology you were using (if applicable). We aim to acknowledge reports within two business days and resolve issues as promptly as possible.