Last updated: August 6, 2026
Our commitment
Heather Window & Door serves homeowners and businesses across the Dallas–Fort Worth area. Anyone who needs a garage door repaired, installed or replaced should be able to use this website to reach us — with a screen reader, with a keyboard only, with a screen magnifier, with voice control, with a switch device, or on a phone held in one hand.
We treat that as part of doing the job properly, not as an add-on. When something on this site gets in your way, we want to hear about it and fix it.
The standard we work to
We build and test this website against the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, which includes the earlier 2.0 and 2.1 success criteria. WCAG is the international standard for making web content usable by people with a wide range of disabilities, and Level AA is the level most commonly referenced in U.S. accessibility law and policy.
WCAG 2.2 Level AA is our target. It is what we design and code toward, and what we measure ourselves against when we review a page.
Conformance status
This site is partially conformant with WCAG 2.2 Level AA. "Partially conformant" means most of the site meets the standard, but we cannot yet claim that every page and every component does.
We want to be exact about what that is based on, because accessibility statements are often written to sound more certain than the work behind them.
What has been done
- Accessibility was designed into the site's shared components and stylesheet from the start, rather than retrofitted.
- Automated structural checks run on every build, and the build fails if they find a problem.
- Pages have been reviewed manually by our team using a keyboard and at multiple screen sizes.
What has not been done
- No independent third-party accessibility audit has been carried out. No outside firm has evaluated this site, and no certification, seal or letter of conformance exists for it.
- No testing with assistive technology has been completed. We have not yet run structured test passes with screen readers such as NVDA, JAWS, VoiceOver or TalkBack, or with voice-control and switch-access software.
- No testing on physical devices with real users. Our responsive checks have been done through browser tooling and automated rules, not by disabled people using their own hardware and their own settings.
Until that testing is finished, our position is a working commitment rather than a claim of full conformance. We would rather tell you where the gap is than paper over it.
Measures we have actually taken
These are specific things implemented in this website today, not general intentions.
Structure and navigation
- Semantic landmarks on every page — a real header, navigation, main and footer — so screen reader users can jump between regions instead of reading top to bottom.
- A "Skip to content" link as the first focusable item on every page, hidden until you tab to it, then fully visible.
- One H1 per page and headings in correct order, with no skipped levels and no empty headings. This is enforced by the build, not left to discipline.
- Descriptive link text and internal links that resolve. Every internal link is verified at build time, so navigation does not dead-end on a missing page.
Keyboard and focus
- All interactive elements are reachable and operable by keyboard — links, buttons, form fields, the service selector, and the accordions and disclosure sections.
- A high-visibility focus indicator on every focusable element: a solid outline with an offset and a contrasting ring, so the focus ring stays visible against both light and dark backgrounds.
Color, contrast and visual design
- Text and interface colors chosen to meet WCAG AA contrast ratios across the shared component set.
- Form controls with visible borders, so input fields read as fields — not as faint boxes — for people with low vision or on a washed-out screen (WCAG 1.4.11 Non-text Contrast).
- No information conveyed by color alone. Required fields, errors and status messages carry text as well as color.
Touch and pointer
- A 44 × 44 pixel minimum touch target on touch devices for buttons, primary calls to action, form controls, mobile-menu destinations and accordion toggles — comfortably above the 24 × 24 minimum in WCAG 2.2 (2.5.8 Target Size).
- Phone numbers are tappable links, so you never have to transcribe a number by hand.
Forms
- Every field has a visible, programmatically associated label. We do not rely on placeholder text as a label.
- Autocomplete attributes on name, phone, email and address fields, so browser and assistive-technology autofill works.
- Rejected submissions produce a plain-text explanation placed at the top of the form and announced to assistive technology, and the form keeps everything you already typed instead of clearing it.
- Only name, phone, service type and the contact-consent checkbox are required. Everything else — photos, address detail, description, timing — is optional, so a longer form never becomes a barrier to reaching us.
Motion and media
- Reduced-motion support. If your operating system is set to reduce motion, animations and transitions are disabled rather than merely shortened.
- Auto-advancing sections can be stopped. A small number of sections rotate on their own — the reviews carousel and the recent-work feed. They do not move at all when reduced motion is requested, they pause as soon as you hover or move focus into them, they stop while the browser tab is in the background, and each one has manual controls so you can move through it yourself.
- Alternative text on every image. Every image on the site carries an alt attribute — again, enforced at build time — and decorative images are marked as decorative so screen readers skip them instead of announcing filler.
- No auto-playing video or audio, and no flashing content. We do not currently publish video or audio anywhere on this site. If we add any, it will ship with captions and a transcript.
Responsive behavior
- Pages reflow to a single column and remain usable on narrow screens and at high browser zoom, without horizontal scrolling (WCAG 1.4.10 Reflow).
- Layout contracts are validated on every build — fluid containers, shrinkable form controls and long-form text, responsive images and embeds, a small-screen breakpoint, short-landscape handling and safe-area spacing — so a change to one template cannot silently break the rest of the site.
Known limitations, and what we are doing about them
These are the gaps we know about right now.
1. Assistive technology has not been tested
The limitation: our markup is built to be screen reader friendly, but until someone runs a real screen reader through a real service-request flow, "should work" is not "does work." Things like announcement order, error announcement, and how our disclosure sections behave in browse mode are unverified.
What we are doing: assistive-technology test passes — screen reader, voice control and keyboard-only, on both desktop and mobile — are planned as the next accessibility work on this site. We will update this statement with the date and the findings when they are complete, including anything that fails.
2. Automated checks cannot judge quality
The limitation: our build verifies that every image has alt text, that headings are in order, and that landmarks exist. It cannot tell whether a particular alt text is genuinely useful, whether a heading is well named, or whether focus lands somewhere sensible after an interaction. Those are human judgments and we have not reviewed every page for them.
What we are doing next: manual page-by-page review, prioritizing the pages people actually use to reach us — the home page, service pages, service-area pages and the quote and contact forms.
3. Interactive components need individual review
The limitation: the service-area map, the ZIP code coverage checker, the symptom selector and the photo upload control are more complex than plain text and have not been individually tested with assistive technology.
What we do instead, and always will: each of these has a non-interactive route to the same outcome. The counties and cities we serve are listed in plain text as well as shown on the map; you can tell us your address in the form or on the phone rather than using the ZIP checker; photos are entirely optional and you can describe the problem in words instead.
4. Blog and long-form content
The limitation: articles are written and published over time by different people. Heading structure and alt text quality in older posts have not all been re-reviewed against our current standard.
What we are doing about it: reviewing older articles as we update them, and applying the same build-time checks to every new one.
5. Third-party components we do not control
Some parts of this site come from outside providers. We choose them carefully and we are responsible for how we use them, but we do not control their internal code and cannot fix their accessibility ourselves.
- Google Maps — used to display our service area. The map is supplementary. Every county and city we serve is also written out in plain text on the page, and you never need the map to contact us or to check whether we cover your address.
- Google reCAPTCHA — protects our forms from automated spam. It normally runs invisibly in the background with nothing to solve. If it ever presents you with a challenge you cannot complete, stop and call us instead; we will never ask you to pass a test to get service.
- Google Places address suggestions — offers address completions as you type in the service address field. You can ignore the suggestions entirely and type your address yourself, or leave the address field blank and give it to us over the phone.
Our approach: keep a text-based equivalent for anything a third-party component provides, and review whether these components still earn their place each time we rebuild a page.
Tell us about a barrier
If any part of this site is difficult or impossible for you to use, please tell us. You do not need to know why it happened or what to call it — "I could not get past the phone field with my keyboard" is a perfect report.
How to reach us
- Call: (469) 281-7750 — calls are answered 24 hours a day, seven days a week. If you cannot use the form for any reason, this is the fastest route, and someone will take your report or handle your service request over the phone.
- Email: contactus@heatherwindowanddoor.com
- Our contact page, if the form works for you.
We are a mobile service business — our technicians come to you, and we do not have a showroom or a walk-in counter, so there is no location to visit. Phone and email are the ways to reach us.
What helps us fix it faster
Only if you have the details handy — none of this is required:
- The page you were on, or roughly what you were trying to do.
- What went wrong, in your own words.
- The device, browser or assistive technology you were using.
What you can expect back
- We aim to reply to accessibility reports — what we found and what we intend to do — within five business days.
- If a fix will take longer than that, we will tell you so and give you a way to get what you needed in the meantime.
- Reporting a barrier never costs you anything and never delays your service. If you contacted us about a repair and hit an accessibility problem along the way, call us and we will take the whole request by phone.
Information in another format
If you need anything on this site — service details, our warranty and payment terms, or a written estimate — in a different format, ask and we will provide it. That includes large print, plain text by email, or simply having it read to you over the phone.
How we assess this site
We use a self-evaluation approach. No external organization has evaluated this site on our behalf. Our assessment is made up of three things.
Automated checks on every build
The site cannot be published if it fails them. They verify that every page has exactly one H1, that heading levels do not skip, that no heading is empty, that every image carries an alt attribute, that a main landmark and a correct viewport declaration are present, and that no internal link is broken.
Manual review by our team
Keyboard-only walkthroughs of the main paths through the site, checks at multiple viewport widths and zoom levels, and review of color contrast on shared components.
Reports from people using the site
Feedback from visitors is treated as a real finding and goes into the same queue as anything our own checks turn up.
We review this statement whenever we make a significant change to the site, and at minimum once a year. When assistive-technology testing is completed, we will revise the conformance section above to describe exactly what was tested, on what, and what it found.
Formal complaints
We would much rather hear from you directly and put it right. If you are not satisfied with how we have handled an accessibility concern, ask for it to be escalated to the business owner and we will make sure it is looked at again.
Statement prepared August 6, 2026 by Heather Window & Door, based on a self-evaluation of this website. It has not been reviewed by an attorney or by an external accessibility auditor.