Legal
Accessibility Statement
Last updated
Our commitment, and what we do not claim
We build this site to target WCAG 2.2 Level AA. We do not claim full conformance. No outside audit has been done. We check the site ourselves, most recently in the review described below, and parts of it may not yet meet every success criterion. We fix what we find and what you report.
What is actually built in
These are measures in the build, not intentions:
- a skip link as the first focusable element on every page;
- a keyboard path through every control, including the mobile menu. Escape closes the menu and puts focus back on its button;
- a visible focus indicator on every focusable element, drawn with
:focus-visibleand re-coloured on dark surfaces so it stays visible; - a real
<label>on every form control (no placeholder-only labelling), with any hint under a field read out together with it; - form errors shown as a message right after each field that needs fixing. The message is tied to its field, so a screen reader reads them together. A status line that screen readers announce names every field to correct, and focus moves to the first one;
- tables that scroll sideways on a small screen can be reached with the keyboard and are named by their caption;
prefers-reduced-motionrespected site-wide;- meaningful
alttext on every informative image and emptyalt=""on decorative ones; - explicit
widthandheighton every image, so the page does not shift under you while it loads; - no accessibility overlay or widget, which cannot fix the underlying markup and can get in the way of the assistive technology you already use.
Colour contrast was checked against WCAG 2.2 AA on every page in the review described below.
Known limitations
Our review, which began on 24 September 2026, found a number of issues. A re-check that evening found one more: the estimated range bar on the window and siding cost calculator covered the first controls on small screens. We fixed it on 25 September 2026 and finished the fix on 26 September 2026, when the bar also stopped covering the Next button on the first step. That was the earlier, step by step version of the calculator, which we replaced on 1 October 2026 (see below). We fixed the other issues between 24 and 27 September 2026, including these three on 27 September 2026.
The first was on the same, earlier calculator. While you worked through its steps on a screen up to 980 pixels wide, the estimated range bar at the bottom of the screen could sit over a control or link, for example just after you pressed Next. We fixed that before the calculator was replaced. The second was in the header. With the browser’s text size set to 20 to 24 pixels, the phone number ran past the edge of a phone screen, so every page scrolled sideways. Where the number no longer fits, the header now shows the phone icon instead, and the link keeps the number as its name for screen readers. The third was in the strip of facts near the top of the Sparks page and the Gardnerville and Minden page. With large text and wider spacing of letters and words, the phone number there could run up to 15 pixels past the edge at some screen widths. It now wraps onto two lines instead.
On 1 October 2026 we replaced the calculator with a new version that has two tabs, one for windows and one for siding. On screens up to 768 pixels wide a strip at the bottom of the screen shows the running total while the controls are in view. It hides once the result panel itself is on screen, and it steps aside when the control you have moved to with the keyboard would sit under it. On 2 October 2026 we ran the automated checker on the new calculator, on both tabs, at screen widths of 1280, 768, 390 and 320 pixels, and again on every page of the site at 1280 and 390 pixels. It reported no failures.
One issue is still open. If you raise the browser’s text size to between 18 and 24 pixels and also widen the spacing of letters and words, for example with a text spacing tool, then at some screen widths between 380 and 485 pixels the phone number in the header can run up to 28 pixels past the edge, and the page scrolls sideways a little. Scrolling sideways brings the number into view, and the same number is at the foot of every page. We know of no other open issue.
On 26 September 2026 we ran the automated checker again on all 70 pages, with its WCAG 2.2 Level A and AA rules and its best practice rules, at screen widths of 1280, 768, 390 and 320 pixels as each page loads. It reported no failures. On 27 September 2026 we also ran it in a separate pass after each step of the calculator and on its estimate, at the same four widths, and it reported no failures there either. That does not mean nothing is there. Neither pass changes the browser’s text size or spacing, so neither shows the open issue above. The checker also listed some text whose colour contrast it cannot measure on its own, because a background image or a decorative mark sits behind or beside it; a person has to check those. Automated tools catch only part of what can get in someone’s way, and the barriers that matter most are the ones we have not found. That is why the reporting route below is a real one. When something is reported, we will list it here with what we are doing about it and when.
Tell us about a barrier
If any part of this site blocks you, tell us: (775) 391-8487 · estimates.wsr@gmail.com · 1155 Watson Way, Suite 7, Sparks, Nevada 89431. Please include the page address and what happened. We aim to respond within 5 business days.
You never need this website to get a quote from us. Call the number above and we will take your project details, give you the same information, and book the same on-site measurement by phone.
How we assessed it, and when
This site is assessed by self-evaluation. No third-party audit has been performed. The most recent review, from 24 to 27 September 2026, covered every page and used:
- the axe-core 4.13 automated checker, with its WCAG 2.2 Level A and AA rules and its best practice rules, at screen widths of 1280, 390 and 320 pixels, and again on 26 September 2026 at 1280, 768, 390 and 320 pixels, each time as the page loads, and on 27 September 2026 in a separate pass after each step of the earlier calculator at the same four widths; and on 2 October 2026 on both tabs of the new calculator at those four widths and on every page at 1280 and 390 pixels;
- a keyboard pass at desktop and phone widths, pressing Tab through every page and checking that each stop shows a focus indicator;
- every form on the site sent empty and with a mistyped email address, to check that each error message appears next to its field and is tied to it;
- a check that no page scrolls sideways at widths from 320 to 1280 pixels, and at phone widths of 320, 360, 390 and 414 pixels with the browser’s text size set to 20, 22 and 24 pixels, and on 27 September 2026 at every third width from 320 to 1280 pixels with the text size set from 17 to 24 pixels, with and without wider spacing of letters and words.
This statement was first prepared on 29 July 2026 and last updated on . It is revised when the site changes materially or when a report tells us something we did not know.
The standard we use, and why
The U.S. Department of Justice has not issued a web-accessibility regulation for private businesses under Title III of the ADA. Its April 2024 rule adopting WCAG 2.1 Level AA applies to state and local government entities under Title II. We use WCAG 2.2 Level AA as our target because it is the current benchmark, not because a regulation names it for us.
Content we do not control
Some links take you to a site run by another company, such as our financing partner’s application flow. The markup there is theirs, not ours, and we cannot guarantee how it behaves with your assistive technology. We are not disclaiming responsibility for the outcome: tell us which one gave you trouble and we will raise it with the vendor, and in the meantime we will give you the same information and take the same request by phone at (775) 391-8487.