Accessibility
We build every page to work with a keyboard, a screen reader and a phone screen at 320 pixels wide.
Resezido Climate is an HVAC company in Austin, Texas, and this site is where most people reach us before we ever meet in person — a lot of that first contact happens on a phone in a hot attic doorway, not at a desk. If a page fights you, that's a defect on our end, and we want to hear about it.
Accessibility at a glance
Read this first- Standard we build to
- WCAG 2.1 at level AA, checked by hand at 320, 360, 414, 768, 1024, 1440 and 1920 pixels wide, not just run through an automated scanner.
- Who to tell
- Call +1 (213) 555-8290 or email office@resezido.com and describe the page and what happened.
- Response time
- Two business days for an acknowledgement, with a plan for what we're doing about it.
- Alternative route
- Everything a form does, you can do the same over the phone — ask a question or send an inquiry. We'll write it down on our end.
- Known gaps right now
- Listed under "What still needs work" below, kept current rather than a blanket claim of full compliance.
- Data handling
- Covered separately in the privacy policy and the data request page — this page is about using the site, not what we do with your information.
01 — CommitmentHow we actually test it
We check the site with a keyboard alone, tabbing through the menu overlay and the forms without a mouse, because a technician standing at a job with one hand on a ladder is going to be doing something close to that. We check it with a screen reader on the pages that carry the most weight — the contact form and the checker on fit-check.html. We check colour contrast against the palette we actually shipped: near-black ink on cream, cream on deep forest green. Amber stays reserved for links and controls rather than body text, because amber-on-cream at small sizes fails contrast and we know it.
We test at seven widths — 320, 360, 414, 768, 1024, 1440 and 1920 pixels — because a layout that only works at one phone size and one desktop size is not actually responsive, it's coincidentally correct twice.
02 — Built inWhat that looks like on this site
Every page has a skip link that jumps straight past the header to the main content, visible the moment it gets keyboard focus. Every tap target — the menu button, the form fields, the footer links, the chat launcher — holds a minimum height of 44 pixels, because a button that's technically clickable at 28 pixels is not clickable with a thumb in a work glove. Every image on this site ships with real width and height attributes and a srcset across four sizes, so a page doesn't jump around as images load in on a slow connection out in the field.
The parallax effect on the homepage hero and the section imagery is driven by a script that checks prefers-reduced-motion first. If your system is set to reduce motion, the moving layers are flattened flat and the scroll reveals show their finished state immediately instead of animating in. Nothing on this site autoplays audio or video, and nothing flashes more than three times a second.
Every interactive control — the menu toggle, the disclosures on the legal pages — is a real button or a real link, not a styled div with a click handler bolted on, so it already carries the keyboard behaviour and the role a screen reader expects. The chat widget follows the same rule: real form fields, a real send button, nothing simulated.
03 — Known limitsWhat still needs work
The parallax hero on the homepage is a visual flourish before it's anything else, and while it degrades correctly under reduced motion, we haven't yet had a blind user test it end to end and we're not going to claim we have. The support chat widget is a third-party-style pattern we built ourselves; it's keyboard operable and labelled, but a long conversation can get dense to read back with a screen reader and we're working on trimming that. If you hit either of these and it genuinely blocked you from getting a quote or booking a job, call the shop directly — that path always works.
04 — ContactTell us what broke
Say which page, roughly what you were trying to do, and what happened instead — a button that didn't respond, or a form field a screen reader skipped. You don't need to diagnose it, just describe it. Reach us at +1 (213) 555-8290 or office@resezido.com, or use the contact page form, which posts to the same inbox dispatch already checks.
05 — StandardsWhere this points
We measure against the Web Content Accessibility Guidelines, version 2.1, level AA. We haven't hired an outside auditor to certify this site, and we're not going to say we have — this statement describes what we build to and test for, not a certificate we were issued. If your own screen reader or assistive setup surfaces something the checklist above missed, that report is worth more to us than the checklist.