Built to be used by everybody.

Every page is built from real HTML elements rather than styled divs, which is what makes a screen reader useful instead of exhausting:

• Genuine landmark regions — a banner, navigation, main, and footer — so you can jump straight to content
• One level-one heading per page, with every other heading nested in order beneath it
• A skip-to-content link as the first thing you reach with the Tab key
• Named navigation regions, so “Primary”, “Legal”, and “Service Areas” are distinguishable rather than three unlabelled menus
• The page language declared as English, so the correct pronunciation rules apply
• Our postal address marked up as an address, phone numbers as tel: links, and email as a mailto: link
• FAQ answers built from the browser’s own expandable element, so they announce their open and closed state without us scripting it

Every link, button, and form control on this site can be reached and operated with a keyboard alone, and focus order follows the visual order of the page.

Focus is always visible. A focused control gets a two-pixel blue outline set three pixels clear of its edge, and that indicator has not been removed or dimmed anywhere on the site. That blue against our paper background measures roughly 5.7:1, comfortably above the 3:1 that the standard asks of a focus indicator.

The mobile menu opens from a button that reports whether it is expanded, and while the menu is closed its links are properly hidden from the keyboard rather than sitting invisible in the tab order waiting to trap you.

The contact form — the only form on the site — is labelled properly throughout. Every field has a real label attached to it, required fields are announced as required rather than only marked with an orange asterisk, each error message is tied to the field it belongs to, and the summary that appears when a submission fails announces itself instead of waiting to be found.

If your operating system is set to reduce motion, this site honours it globally — not on some elements, on all of them:

• Scroll-reveal animations resolve immediately instead of fading and sliding in
• The scrolling band of service names stops moving
• The radar sweep on the service-area map stops
• The photograph sequence in the home-page hero stops advancing on its own, and the slow zoom on each frame is switched off
• Background video is never downloaded at all — you get the still photograph instead

None of it is load-bearing. The home-page sequence is plain photography rather than video, it is hidden from assistive technology, and it carries real controls — previous, next, and a jump straight to any frame — so you can move through it at your own pace. Background video is muted, carries no audio you need to hear, is hidden from assistive technology too, and always sits behind a still image that paints first. If any of it fails to load, nothing is lost.

Nothing on this site flashes.

Every photograph on this site is our own work, and every one of them carries alt text written for that specific image — “aerial drone view of a completed asphalt shingle roof replacement on a two-storey Northern Indiana home”, not “roof”.

Purely decorative images carry empty alt text so a screen reader skips past them instead of reading out a filename. Icons are hidden from assistive technology, and any control that is an icon alone carries a label describing what it does.

We checked our palette numerically rather than by eye. Against the light paper background this site uses, body copy measures about 5.5:1, emphasised text about 10.1:1, headings about 16.2:1, and the blue accent about 5.7:1 — all above the 4.5:1 that Level AA requires for text. The exceptions are small secondary labels, and they are listed under known limitations below rather than left for you to find.

Where a control is in an active state, it is marked by more than colour: an underline under the current navigation item, a bar above the current tab, an icon that rotates when an FAQ opens.

Text scales. Type sizes are fluid rather than fixed, the page can be zoomed to 200% without content being cut off or overlapping, and we have not locked pinch-zoom on mobile the way a lot of sites quietly do.

The controls you actually need on a phone are sized for a thumb: primary buttons are roughly 52 pixels tall, the fixed navigation bar at the bottom of the screen is 70 pixels tall with five wide slots, and the menu toggle and social link are 44 pixels square.

That bottom bar is the only element fixed to the screen, and the page reserves space for it so it can never cover the footer or hide a phone number underneath itself.

The site is rendered on the server. With JavaScript switched off, or still loading, or blocked by a corporate network, you still get every page, every photograph, every phone number, and FAQ accordions that open and close — because they are built from the browser’s native expandable element rather than scripted.

Content is deliberately visible by default and only animated once the page has loaded, so a script that fails can never leave you looking at a blank page. There is even a timer that reveals everything anyway if the animation code misbehaves.

Honest scope: this is our own testing, not a specialist audit.

• Walking every page with the keyboard only, checking focus order and that nothing traps focus
• Browser zoom to 200%, checking for clipped or overlapping content
• Running the site with reduced-motion enabled and with JavaScript disabled
• Calculating the contrast ratio of every text colour in the palette against every background it sits on, rather than guessing

These are real and we are not going to bury them:

• Some small secondary text is set in a muted grey that measures roughly 2:1 against its background — well below AA. It affects the breadcrumb trail at the top of a page, the copyright line in the footer, and a handful of small labels such as the “Tap to call” line under our phone number and the state tags beside our Michigan towns. It is first on the fix list, and it is a colour change rather than a rebuild.
• The dense link lists in the footer sit closer together than our 44-pixel touch-target goal. They are keyboard-operable and they are tappable, but they are tighter than we want them.
• On desktop, the Services menu expands on hover, so a keyboard user does not get the dropdown. Nothing is unreachable — every link inside it also appears on the Services page and in the footer — but the menu itself should open on focus and does not yet.
• The mobile menu does not close when you press Escape, and it does not return focus to the button that opened it.
• We have not had an independent accessibility audit, and we have not yet tested this site with people who use assistive technology every day.
• Sites we link to — our Facebook page, for one — are outside our control and outside this statement.

If any part of this site stopped you doing what you came to do, we want to hear about it, and we would rather hear it bluntly than not at all. It is the only way most of these things get found.

What helps us fix it quickly:

• The address of the page, or a description of where you were
• What you were trying to do when it went wrong
• The browser and device you were using
• Any assistive technology involved — screen reader, magnifier, voice control, switch access

Call (574) 334-6597 or email info@underdog-roofing.net. We reply to accessibility reports on the same footing as any other enquiry — within one business day. If the fix itself is not quick, we will tell you what we are doing about it and roughly when it will land, rather than going quiet.

None of this should stand between you and a roof. If any part of this site is unusable for you, call us and we will do the entire thing by voice: take the details, book the inspection, describe what we found on the roof, and read the estimate out line by line.

We can send a plain-text version of any page or estimate by email, we can post paperwork to you, and we can walk the property with you in person and explain what we are looking at.

The website is a convenience. It has never been the only way to hire us.

This statement was last reviewed on the date shown at the top of the page, and it describes the site as it stands today rather than as we would like it to be.

When we fix something on the limitations list, it comes off the list. When we find a new problem, it goes on. A statement that only ever grows more flattering is not worth reading.