Accessibility

How the site is built

• Structure. One heading at the top of each page, headings in order beneath it, landmarks for the masthead, main content, navigation and footer, and a breadcrumb on every page but the first.
• Keyboard. Every link, button, form field, disclosure and the chat are reachable in order with the Tab key and show a visible focus ring. The seasonal offer traps focus while open and closes on Escape; so does the chat.
• Size. Tap targets are at least 44 by 44 pixels; body text is at least 16 pixels; inputs are at least 16 pixels so phones do not zoom. Text can be enlarged to 200 percent without loss.
• Contrast. Body text on the linen ground, and light text on the dark footer, exceed a 4.5:1 contrast ratio; link underlines do not rely on colour alone.
• The drawings. The exhibits and the route are inline SVG with a role of image and a written description of what they show; wide drawings scroll inside their own container rather than the page. The severity marks — diamonds filled, half-filled, open and dashed — always sit beside their word (major, minor, observation, unsettled), never alone.
• Forms and status. Every field has a visible label; required fields are marked in the markup; status messages after sending are announced to assistive technology.
• Motion and sound. Nothing moves on its own, nothing plays, and nothing flashes.
• Without scripts. The self-inspection, the chat and the offer are enhancements; with scripts off, every word of content, every link and the email address remain.

Known limits

• The illustrated faces of the consultants and chat personas are decorative and are marked as such; they do not convey information that is not also in text.
• The live chat needs scripts to send messages; without them, the email address and the intake form reach the same desk.
• Fonts are loaded from Google Fonts; if they do not load, the site falls back to your system’s serif and sans-serif faces and remains readable.

Our reference, and what we do not claim

We use the Web Content Accessibility Guidelines as the reference for how this site is built and checked. We do not claim formal conformance to any level; we check against the guidelines, we fix what we find, and we fix what you report.

Tell us

If anything on this site gets in your way — a control you cannot reach, a drawing you cannot read, a contrast that is too low, a form that does not announce what it did — write to hello@aspenirb.com with the page and what happened. It will be read by a person and fixed, and you will hear back.