Our commitment
Calywire builds and runs websites for other companies, so we hold our own site to the standard we ask of client work. Anyone should be able to read what we publish, complete a form, and get in touch with us, whether they browse with a screen reader, navigate by keyboard, enlarge the page, or need captions.
The standard we work to
We are working toward the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. That is a target we keep testing against and improving on, not a finished state. We also build and operate this site with the intent of the Americans with Disabilities Act (Title III) and the California Unruh Civil Rights Act in mind, which is why accessibility is part of how pages get made here rather than a cleanup pass at the end.
What we have done so far
- Ran automated accessibility testing on our main page types (home, service pages, blog index, contact) and walked the same pages using only a keyboard.
- Raised the contrast of the small grey text used across the site so body copy, dates, labels, and footer links clear the 4.5 to 1 minimum against their background.
- Made the keyboard focus ring visible on every link, button, and form field, including inside the contact and newsletter forms where it had been suppressed.
- Fixed the “skip to content” link at the top of each page so it actually appears on screen when it receives focus.
- Corrected heading order so a screen reader user can move through a page by heading without hitting a level that was skipped.
- Took image links that carry no text out of the tab order, so a blog post is announced once instead of twice.
- Checked that images on our main page types carry alternative text, and marked purely decorative graphics so assistive technology passes over them.
- Added an accessibility scanner that runs inside our editor, so new pages get checked before they go live.
Where we still fall short
We know about these and are working through them:
- Some blog posts published before 2023 still carry older markup, thin alternative text, or tables that are hard to follow out of sequence.
- Content embedded from third parties, including YouTube videos and social widgets, is not fully under our control and may not meet the same standard.
- A few downloadable PDFs, mostly older guides, are not yet tagged for screen readers. Ask us and we will send you the same material in a format you can read.
Technology this site relies on
The site is built with HTML, CSS, JavaScript, and WAI-ARIA. Accessibility depends on those working together with your browser and with any assistive technology you use.
Tell us what is not working
If a page, a form, or a document gets in your way, write to info@calywire.com. Give us the address of the page and what happened, and include your browser and assistive technology if you know them. We aim to reply within five business days. If a fix will take longer than that, we will tell you what we are doing and when to expect it.
Last updated: September 4, 2026.