It works with
JavaScript off.

What we've built in

Works without JavaScript

• Every navigation link is a real anchor element with a real href.
• The slide-out main menu is driven by a checkbox and CSS, so it opens, closes and locks page scroll with scripting disabled.
• The full-screen quote overlay works the same way, and the form inside it posts to the server without client-side code.
• Sub-menus in the drawer are native disclosure elements, operable without script.
• Frequently asked questions expand and collapse natively.

JavaScript, when present, adds refinement: Escape-to-close, focus management, scroll reveals and the impact calculator. Nothing essential depends on it.

Keyboard

• A skip link is the first focusable element on every page.
• Visible focus indicators throughout, with a high-contrast outline.
• Menu and overlay toggles are reachable and operable by keyboard.
• Logical tab order following the visual reading order.

Screen readers and structure

• Semantic HTML: one h1 per page, ordered heading levels, real landmarks.
• Data tables use captions, scope attributes and proper header cells.
• All form fields have associated labels; errors are linked with aria-describedby.
• Submission results are announced through live regions.
• All meaningful graphics carry text alternatives; decorative ones are hidden.
• The scrolling ledger ticker is hidden from assistive tech and duplicated as text.

Motion and colour

• All animation respects prefers-reduced-motion, including the ticker, scroll reveals and the counter animations in the impact calculator.
• Body text and interface text target at least 4.5:1 contrast against their background.
• Colour is never the sole carrier of meaning — grades, states and errors carry text.

Responsive and zoom

• Layouts reflow to 320 px width without horizontal scrolling.
• Text scales to 200% without loss of content or function.
• Wide reference tables scroll horizontally inside their own container, not the page.
• Touch targets are sized for use with gloves on a yard.

Where we know we fall short

• Some of the reference tables are genuinely wide. They scroll within their container, which is workable but not ideal on a small screen.
• The impact calculator requires JavaScript. The underlying per-unit figures are published as plain text on the methodology page so the information is not gated.
• The interactive tote diagram conveys spatial relationships that a text alternative can only approximate. Every component is also described in full text beneath it.

Standard we're working to

WCAG 2.2 Level AA. We test with keyboard-only navigation, with JavaScript disabled, at 200% zoom, and with screen reader software. We are not formally certified and we would rather tell you our actual gaps than display a badge.

Reporting a problem

Email info@ibctotestexas.com with “Accessibility” in the subject. Tell us the page, what you were trying to do, and what happened. Include your browser and assistive technology if you know them.

We aim to acknowledge within two business days and to fix genuine barriers quickly. If something on this site is blocking you from getting a quote, write to us and we will simply handle the request by email instead — that route always works.