Accessibility

Accessibility Statement

cyberguards.ai is built to be usable by as many people as possible, including people who use screen readers, keyboard navigation, voice control, or other assistive technology.

Get a straight answer

Our target

We aim for conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA across the public website. This is the same target most modern accessibility regulations and procurement standards reference. We treat conformance as an ongoing practice rather than a finished destination.

What we have done

  • Semantic HTML. Headings, landmarks, lists, tables, and form controls are marked up semantically so assistive technology can navigate the page structure.
  • Keyboard navigation. Every interactive element is reachable and operable from the keyboard. A "skip to main content" link is present at the top of every page.
  • Visible focus indicators. Focus is shown clearly so keyboard and switch users know where they are.
  • Color contrast. Text and interactive controls meet WCAG AA contrast requirements against their backgrounds.
  • Alt text. Images that convey information have descriptive alternative text. Decorative images are marked as decorative so assistive tech can skip them.
  • ARIA used sparingly. We use native HTML semantics first; ARIA only fills the small remaining gaps.
  • Reduced motion. Animations respect the operating-system "reduce motion" preference.
  • Form labels. Every form control has an associated label and error messages tied to the field they describe.
  • Mobile and zoom. The site is responsive and remains usable when text is enlarged up to 200%.

Known limitations

Accessibility work is never complete. Areas we are continuing to improve:

  • Third-party content. Some embedded third-party experiences (calendar booking, analytics opt-outs) follow their providers' accessibility implementations and may not fully match our internal standards.
  • Older posts. We are progressively reviewing older blog content against current standards; if you find a specific issue, please report it.

If you find a barrier we have not listed, telling us about it is the most direct way to make the site better.

How to report an accessibility issue

Email [email protected] with the subject line [ACCESSIBILITY] and as much detail as you can comfortably share:

  • The URL where you encountered the issue.
  • A short description of what you were trying to do.
  • Your browser, operating system, and any assistive technology you were using.

We acknowledge accessibility reports within five business days and aim to fix substantive issues within thirty days where the change is technically feasible. If a fix will take longer, we will tell you why and provide a target date.

Alternative ways to reach us

If the website is creating a barrier for you and you need to communicate with us another way:

  • Email: [email protected]
  • Postal: CyberGuards, 2261 Market St, STE 85291, San Francisco, CA 94114, United States

Changes to this statement

We update this page when we ship significant accessibility improvements or when our targets change. The "Last updated" date at the top tracks the latest revision.

Want a credible answer when a customer, auditor, or your board asks how secure you are?

A quick scoping call with the senior tester who would run your engagement. No slides, no pitch — we look at what you have, tell you what we would test first, and give you a fixed scope, price, and date.

Get a straight answer