Accessibility

What the site does

• Reads without scripts. Every word of content is in the HTML. The two-board checker, the chat, the seasonal offer and the forms are enhancements on top of readable pages; the pages are complete without them.
• Readable type. Body text is 17 pixels on a high-contrast ink on ivory; nothing interactive is smaller than 16 pixels; inputs are 16 pixels or larger so phones do not zoom on focus. Headings are real headings in order, one top-level heading per page.
• Room to tap. Links in the masthead and footer, buttons, form controls, the chat launcher and the dock buttons are at least 44 pixels tall; the burger menu opens a list of 48-pixel rows.
• Keyboard. Everything that can be clicked can be reached and operated with a keyboard. Focus is visible as a 3-pixel ring in the site’s colours. The seasonal offer traps focus while open, returns it where it was on close, and closes on Escape; so does the chat and the narrow-screen menu.
• Drawings that speak. The two-rail drawings carry a spoken label that says in words what the picture says in lines; decorative drawings are hidden from assistive technology. The illustrated portraits are labelled by name.
• Forms that explain themselves. Every field has a visible label; required fields are marked as required; status messages after sending are announced through a live region, and errors say what to try next.
• Motion and distraction. No autoplay, no carousels, no animation beyond the burger’s three bars. The seasonal offer appears once per session at most and never immediately.
• Narrow screens. At 375 pixels wide the page does not scroll sideways; wide drawings and tables scroll inside their own container instead. Sticky elements do not cover content.
• No trackers. No third-party scripts, which also means nothing on the page competes with your own tools.

What we know is imperfect

• The illustrated portraits and the chat persona faces are decorative likenesses; they are labelled, but they do not convey information beyond the name, which is also in text.
• The two-board checker’s questions are rendered by script after the page loads; the five questions and the three verdicts are also written out in plain text on how it works for readers without scripts.
• We test with keyboard, a narrow viewport and a screen reader on a regular cadence, not on every change. If we have missed something, it is a fault, not a policy.

Reporting a barrier

Email hello@chamberlainirb.com with the page, what you were trying to do, and what got in the way; the browser or assistive technology you were using helps but is not required. We reply from the desk and fix the site itself. If the barrier stops you from booking the free application review, say so in the email and we will take the review by email instead.

The standard

The site is written against WCAG 2.2 level AA as its working reference. We describe it as built toward that standard rather than claiming formal conformance, because conformance is a tested state and this page is a commitment; the list above is what we check.

The privacy and terms pages sit alongside this one.