Accessibility

Last updated August 2, 2026

INRBLOOM builds systems other people have to use. A website that locks someone out fails on its own terms, so access here is part of the build rather than a pass at the end of it.

Where we stand

This site is built to meet WCAG 2.1 Level AA. Based on our own testing it substantially conforms to that standard. We say substantially, and not simply that it conforms, for one honest reason: this is a self-assessment by the team that built the site, not an audit by an independent third party. We would rather tell you that than imply a certificate we do not hold.

What is actually in place

• Keyboard access. Every interactive element can be reached and operated with a keyboard, and a skip link lets you jump straight past the navigation to the main content.
• Visible focus. Whatever you are on is clearly marked, so keyboard users are never guessing where they are.
• Reduced motion. This site has animation in it. If your system asks for reduced motion, the animation is cut back accordingly, everywhere it appears.
• Contrast. Text and interface colors are chosen to meet AA contrast, and the palette was checked rather than eyeballed.
• Forms that explain themselves. Fields carry real labels, and validation messages are announced to screen readers instead of only turning something red.
• Structure and language. Pages use a proper heading order and declare their language, so screen readers and translation tools handle them correctly.
• Text that scales. Type is set in relative units and the layout holds together when you zoom or enlarge text.

What we know is not finished

Publishing a list of gaps is more useful than publishing a claim, so here is ours:

• No independent accessibility audit has been carried out, and we have not published a VPAT.
• Our testing has been automated checks plus manual keyboard and screen reader passes. It is not a substitute for testing with a wide range of assistive technology and real users, which we intend to do.
• Essays are added over time. Each is checked as it is published, but new content is exactly where problems tend to appear first.
• Form submissions are handled by Netlify, and we do not control the accessibility of any page it serves on its own.

If something blocks you

Tell us and we will fix it. Email Contact@inrbloom.com with the page you were on, what you were trying to do, and what got in the way. If it helps, mention the browser or assistive technology you use.

We aim to reply within five business days. If a fix will take longer than that, we will say so and give you a straight answer about when, rather than leaving the message unanswered.

If you need something on this site in another format, ask. We will get it to you in a form you can use.