Accessibility Statement

Conformance status

The Web Content Accessibility Guidelines (WCAG) define requirements for designers and developers to improve accessibility for people with disabilities. WCAG has three levels of conformance: A, AA, and AAA.

Every Level A and AA failure we have found on sunriseelectricalcontracting.com has been fixed, but we do not claim full conformance with WCAG 2.2 Level AA. Some criteria can only be judged by a person using assistive technology, such as whether every status message is announced, and nobody has tested those yet. The gaps we know about are listed under “Limitations and alternatives.” This is our own evaluation, not an outside audit or a formal conformance report, and we do not give a percentage of the site that conforms.

We have also worked through many Level AAA criteria, the optional highest level, which the W3C itself does not recommend requiring for a whole site. We do not claim AAA conformance, and the gaps below include the AAA ones we know about. This statement covers the public website. The staff tools behind our sign-in are internal and are not part of it.

What we do to be accessible

Content and navigation

• Plain-language content authored against our editorial standards
• Images that carry meaning have descriptive alt text; images that are purely decorative are hidden from screen readers rather than described
• The first time a glossary term or abbreviation (GFCI, AFCI and similar) appears on a guide, service or glossary page, it links to its glossary entry
• Guides, glossary entries, services, areas, tools, reviews and the policy pages show a breadcrumb trail of where you are. The standalone booking page has none, because it deliberately has no site navigation
• Our AI chat assistant carries a persistent on-screen “AI assistant” label and is reachable by keyboard

Color and display

• Text and background colors come from a fixed set of design tokens. An automated check on every code change holds the main text colors, including muted text, to 7:1 contrast (the stricter AAA level) and the edges of form fields and other interface parts to 3:1, in both the light and dark themes. A scan of the rendered text on 14 representative pages, in both themes, on October 14, 2026 found none below 7:1 (4.5:1 for large text)
• Form fields have a visible edge and their placeholder text has enough contrast; both were raised in October 2026 after we found them too faint
• The site is styled for forced-colors mode (Windows High Contrast) across booking, search, the calculators, the home page and the area, service and guide pages. Automated tests cover the calculators, the booking steps, the home page's hotspot, status dots on service and guide pages, the glossary's letter rail and the keyboard focus ring. Two highlighted states, an address suggestion and a search result, are styled but not covered by those tests
• We respect prefers-reduced-motion and minimize unnecessary animation. The decorative pulse rings (around the AI assistant's launcher and on the home page's live dots) pulse twice and then rest, and an automated test fails a code change that adds a looping animation to our stylesheets, apart from loading spinners

Keyboard, focus and touch

• The site can be operated by keyboard. Pages with our standard header and footer begin with a skip link to the main content; on a first visit, the cookie notice's controls come before it in the tab order. The standalone booking page at /schedule has no repeated header or footer to skip, so it has no skip link. The one-key “/” shortcut for search was removed, so search opens only with Ctrl+K or Cmd+K or its button
• The keyboard focus ring is always visible, and we added space so that sticky bars and the chat launcher do not cover the element you are on. On the glossary, the sticky toolbar no longer hides the links you tab to
• The header buttons, the chat close button, the cookie buttons, the form checkboxes and radio buttons, and the glossary's letter rail have touch targets of at least 44 by 44 pixels

Booking

• After you book, the photo-upload offer closes after nine minutes. A minute before it closes the page warns you and offers “Keep this open,” which you can use up to ten times, each time giving you another nine minutes. Nothing is lost if it closes: your booking is already made, and the page tells you where to email the photos
• If you leave a booking half finished, what you entered is saved in your browser for up to two hours, and the page says so
• In the booking and change-or-cancel flows, errors and most status messages are announced to screen readers as they appear. Some, such as photo-upload progress, appear conditionally, and we have not confirmed with a screen reader that each one is announced

Limitations and alternatives

We know we don't catch every accessibility issue on every page. If you encounter content that isn't accessible to you, we want to hear about it — and we'll get you the information or service through another channel in the meantime.

Not yet tested with assistive technology

• We have not yet done a manual pass with screen-reader software. Our checks confirm that pages expose the right structure, names and roles; they don't tell us whether the result is actually pleasant to listen to. A hands-on pass with NVDA, VoiceOver and TalkBack has not happened yet, and it is the main thing standing between this statement and a firmer claim.
• The booking flow hasn't been watched end-to-end by a person using a screen reader. It can be completed by keyboard, and its errors are announced. Our automated axe-core check covers the booking pages, including /schedule and the change-or-cancel page, but it blocks a code change only for critical violations; lesser findings are reported without stopping anything. What's still missing is someone actually completing a booking with a screen reader running, including the bot check and the address suggestions, which are provided by third-party services (Cloudflare Turnstile and Google Places) that we do not control.

Other gaps

• We have not met every Level AAA criterion. Known ones: some long sections of guides and service pages still run more than about 300 words under a single heading, and we are adding sub-headings to them; we have not yet added the plain-language summaries at a lower-secondary reading level that Level AAA asks for, though we are piloting one on a single guide; and the photo upload after booking is timed (it can be extended, but it is not untimed).
• Our automated checks mostly run on a test copy of the site, not the live one. The pre-merge accessibility check covers every guide, glossary entry, area and service page that existed when that copy was last refreshed; a page published since then is first checked by the weekly Lighthouse audit of the live site.

If something gets in your way

If any of these gets in your way, the fastest fix is to call or text us and we'll handle it directly. Nothing on this site is the only way to reach us.

Feedback channel: service@sunriseelectricalcontracting.com — monitored during business hours.

Phone: (831) 786-5506 — answered during business hours; backup answering service after hours.

What you can expect from us:

• Acknowledgment within 5 business days of your message.
• Proposed solution within 10 business days of your message.

If a specific page or feature isn't accessible to you, we will provide the information or service through an alternative channel — phone, text, mail, or (for Sunrise customers in our Santa Cruz County service area) an in-person visit — at no cost to you.

How we assessed accessibility

This is a self-evaluation. No outside firm has audited the site, and we have not commissioned a formal conformance report.

What that self-evaluation consists of:

Automated checks

• Automated axe-core testing of every guide, glossary entry, area page and service page in our test build, plus our other page templates and the booking pages. A code change that affects how pages render can't be merged while it shows a critical violation; serious and moderate findings are reported but do not block it
• Lighthouse accessibility audits on 15 representative pages whenever a change reaches our main branch, where anything under a perfect score fails, plus a weekly Lighthouse audit of the pages listed in our sitemap on the live site. Pages kept out of the sitemap, such as the standalone booking page, are not in the weekly run
• A scan of the rendered text contrast on 14 representative pages in both themes, an automated check of the color tokens on every code change, and tests that put controls into their hover, pressed and keyboard-focus states and check that none falls back to low-contrast orange text
• Build checks on every proposed code change that fail if a page loses its skip-link target, or if a photo placeholder starts announcing itself to screen readers

Reviews and walkthroughs

• On October 13, 2026, two reviews checked the site against all 86 WCAG 2.2 success criteria at Levels A, AA and AAA: one read our source code, and the other measured the live site in both the light and dark themes. We then fixed the Level A and AA failures they found and many of the Level AAA ones. The gaps above are what we know of now
• On October 15, 2026 we re-ran two of those measurements on the live site after the fixes: the site header under text-spacing overrides at widths from phone to desktop, and a count of long sections with no heading across the 198 pages in our sitemap
• A point-in-time review of accessible names, landmark structure and heading order across 34 pages
• A point-in-time keyboard walk of 13 pages

Continuing improvement

We re-verify accessibility at least annually and after any major site change. When a review date appears at the top of this page, it is the date of the most recent verification.

If you have ideas, frustrations, or specific issues you've run into — please tell us. The fastest way to improve is to hear from people actually using the site with assistive technology.