Accessibility

researchsecurity.ai is designed and built to meet WCAG 2.1 Level AA. Our institutional customers evaluate vendor accessibility as part of procurement; we treat conformance as a functional requirement of the site, not an afterthought.

What we build to

• Semantic HTML landmarks and a real heading hierarchy on every page.
• Visible keyboard focus states throughout, including a "Skip to content" link at the top of every page.
• Body-text contrast of at least 4.5:1 against background; large-text contrast at least 3:1.
• Alt text on informative images; decorative images marked as such and hidden from assistive technology.
• Forms with programmatic labels, clear error messaging, and non-color-only status indicators.
• No content dependent on hover or motion; no autoplay of media.
• Full functionality without JavaScript for the informational site (Astro static pages render server-side).

Known issues

None known at the time of this review. If you encounter a barrier, please tell us; we treat accessibility bugs the same way we treat security bugs (see below).

How to report a barrier

Use the contact form and mention "accessibility" in the message. Include the page URL, the assistive technology or browser you were using, and a short description of what did not work. We aim to acknowledge reports within one business day and to fix substantive issues promptly.

Accessibility conformance for procurement review

For institutions running a procurement accessibility review, we will complete your institution's accessibility questionnaire (for example, an accessibility conformance report in the VPAT format) as part of that review, the same posture as our HECVAT commitment. See the Trust Center for the broader security posture and design-partner review approach.

Assessment method

This site's accessibility is verified through automated testing (axe-core / Lighthouse accessibility scoring), manual keyboard-only navigation, screen-reader spot checks, and color-contrast verification against the WCAG 2.1 formula. Reviews are performed at launch and when significant page-level changes ship.