Accessibility

Last updated: September 5, 2026

A roof is something everybody needs, so a roofing website has to work for everybody — someone using a screen reader, someone who can’t use a mouse, someone with low vision, someone on a phone in bright sun. We aim for the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, both on roofpropage.com and on every roofing website we build. We haven’t had an independent audit against that standard, so this page tells you what we’ve actually built rather than claiming a clean bill of health.

What every site we build already does

• A “Skip to main content” link. It’s the first thing a keyboard user reaches on every page, so they can jump straight past the menu to the page itself instead of tabbing through the navigation every time.
• Tap-to-call buttons big enough to hit. The call button in the header and the sticky bar at the bottom of a phone screen are at least 44×44 pixels — the size a shaky hand or a large thumb can actually land on. Every design uses the one shared call button, so that size is set in a single place, and an automated check stops a design from quietly rolling its own.
• A brand colour that stays readable. The one colour a roofer picks for their brand is checked every time a page is drawn — if it’s too pale for white text to sit on, we darken it until it isn’t, so a colour saved before we added the check is fixed on the visitor’s screen too. The forms you fill in on our own site have their border and placeholder colours pinned to the contrast minimums.
• Menus that behave like menus. Every site design we offer but one shares the same phone menu and call/text panel, and both are proper dialogs: keyboard focus stays inside while they’re open, Escape closes them, and a screen reader announces them as dialogs. The exception is the “Storm” design, which builds its own menu — it’s described below.
• Real page structure. One “main content” landmark per page that the skip link jumps to, and a visible label attached to every field of the quote form — so a screen reader reads out what each box is for instead of “edit text”.

Where we know we fall short

Three things are worth being straight about, because we’d rather you heard them from us than found them the hard way.

• One of our designs has a simpler phone menu. The “Storm” style’s menu closes when you press Escape and puts your keyboard focus back on the button that opened it, but unlike every other design it isn’t announced to a screen reader as a dialog, and keyboard focus isn’t held inside it while it’s open.
• Photo descriptions are generic. A roofer uploads their own job photos, and we can’t describe a picture we’ve never seen — so a photo saved without a caption gets a generic description (“Roofing project photo”). A screen reader will say a photo is there, but not what’s in it.
• We haven’t tested everything with every screen reader. No independent audit has been done, and we haven’t re-tested each of our designs against each screen reader.

If you hit any of these, the paragraph below is the fastest way to get it fixed.

Tell us about a barrier

If any part of roofpropage.com, or of a roofing website we host, is hard or impossible for you to use, email support@roofpropage.com. Tell us the web address of the page, what you were trying to do, and what happened — and, if it helps, what you use to browse (a screen reader, keyboard only, magnification). We’re a small team and answer these by hand: we aim to reply within five working days and to fix what we can. If something blocks you from getting a quote from a roofer, say so and we’ll treat it as urgent.

See also our Privacy Policy and Terms & Acceptable Use.