Accessibility Statement

1. What we are aiming at, and what we are not claiming

We build this site to target WCAG 2.2 Level AA. We do not claim full conformance: no third-party audit has been completed (self-evaluation only, most recently from 24 to 27 September 2026), and parts of the site may not yet meet every success criterion. We fix what we find and what you report.

We are not going to write that this site is perfect for everyone. That promise is unverifiable, and a company that makes it has told you what it wishes were true rather than what it checked.

2. What we actually did

These are build decisions on this site, not intentions:

• A skip link is the first focusable element on every page and jumps to the main content.
• Every interactive control is reachable and operable with a keyboard alone. A table that has to scroll sideways on a narrow screen takes keyboard focus, so it can be scrolled with the arrow keys.
• A visible focus ring follows the keyboard, re-coloured on dark sections so it stays visible there, and that includes the form fields on those sections.
• Every form control has a real <label>. Placeholder text is never used as a label.
• When a form cannot be sent, each field that needs fixing gets its own message on the line below it, such as “Fill in this field.” The message is tied to its field, so a screen reader reads it out when the field takes focus, and it clears as soon as you edit that field. A status line names the fields to fix, and focus moves to the first of them. The short hint that goes with a field is read out with it in the same way.
• prefers-reduced-motion is respected, and there is no scroll-triggered reveal anywhere. Nothing here is hidden behind a scroll effect.
• Informative images carry meaningful alternative text and decorative ones carry empty alternative text, and every image carries explicit width and height so the page does not jump as it loads. Project photographs carry descriptive alternative text that says what is happening in the frame, not a keyword list, and the technical illustrations are inline drawings with a text description. Where a drawing’s own labels would print too small to read on a narrow screen, the same labels are also listed as text under it.
• Colour contrast is checked against WCAG 2.2 AA with an automated check. The most recent run, on 27 September 2026, found no contrast failures on any page, at a desktop width or at a phone width.
• We do not use an accessibility overlay or widget. An overlay does not fix the underlying markup; it announces that nobody did.

3. Known limitations

No barrier that stops you using a page is on our open list today. Three smaller issues are:

• The lettering drawn inside the diagrams is small, especially on a phone. The legend under each diagram repeats every label in 12 pixel text that does not shrink with the drawing.
• With the spacing between letters and lines increased, the longest place name in the cost calculator’s city list is cut off on a small phone while the list is closed. It shows in full when you open the list.
• On a phone held sideways, or with the spacing between letters and lines increased, the calculator’s step counter and step buttons can sit under the page header just after you press Next. Scroll up a little to see them.

On 24 September 2026 an automated accessibility check of all 43 pages of this site, at a desktop width and at a phone width, found no failures, and every form’s focus ring and error messages were checked field by field with nothing left to fix. That check ran as each page loaded, so it did not move through the steps of the cost calculator.

A check on 26 September 2026 that did move through them found one barrier: on a screen up to 980 pixels wide, the Planning range bar at the bottom of the screen could sit over some of the calculator’s controls, such as the city list or the Back and Next buttons. We fixed it on 27 September 2026. The bar now steps aside whenever one of the calculator’s controls would sit under it, and the city list is taller, so it is easier to tap. On 27 September 2026 we ran the automated check on the calculator again after each of its four steps, at screen sizes from a small phone to a desktop, including phones held sideways, and it found no failures.

An automated check catches only some kinds of barrier, and this site has not yet been tested with a screen reader or any other assistive technology. So this is a statement about what we have checked, not a claim that no barrier exists. The barriers that matter most are the ones we have not found, which is why the reporting route below is a real one and not a formality. When something is reported we will list it here, with what we are doing about it and a target date, rather than quietly fixing the page and leaving this section saying “none”.

4. Tell us if something blocks you

If any part of this site blocks you, tell us: (775) 200-0648 · info@adadremodel.com · 1155 Watson Way, Suite 7, Sparks, NV 89431. Please include the page address and what happened. We aim to respond within 5 business days.

The domain’s mailbox is still being provisioned, so if an email bounces, the phone number is the channel that works. A barrier report that reaches nobody is not a report.

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 that is on these pages, and book the same on-site walkthrough by phone.

5. How this was assessed

Self-evaluation during the build: automated checks over the built pages, a manual keyboard pass through every interactive control, and a manual review of colour pairs against the design system’s contrast targets. The self-evaluation of 24 September 2026 repeated the automated check on every page at a desktop width and at a phone width, and checked every form’s keyboard focus ring and error messages. On 27 September 2026 the automated check was also run on the cost calculator after each of its four steps, at phone, tablet and desktop sizes. No third-party audit and no testing with assistive technology. Statement date: 29 July 2026. Last reviewed: 6 October 2026.

6. Where the standard comes from

The U.S. Department of Justice has not issued a web-accessibility regulation for private businesses under Title III of the Americans with Disabilities Act. 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.

7. Content we do not control

This site embeds no third-party content: no map frame, no chat widget, no financing application flow, no video player. Some links do leave this site, and the pages they open are not ours: our financing partner’s own website; building department pages from the City of Reno, the City of Sparks and Washoe County, cited in our articles and area pages (one of them is a PDF); and the cost guide websites the cost calculator cites for its structural and permit allowances. We do not control their markup. If one of those pages blocks you, call (775) 200-0648 and we will take the information by phone, and for financing we will put you in touch with the lender directly.