BuiltIt.dev

Accessibility Statement

Last updated November 6, 2026

BuiltIt.dev should work for everyone, including people who use a screen reader, a keyboard, voice control, screen magnification or other assistive technology. This page explains what we aim for, what we have done, where we know the site falls short, and how to tell us about a problem.

Our goal

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab) at Level AA. These guidelines are the standard most commonly used to judge website accessibility under the Americans with Disabilities Act (ADA) and similar laws.

What we have done

  • Every page has a “Skip to main content” link, landmarks and a logical heading structure.
  • Everything works with a keyboard alone, with a visible focus ring on links, buttons and form fields.
  • The fixed header steps out of the way so it never covers what you are focused on.
  • Images have text alternatives, and decorative graphics are hidden from screen readers.
  • Text, icons and form field outlines meet WCAG AA color contrast, including dark text on every orange button and badge.
  • Contact form fields have labels, required fields are announced, and errors are read out and linked to the field they belong to. If a message fails to send, what you typed stays in place and the Send button keeps focus so you can try again.
  • Links that open a new tab say so, and tables can be scrolled with the keyboard on small screens.
  • Animation follows your device’s “reduce motion” setting, and pages work when zoomed to 200% and on small screens.
  • Before changes go live we run automated checks (axe-core) on every page at desktop and phone width, use each page with a keyboard alone, and review the names and roles exposed to screen readers. These checks ran in Chromium, and a second independent review in November 2026 added selected checks in WebKit.

Known limitations

  • Booking calendar. Call booking uses an embedded calendar from Calendly, a third party. We do not control its accessibility. If it gives you trouble, email us and we will set up a time with you directly.
  • Screen reader testing. We have not yet completed a full pass with VoiceOver, NVDA or JAWS themselves. If something does not read correctly with yours, please tell us.

Tell us about a problem

If anything on this site is hard to use, or you need information in another format, email hello@builtit.dev. Tell us the page and what went wrong, and we will reply within 5 business days with a fix or another way to get what you need.

You can also reach us through the contact page.

How we keep this up to date

We review this site for accessibility when we make significant changes, and at least once a year. This statement was last reviewed on November 6, 2026.