CompubilityBack to home

Accessibility Statement

Accessibility Statement

Compubility is committed to providing a website that is accessible to the widest possible audience, regardless of technology or ability. We continuously work to improve the accessibility and usability of our digital experiences.

Standards and guidelines

We aim to design and build digital experiences that conform to WCAG 2.1 Level AA success criteria and that align with applicable accessibility requirements commonly adopted by public agencies.

  • accessible design and information architecture patterns
  • semantic HTML and keyboard navigability
  • color contrast and readable typography
  • accessible forms, error messaging, and focus management
  • image alternative text guidance and content authoring practices
  • accessibility QA as part of release readiness

Compatibility and assistive technology

Our goal is to support modern browsers and assistive technologies. We test experiences using a combination of automated checks and manual review (including keyboard-only navigation and screen reader spot checks) as part of project delivery.

Known limitations

We recognize that accessibility is an ongoing effort. Some pages or content may not yet fully conform, especially:

  • third-party embedded tools or widgets
  • older PDFs or documents not originally authored for accessibility
  • content authored by third parties that we do not control

When we identify issues, we prioritize fixes based on severity and user impact.

Accessibility support

If you experience difficulty accessing any part of this website or need information in an alternative format, we want to help.

Contact us:

Email: support@compubility.com

To help us respond quickly, please include (if possible):

  • the page URL
  • a short description of the issue
  • what device/browser/assistive technology you’re using
  • a screenshot (optional)

Response timeframe

We aim to acknowledge accessibility requests within 2 business days and to provide an estimated timeline for resolution once we’ve reviewed the issue.

Last updated

Last updated: January 11, 2026