Accessibility.

The reference standard

We design and test this site against the Web Content Accessibility Guidelines 2.2 at Level AA. That is a reference we hold ourselves to, not a certificate we hold; where the site falls short of it we want to know, and the address at the foot of this sheet reaches the people who can fix it.

What is done

• Static, readable HTML. Every word of content is in the page before any script runs. The widgets — the tolerance check, the figure toggles, the chat, the seasonal offer — are enhancements on top of readable markup, not the only way to reach the content.
• One heading structure per page. Exactly one first-level heading, sections in order, and a breadcrumb line on every dedicated sheet.
• Keyboard throughout. Every button, link, form control, question row and the chat are reachable and operable by keyboard; focus is visible as a gold outline; the seasonal offer traps focus while open and returns it on close; Escape closes both the offer and the chat.
• Drawings with text. Every figure carries a description of what it shows and what it argues, so that the argument is available without the picture. Decorative marks are hidden from assistive technology.
• Size and contrast. Body text is 17 pixels on a warm ivory ground; text on the dark end-plate and footer is set to read at well above the minimum contrast; all controls are at least 44 pixels tall and all inputs at least 16 pixels, so phones do not zoom on focus.
• Mobile first. At phone widths nothing scrolls sideways except the wide technical drawings, which scroll inside their own frame; the menu collapses to a button that states whether it is open; the dock and chat stay clear of content.
• Motion kept small. Transitions are short hover shifts on buttons; there is no autoplaying motion, no parallax and no animation that cannot be ignored.
• Forms that say what happened. Each form reports sending, success and failure in a live region, and offers the chat or email as a second route when a request does not go through.

Known limits

• The technical drawings are wide by design and scroll horizontally on narrow screens; their descriptions carry the argument, but the detail of a dimension line is visual.
• The engraved portraits and the chat persona faces are illustrations; they are described, not transcribed.
• The live chat depends on scripts and a network connection; when either is unavailable, the intake sheet and email carry the same request.
• Typefaces load from Google Fonts; if they are blocked, the page renders in the system serif and sans fallbacks without loss of content.

Ask for another form

If any part of the site — a drawing, a table, the questions sheet, the pricing comparison — is difficult to use with the technology you rely on, write to hello@purdueirb.com and say which page and which part. We will send the content as plain text, as a document, or talk it through by the channel you prefer, and we will fix the page. The same address takes the free application review request in any form that suits you.

Related sheets

The privacy sheet describes what the forms and the chat collect; the terms describe the service itself; the sitemap lists every page on the site in one place.