Everyone should be able to use this site. Here is the standard we hold it to, where it falls short today, and how to tell us about anything that gets in your way.
Last updated 19 September 2026
The standard we hold it to
We aim for the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. It is the baseline in the group's shared design rules, set once so each venture does not have to invent its own; each venture applies it on its own site and answers for it there.
This statement covers ibrothers.us only. Each venture runs its own site, and its own site is where to raise anything about it.
Where this site stands
We have not yet finished a full audit against WCAG 2.2 AA, so we do not claim to meet it. What follows is what we have checked, and what we know still falls short.
Scope: every public page of ibrothers.us. The staff sign-in and admin areas are not covered. We last checked the site on 19 September 2026, by reviewing its pages and code.
What already works
- Every form field has a label a screen reader announces, even where the design shows only a placeholder.
- Required fields on the contact form are marked, and a problem with a field is written beside that field and tied to it, so a screen reader reads the problem with the field rather than somewhere else on the page.
- Messages that confirm a form was sent, or explain why it was not, are announced as they appear.
- Images carry a text description. Purely decorative marks are hidden from screen readers, and the logo is announced once rather than twice.
- The page language is declared, so a screen reader pronounces the text correctly.
- Buttons and links shown only as an icon, such as the social links and the newsletter's send button, carry a text label saying what they do.
- A "Skip to content" link is the first thing a keyboard reaches on every page, so you can pass the menu and go straight to the page itself.
- The menu opens and closes with a real button that says whether the menu is open, closes with the Escape key, and cannot be reached by keyboard or screen reader while it is closed.
- Everything you can reach with a keyboard shows a clear focus ring, on light and dark backgrounds alike.
- Links that jump to a section of the page move your keyboard focus there too, so you carry on from the section you chose.
- If your device is set to reduce motion, the site respects it: nothing slides, scales or rotates as you scroll, pages change without a transition, and the moving strip of ventures stays still.
- The moving strip of ventures stops while your pointer or keyboard is on it.
What still falls short
- Unless your device asks for reduced motion, some content starts hidden and animates in as you scroll to it, so it can be briefly missing if you jump straight to a section.
- The main navigation sits behind a menu button on every screen size, large screens included, rather than being shown on the page.
- We have darkened the lighter text styles we found too faint, but have not yet measured the contrast of every one against its background.
- Links to other sites open in a new tab without saying so first.
- We have not yet tested the whole site with a keyboard alone or with a screen reader from start to finish.
How we keep this page honest
We review the site against the standard every quarter and update this page when we do. A problem comes off the list above only once it is fixed, and a new one goes on as soon as we find it.
A barrier on one of our sites is treated as a finding for the whole group, because the same fix usually belongs in all four.
Tell us about a barrier
If anything here is hard or impossible for you to use, write to hello@ibrothers.us. Say which page, what you were trying to do, and what got in the way. A person reads every message.
If you need something on this site in another form, such as plain text, ask and we will send it.
Version 1.1, 19 September 2026:
Added the scope, when the site was last checked, and how to report a barrier.
Did something on this site get in your way?
Tell us the page and what happened, and a person will answer.