Accessibility statement
I want this site to work for everyone, including people who use a screen reader, a keyboard instead of a mouse, zoomed-in text, or voice control. Here's what I've done, how I check it, what isn't perfect yet, and how to tell me when something's wrong.
The standard I build to
This site aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. That's the widely used standard for web accessibility. I built this site myself, so if something's wrong, I'm the one who fixes it.
What that means on this site
- Text has a contrast ratio of at least 4.5 to 1 against its background. Large text, buttons, and form borders are at least 3 to 1.
- Everything works with a keyboard, and a clear outline shows where you are on the page.
- Every page starts with a "Skip to content" link.
- Headings are in order, so a screen reader can jump through a page by section.
- Every form field has a visible label. If something's wrong, the error says what, in words, right next to the field.
- Buttons, form controls, and menu links are at least 44 by 44 pixels, so they're easy to tap.
- Pages still work when you zoom to 200%, and on screens as narrow as 320 pixels.
- If your device is set to reduce motion, the site turns animation off.
- Images have text descriptions. Purely decorative images are hidden from screen readers.
- Phone numbers and email addresses are links you can tap.
- The price calculator has a plain-text price list on the same page, so you can get the numbers without using the calculator.
No overlay widgets
You won't find an "accessibility" button or toolbar on this site. Those overlay widgets promise to fix a site on their own. They don't, and the FTC fined one of the companies behind them $1 million for claiming they did. Accessibility has to be built into the pages, so that's how I do it.
How I check it
Before anything goes live, I check every page with WAVE and Google Lighthouse, and I go through every page using only a keyboard. Testing tools only catch some problems, which is why the keyboard pass matters. And it's why I want to hear from you if something still gets in your way.
What isn't perfect
- Placeholder images. Some images on this site are still placeholders while I get real photos taken.
- Outside services. The contact form sends through a service called Web3Forms, and calls happen on Google Meet. I don't control how those are built. If either one gives you trouble, call or email me and I'll do things another way.
Something not working? Tell me.
- Call or text: (717) 714-1031
- Email: ccorkum30@gmail.com
Tell me which page you were on, what you were trying to do, and, if you don't mind sharing, what device, browser, or assistive technology you use. I'll reply and tell you what I'm going to do about it.
If you need something from this site in a different way, just ask. I can go over it with you on the phone or send it to you as plain text by email.
On sites I build for clients
Same standard, same checks, before every launch, and no overlay widgets, ever. Accessibility is shared work, though. If you add photos or text to your site later, they need descriptions and clear wording too. Your contract spells out who handles what.
Last reviewed: October 2, 2026