About

Accessibility

The site is meant to work for everyone, with a keyboard, a screen reader or a magnifier as well as with a mouse. Here is what we do, and how to tell us when it falls short.

What we build for

  • Keyboard. Every control on the site, including the calculators, the unit toggle and the menus, can be reached and operated with the keyboard alone. A “Skip to content” link is the first focusable item on each page. Focus is always visible.
  • Screen readers. Form fields have labels, hints and error messages linked to them; results are announced when they change; tables have captions and row headers; icons are decorative and hidden from assistive technology.
  • Zoom and text size. Pages work at 400% zoom and with text enlarged in the browser. Layouts reflow to a single column on narrow screens; nothing requires horizontal scrolling except wide tables, which scroll within their own box.
  • Colour and contrast. Text meets WCAG 2.2 AA contrast ratios against its background, and no information is conveyed by colour alone.
  • Motion. The site uses almost no animation. Where a page scrolls to a result, it respects the operating system’s reduced-motion setting.
  • Without JavaScript. The calculators need JavaScript to run, but every calculator page prints its formula and worked examples so the calculation can be done by hand, and nothing else on the site depends on scripts.

Standard

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. Pages are checked with automated tools and by hand with keyboard-only navigation and a screen reader before they are published.

Known limitations

Advertisements are served by Google and are inside their own frames; we cannot control their accessibility beyond labelling the advertisement area. Printed results use the browser’s print function, whose dialog is outside our control.

Tell us

If something on the site does not work for you, write to contact@roofingscalculator.com or use the contact form, and say which page and which assistive technology you were using. Accessibility reports are treated as errors and fixed as a priority.