Accessibility Statement
Last updated: September 2026
Untamed Web Design LLC builds every website — for a client, a prospect mockup, or our own site — to meet WCAG 2.2 Level AA, the Web Content Accessibility Guidelines that the U.S. Department of Justice points to when enforcing the ADA, and that Section 508 uses as its technical standard for federal and federally funded systems. This is not a policy we bolt on after launch — it's a gate every site passes through before it reaches a client or the public.
How we get there
Accessibility is built into how we work, not tested in at the end:
- Automated audit. Every site runs through our accessibility checker before launch, and again after any deploy — checking contrast ratios, missing alt text, heading structure, form labeling, ARIA misuse, and focus order. Zero critical and zero serious findings is the bar; nothing ships with an open one.
- Manual review. A human pass with a screen reader (NVDA/VoiceOver) and keyboard-only navigation — tabbing through every interactive element, confirming skip links, confirming nothing traps focus, confirming forms announce errors correctly.
- Semantic, hand-coded markup. We don't use page builders or bloated CMS themes that bury structure in generic
<div>soup. Real headings, real landmarks, real button and link semantics — the foundation screen readers and assistive tech actually rely on. - Real color and contrast, not guesses. Every text/background pairing is checked against WCAG's 4.5:1 (normal text) and 3:1 (large text, UI components) minimums at design time, not patched after a complaint.
- No overlay widgets. We do not use accessibility overlay/widget scripts. They don't achieve real conformance, several have been the subject of their own ADA lawsuits, and they can actually break screen reader behavior. We fix the site, not paper over it.
Conformance status
| Standard | Status |
|---|---|
| WCAG 2.2 Level A | Fully conforms |
| WCAG 2.2 Level AA | Fully conforms |
| Section 508 (federal technical standard) | Conforms — Section 508 references WCAG 2.0 AA as its floor; we build to the newer, more complete 2.2 AA |
| ADA Title II web rule (DOJ, 2024) | Conforms — the rule's technical standard is WCAG 2.1 AA; we meet the newer 2.2 AA |
"Fully conforms" means the tested pages meet the standard with no known violations at the time of testing. Accessibility is an ongoing practice, not a one-time certificate — see reporting below.
What this means for client sites
Every website we build for a client ships with its own accessibility statement like this one, scoped to that site: conformance level, what was tested and when, any known limitations, and a way to report a problem. Public agencies and nonprofits can attach that statement directly to a procurement file, grant compliance report, or board record. If a project has a formal compliance requirement — a state contract, a federal grant condition, a district policy — we scope the audit and remediation explicitly in the quote, in writing, so the expectation is documented before work starts.
Known limitations
We test primarily with NVDA and VoiceOver, at current browser versions, on desktop and mobile viewports. If a client integrates a third-party embed we didn't build (a payment processor, a booking widget, a map), that embed's accessibility is the responsibility of its vendor — we choose vendors with a strong accessibility track record and flag any exception in writing.
Reporting a problem
If you use assistive technology and hit a barrier anywhere on this site or on a site we built, tell us. We treat accessibility reports as priority fixes, not backlog items, and we'll confirm the fix with you directly.
contact@untamedwebdesign.com · (559) 939-8907
Building or fixing a government, district, or nonprofit site?
We're a certified California Small Business (Micro), #2055352, and accessibility is a gate on every build we do — not an add-on line item. If your current site has an open ADA complaint, a Section 508 requirement in a grant, or you just need to be able to show a conformance statement, that's exactly what we scope.
Why accessibility compliance matters for public-sector websites
Cities, counties, special districts, school and community college districts, transit agencies, and the nonprofits that serve them are under real, growing legal exposure around web accessibility — and it's become a procurement requirement, not just a best practice.
The ADA Title II web rule (effective 2026–2027)
The Department of Justice's 2024 rule sets a hard deadline: public entities with 50,000+ population must conform to WCAG 2.1 AA by April 2026; smaller entities and special districts by April 2027. This is the first time "meet WCAG AA" has been a specific, dated federal mandate for state and local government websites — not a guideline agencies can defer indefinitely.
Section 508 and federal funding
Any agency, school, or nonprofit program that touches federal funds, grants, or federally assisted programs typically carries a Section 508 or Rehabilitation Act Section 504 obligation. A documented conformance statement is often exactly what a grant compliance file or state monitoring review asks for.
ADA Title III risk for nonprofits and quasi-public sites
Nonprofits open to the public — even without direct government funding — have been named in a wave of ADA web-accessibility lawsuits nationally. A conforming site with a public accessibility statement is real risk reduction, not just good practice.
Small business (SB) participation goals
California sets a 25% small-business contracting participation goal, with a bid preference on eligible state solicitations. Pairing a certified SB(Micro) vendor with a genuinely WCAG 2.2 AA-conforming build lets an agency check two procurement boxes with one contract.
This statement describes our practices and the current conformance status of the pages we control. It is a good-faith accessibility statement, not a legal opinion or a substitute for a formal third-party audit where one is contractually required.