/ Accessibility · Last updated June 23, 2026

Built for everyone
who needs the lights on.

We target WCAG 2.1 AA, and we treat accessibility the same way we treat the electrical code — as the floor, not the ceiling.

Visual

Text contrast meets WCAG AA against every background (≥4.5:1 for body, ≥3:1 for large text)
Color is never the only signal — every status uses icon, label, or shape too
Focus rings are visible, high-contrast, and never stripped
Text resizes up to 200% without loss of content or function
Dark-first palette with deliberate contrast in every state

Keyboard

Every interactive element is reachable with Tab and operable with Enter or Space
Skip-to-content link appears on first Tab
No keyboard traps — Escape closes every modal and overlay
Logical focus order matches visual order
Custom widgets follow the ARIA Authoring Practices for keyboard behavior

Assistive tech

Semantic HTML first; ARIA only when native semantics don't exist
Form inputs have programmatic labels, error messages tied with aria-describedby
Images carry meaningful alt text; decorative SVGs use aria-hidden
Headings step in order — exactly one H1 per page
Dynamic regions announce updates with aria-live where appropriate

Mobile & motion

Tap targets meet the 44×44 px minimum
Pinch zoom is enabled; the viewport is never locked
Animations honor prefers-reduced-motion — parallax, autoplay and decorative loops pause or shorten
Safe-area insets respected on notched and curved screens
Horizontal scrolling is opt-in only and never required for content

Our standard, in plain terms

The Web Content Accessibility Guidelines (WCAG) 2.1 Level AA is the legal benchmark referenced by the ADA, California's Unruh Act, and Section 508. We test against it on every release. Our development pipeline runs automated checks (axe, Lighthouse) on every preview build, and we do manual keyboard and screen-reader walkthroughs before publishing structural changes.

Known gaps we are actively working on

Accessibility is a moving target. Third-party widgets (maps, embedded forms, chat) sometimes ship updates that regress keyboard or screen-reader behavior. We monitor for these and patch within five business days of a verified report. PDF project specs older than 2023 may not be fully tagged — we will provide an accessible alternative on request.

Report an accessibility issue

If you hit a barrier — a control you cannot reach with a keyboard, a contrast issue, a screen-reader quirk, a form you cannot complete — tell us. Include the page URL, your device and browser, what you tried, and what happened. We answer every report within one business day.

Email info@silvercreekelectric.com · Call (408) 321-9094 · Or use the contact form.

Our commitment

If you tell us a real barrier exists, we will not argue with you about whether it is "technically compliant." We will fix it. Our goal is a site that works for every owner, GC, architect, and facility manager who needs to reach us — regardless of how they browse the web.

Built for everyonewho needs the lights on.