A website that works for readers who navigate differently.

We want everyone to be able to read about our work, use the readiness scorecard, and reach us. This statement describes the standard we build to, how we test against it, what we know isn't perfect yet, and how to tell us when something doesn't work for you.

A pair of reading glasses rests on an open book; through the lenses the leaf-and-berry pattern on the pages looks sharp and enlarged.

Statement dated November 1, 2026. It applies to every page at bennerhouse.com.

Our target

We design and build this site to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. We treat any failure against that standard as a defect to fix, not a matter of taste. This statement describes our own testing; it is not a claim of formal conformance by an outside auditor.

How the site is built

  • Pages use semantic HTML with landmarks, a logical heading order, and a "Skip to main content" link as the first stop for keyboard users.
  • Every form field has a visible label. Errors are described in text next to the field, never by color alone, and the form reports its status in a live region.
  • Text and interface colors are chosen to meet at least a 4.5:1 contrast ratio, and body text aims for 7:1.
  • Every interactive element shows a visible focus indicator, and nothing on the site requires a mouse, a hover, or a gesture.
  • Layouts reflow to a single column down to 320 CSS pixels wide without horizontal scrolling, apart from data tables and code samples, which scroll within their own region.
  • Animation is decoration only. When your system asks for reduced motion, animations are turned off and the final state is shown.
  • The boxed labels drawn around phrases in headings are visual decoration. The heading text reads normally without them.
  • Every page, script, and font is served from our own domain, so nothing on a page depends on a third-party service loading correctly.

How we test

Before each release, we test every page on the site, including articles, as follows:

  • Automated checks. The axe-core accessibility engine runs against every page at four viewport widths: 320, 375, 768, and 1440 pixels, checking the WCAG 2.0, 2.1, and 2.2 A and AA rules.
  • Keyboard only. We tab through each page at desktop and phone widths and confirm that every interactive element can be reached in a logical order and shows a visible focus indicator.
  • Forced colors. Each page is checked in forced-colors mode, the setting Windows High Contrast uses, to confirm that content, borders, and focus indicators stay visible.
  • Reduced motion. Each page is checked with the reduced-motion preference turned on.
  • Zoom and text spacing. We check pages at 200% browser zoom, and with the text-spacing overrides from WCAG success criterion 1.4.12 applied, to confirm that no text is clipped or overlaps.

We have not yet carried out a structured round of testing with screen readers. That means there may be problems for screen-reader users that our other checks don't catch, and we especially want to hear about them.

Known limitations

  • Illustrations. Each page carries an illustration. Those that add meaning have short, literal alt text; those that are purely decorative are marked so assistive technology skips them. The illustrations contain no text you would need to read.
  • The readiness scorecard and the refinery demonstration. Both are progressive enhancements that need JavaScript. Without it, the scorecard's questions and answers still appear on the page and the text below them explains how every score is calculated, so you can score yourself by hand; the refinery demonstration on the home page shows its finished examples as text. If you'd prefer, we're glad to walk through the scorecard with you by email or phone.
  • Directions. The contact page gives our street address as text, with a link to directions in Google Maps. We don't control the accessibility of Google's site.
  • Linked sources. Articles link to regulators, standards bodies, and research papers. Some of those documents, especially PDFs, may not be accessible, and we don't control them. If you need one in another format, ask and we'll help.

Tell us about a barrier

If something on this site doesn't work for you, please tell us what page you were on, what you were trying to do, and what happened. Include the browser and any assistive technology you use, if you're comfortable sharing that.

  • Email: hello@bennerhouse.com, with "Accessibility" in the subject line
  • Phone: (601) 954-9979, Monday to Friday, 8:00 a.m. to 5:30 p.m. Central Time
  • The contact form, choosing "Something else" as the topic

We reply within two business days. While we fix the problem, we'll get you the information or service you need another way: by email, by phone, or in an accessible document.

Compatibility

The site is designed to work in current versions of Chrome, Edge, Firefox, and Safari on desktop and mobile, with or without assistive technology. It uses standard HTML, CSS, and a small amount of JavaScript; core content doesn't depend on JavaScript.

Review

We review this statement whenever the site changes significantly, and at least once a year. This version was prepared on November 1, 2026.