Accessibility Statement.

Some visitors navigate with a keyboard. Some use a screen reader. Some need captions, less motion on the page, or stronger contrast to read comfortably. All of them should get the full site, not a degraded version of it.

We also know accessibility is never really finished. Standards evolve, browsers change, and we keep shipping new pages. So rather than treating it as a project we completed once, we have built it into how we work day to day.

This site is built to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. That is the standard most accessibility laws point to, including the Americans with Disabilities Act (ADA) as courts have applied it to websites.

In August 2026 we went through the whole site and fixed what we found: keyboard access, screen reader semantics, focus handling, form errors, color contrast in both light and dark themes, video captions, and reduced-motion support.

A statement is easy to write. What actually keeps this site accessible is a set of checks that run whether or not anyone is thinking about it:

• Automated accessibility scans (axe-core, against WCAG 2.1 A and AA rules) run on our page templates in both light and dark themes before every release. If a scan fails, the release does not go out.
• Accessibility linting runs on all interface code and catches things like missing labels, invalid ARIA, and keyboard traps before they are ever committed.
• Our test suite refuses to publish a blog image without descriptive alternative text.
• Menus, search, forms, accordions, dialogs, and interactive tools are built to work by keyboard, with visible focus indicators and screen reader announcements.
• Team videos have closed captions and a written transcript.
• If your device is set to reduce motion, the site's animations stay out of your way.

We would rather be upfront about the rough edges than pretend there are none. Here is what we know about today:

• A few things on the site come from third parties, like the spam protection on our forms. We choose vendors carefully, but we cannot rewrite their code, and it may not fully meet WCAG 2.1 AA.
• The downloadable report files from our free tools are not yet fully tagged for screen readers. Everything in those reports is also available on the page itself.
• Our companion tools on separate subdomains are catching up to the main site and are not all the way there yet.

If one of these gets between you and something you need, or you run into a problem we have not listed, email us. We will get you the information another way.

If something on this site did not work for you, we genuinely want to hear about it. Real reports from real visitors decide what we fix next. We aim to respond within five business days.

• Feedback email: info [at] silverbackmarketing.com
• It helps if you include the page address, what went wrong, and the browser and assistive technology you were using. But do not let missing details stop you from writing.