Accessibility

What we build to

We build and test this site against WCAG 2.2 Level AA. That is our own target and our own assessment, not a certified audit. Every route is checked at narrow and wide screen sizes before it ships, and the checks include automated tests and a keyboard pass.

• every interactive element is reachable by keyboard, with a visible focus ring;
• a skip link is the first thing a keyboard reaches on every page;
• text meets the contrast ratios in WCAG 2.2 Level AA;
• text can be enlarged without the layout breaking or content disappearing;
• motion is short, and it stops when the operating system asks for reduced motion;
• form errors are written as sentences next to the field, and the error summary moves focus to the field that needs attention;
• links say where they go. There are no icon-only buttons and no tooltip-only hints;
• pages reflow from 320 pixels wide to 1920 pixels wide without sideways scrolling, and text spacing can be increased without clipping;
• no state depends on color alone, and form controls meet the 24-pixel minimum target size;
• the page declares its language, and every page has one main heading and a logical heading order.

The limits of our assessment

Automated checks and manual passes do not catch everything. We test the pages we ship, but a feature, a browser, or an assistive technology combination we did not test may still have a barrier. We do not claim that this site has zero barriers.

If an independent audit would help you trust the result, ask us for the current accessibility report. It records what we tested and what we found. We will not describe that report as a certification.

If you need a different arrangement

Call or text (605) 376-1715, or email hello@sfcircuitpc.com, and tell us what would work better. The contact page carries the same route. A handoff at a public meeting spot we agree by text is not the right arrangement for everyone. If we cannot meet a need, we will say so rather than let you arrange your day around it.

Tell us what you need for the handoff itself, not only for the website. We will discuss the arrangement and tell you plainly what we can do.

Reporting a problem

Tell us the page, what you were trying to do, and what happened. A phone call is the fastest route. If you prefer email, send the page address and the device or browser you were using. The questions page answers common issues; the privacy policy explains what we keep when you contact us.

Third-party content

This site loads no third-party scripts, embeds, or advertising. The fonts and images are served from this site.