Skip to content

Accessibility

We build for people who use keyboards, screen readers, zoom, and captions.

Our commitment

Sitebix Services treats accessibility as part of the build, not a pass at the end. We want people to reach the same content whether they use a mouse, a keyboard, a screen reader, or a phone. This page describes what we aim for on this site and on the sites we build for clients. It is a plain-language statement of practice. It is not a legal warranty, and it is not a certificate.

The target we aim for

Our target is the Web Content Accessibility Guidelines (WCAG) 2.2, level AA. That is a widely used standard for websites. Aiming for AA means we design and test against those success criteria. It does not mean an outside auditor has certified this site, and it does not mean every control on every page already passes. When we find a gap, we treat it as work to fix.

What we do in every build

  • Semantic HTML. Headings, lists, landmarks, and buttons are real HTML elements, so assistive technology can tell them apart.
  • Keyboard navigation. People can reach links, menus, and form controls without a mouse, see a visible focus style, and skip to the main content.
  • Color contrast. Body text is navy on white. We check contrast when we choose colors, and we do not use color as the only way to show meaning.
  • Alt text. Informative images have a short description. Decorative images are hidden from screen readers.
  • Forms and labels. Every field has a visible label. Errors are written in text, next to the field, and not by color alone.
  • Captions. When a project includes video we host, we plan for captions. If you supply the video, we need a caption file or a transcript from you.
  • Responsive layout and zoom. Pages reflow on a phone and when text is enlarged. We do not disable zoom.
  • Screen reader checks. We listen to the key templates, including headings, forms, and the menu.

How we test

We use automated checks and manual checks. Automated tools catch missing labels, a broken heading order, and some contrast errors. They miss a lot. We also tab through the page, try the forms, enlarge the text, and listen to the main templates with a screen reader. On a client project, the quote names which templates we test this way before launch.

Audits and remediation

We also offer accessibility audits and remediation for sites we did not build. An audit reviews a sample of templates against WCAG 2.2 level AA and returns a written list: what fails, who it affects, and a practical fix. Remediation is the follow-up work to repair those issues in the theme, templates, and content. An audit is a sample. It is not a promise that every future page will conform. Mention an accessibility audit on the Start a project form and we will scope it.

Known limitations

Some things sit outside what we can fully control:

  • Embedded maps, chat widgets, payment forms, and video players from other companies may not meet the same bar. We choose accessible options when we can, and we say so when a tool is weak.
  • Video or audio you upload without captions stays inaccessible until a caption file is added.
  • PDFs and other documents you upload need to be accessible on their own. We can flag them. Fixing the source file is separate work.
  • A theme or plugin you ask us to keep may include controls we cannot fully repair.
  • On this site, white text on the bright blue buttons is below the AA contrast ratio for small text. We are treating that as a known gap, not as a finished state.

Report an issue

If something on this site blocks you, email hello@sitebix.com. Tell us the page address, what you were trying to do, and the browser or assistive tool you used. We read those notes and we fix issues that are ours to fix.