Accessibility Statement

2k Web Developments LLC is committed to making 2kwebdev.com accessible to as many people as possible, including people who use screen readers, keyboard navigation, screen magnification, or other assistive technology. Accessibility isn't a one-time checkbox for us — it's part of how we build, both for our own site and for the sites we build for clients.

Conformance target

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA — the current standard and the baseline most accessibility laws now reference. We can't honestly claim “fully compliant” — no site that's actively maintained ever truly stays there — so we describe ourselves as substantially conformant and continually improving.

What we've done

As part of a recent accessibility pass, we reviewed the site at the design-system and code level and addressed, among other things:

• Colour contrast: we measured every text/background pair in the design and adjusted muted text, link, accent and form-field colours so body text meets at least 4.5:1 and larger text and interface elements meet at least 3:1.
• Keyboard & focus: every interactive control has a visible focus indicator, and in-page jumps are offset so the sticky header doesn't hide the focused element.
• Forms: every field has a real, programmatic label (not just placeholder text), required fields are marked, and form inputs have borders that meet the 3:1 contrast minimum.
• Structure & semantics: one main heading per page, a logical heading order, and proper landmarks (header, navigation, main, footer) so assistive technology can navigate the page.
• Images: meaningful images have descriptive alternative text; decorative graphics are hidden from assistive technology.
• The service-area map: the interactive map is accompanied by a complete text list of every city we serve, so the same information is available without the map.
• Motion & zoom: we respect the “reduce motion” setting, and the layout reflows without loss of content up to 200% zoom.

We do not use an accessibility “overlay” widget. The consensus among accessibility experts is that overlays don't deliver real conformance — so we fix the underlying code instead.

Known limitations

We're being upfront about the areas we're still working on:

• Manual assistive-technology testing is ongoing. Automated and code-level checks catch a large share of issues but not all of them. We are working through hands-on testing with screen readers and keyboard-only navigation, and will fix issues as we find them.
• Payment checkout. Card and bank payments are handled inside Stripe's secure embedded checkout. That interface is provided and controlled by Stripe, so its accessibility is governed by Stripe rather than by us.
• Third-party content. Where we rely on third-party services (for example, form delivery), we don't control the accessibility of their own pages.

How this was assessed

This statement reflects a self-evaluation combining automated testing with a manual, code-level review of the design system and page templates against WCAG 2.2 AA. It is not a third-party certification or audit.

Tell us about a barrier

If you run into anything on this site that's hard or impossible to use — a page you can't read, a control you can't reach with the keyboard, anything at all — please tell us. Email [email protected] with the page and what went wrong, and you'll reach the person who actually builds and maintains the site. We aim to reply within a couple of business days and to fix genuine barriers as quickly as we reasonably can.

We review this statement as the site changes and update the “last updated” date above when we do.