Accessibility
Pejera Electric builds pejera.com to work with a keyboard and a screen reader, and names the parts that still fall short below.
Half our inquiries come from a phone held in one hand at ten at night, often from someone who works during the week and is booking around it. This page is the honest account of what that experience actually is right now, not a promise that everything is solved.
Commitments and known limitations
Read down the left column for what we've built in, the middle for what that means in practice, and the right for where it currently falls short.
| Area | What we've built | Where it falls short |
|---|---|---|
| Keyboard & skip link | A skip link jumps straight past the masthead to the main content, and every interactive element, tab, chip, accordion and form field, follows the same order a sighted visitor sees, with a visible gold focus ring. |
The Find a Fix chip list on a long symptom match can take several tab stops to clear; a "jump to results" link is not yet in place for that section. |
| Color & contrast | Body text runs in near-black ink on cream or paper backgrounds, chosen to clear 4.5:1 contrast. The oxblood accent used for links and buttons was checked against both cream and white before it shipped. |
The aged gold accent is used only for small-caps labels, hairline rules and focus rings, never for a sentence of body copy, because on its own it doesn't clear that same ratio. |
| Photographs & alt text | Every photograph on the site, from a hand stripping wire to a van parked at the curb, carries alt text describing the actual job in the frame rather than a generic caption. |
The duotone breaks are treated as decorative backgrounds with the reversed-out line as real, readable text laid over them, not baked into the image, so a screen reader gets the words without the picture description repeating them. |
| Marquee strips | The running ticker strips on the front page are marked as decorative for assistive technology, since the same service names and towns already appear as real links and text elsewhere on the page. They pause completely on hover, on keyboard focus, and whenever the browser is set to reduce motion. |
On a very slow connection the marquee can render before the font finishes loading, shifting its width for a moment. It settles within a second and never blocks scrolling. |
| Forms | Every field on the contact form, the homepage contact strip and the data request form carries its own visible label, not a placeholder standing in for one, and an error is written next to the field it belongs to, not just in a banner at the top. |
The two spam-trap fields, company and website, are intentionally hidden from every visitor and never labelled; that's a deliberate anti-bot measure, not an oversight, and it holds no information a real caller would ever fill in. |
| Tabs & accordions | The terms of service page uses real ARIA tabs with arrow-key support; below tablet width the same content collapses into a stacked accordion rather than a cramped tab strip. |
Switching a tab moves focus to the panel heading but does not yet announce which of the four parts is now open; we're working the same fix into the accordion state. |
| Chat widget | The chat launcher is a labelled button, reachable and operable by keyboard, and the panel it opens can be closed the same way. |
New messages appear in the log without an audible screen-reader announcement while the panel is open. If that matters to you, call +1 (296) 555-4780 and speak to the dispatcher directly instead. |
| Tap targets & zoom | Every button, tab, chip and footer link holds a minimum touch target of 44 pixels, and the whole site scales cleanly up to 400% browser zoom without content overlapping. |
None known at the time this page was last checked; if you find one, the reporting line below is the fastest way to tell us. |
Report a problem
If a page doesn't work the way this statement says it should, email office@pejera.com with the page and what happened, or call +1 (296) 555-4780 and we'll walk through it on the phone. We aim to acknowledge a report within two business days and to have a fix or a workaround within two weeks for anything that blocks a booking.
Standards we build against
The site is built to the current Web Content Accessibility Guidelines at level AA as a working target, checked by hand with a keyboard, a screen reader and a phone rather than by an automated score alone. Nothing on this page claims a formal audit or a third-party certification we don't hold.
Related reading
This statement sits alongside the legal pages that cover data, cookies and requests.