Login

Accessibility

Accessibility Statement

Centric is committed to making getcentric.ai accessible to everyone, including people with disabilities. This statement describes our current accessibility status, known limitations, and how to reach us if you encounter a barrier.

Last updated: May 2026

What We're Working Toward

We are actively working to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. These guidelines explain how to make web content more accessible to people with disabilities.

Accessibility is not a one-time project — it is an ongoing commitment. We review and improve our site on a continuous basis and prioritize accessibility in all new development work.

Where We Are

getcentric.ai is partially conformant with WCAG 2.1 Level AA. We estimate we are at approximately 95% conformance. The following summarizes what has been completed and what is actively in progress.

Completed

  • Semantic HTML structure on all pages
  • <main> landmark on all pages
  • Descriptive alt text on all content images
  • Color contrast meeting AA ratios throughout
  • Keyboard-navigable navigation and forms
  • Properly labeled form fields with for/id pairing
  • aria-required on all required form fields
  • Responsive design for all viewport sizes
  • Skip navigation link support via id="main-content"
  • Language attribute set on all pages (lang="en")
  • Descriptive page titles on all pages
  • ARIA labels on interactive icon buttons

In Progress

  • Screen reader testing across NVDA, JAWS, and VoiceOver
  • Enhanced focus indicators on interactive elements
  • Form error messaging with ARIA live regions
  • Full audit of blog post content for heading hierarchy

Technologies We Use

getcentric.ai relies on the following technologies for conformance:

  • HTML5
  • CSS3
  • JavaScript (minimal, progressive enhancement only)

The site is a static HTML site served via Google Cloud Storage and Cloudflare CDN. No third-party accessibility overlays or plugins are used.

What We Know About

Despite our best efforts, some areas may not yet fully meet WCAG 2.1 AA. Known limitations include:

  • Form error handling: Our contact form does not yet surface inline error messages with ARIA live region announcements. Errors are indicated visually but may not be announced automatically to screen reader users. We are working to resolve this.
  • Blog post heading hierarchy: Some older blog posts may have heading levels that skip (e.g., H2 to H4). We are auditing these on an ongoing basis.

If you encounter a barrier not listed here, please contact us — your report helps us prioritize.

Report an Accessibility Issue

If you experience difficulty accessing any part of getcentric.ai, or if you find content that is not accessible, we want to hear from you. We take all reports seriously and aim to respond within 5 business days.

Email: [email protected]

Subject line: Accessibility Issue

Include: The URL of the page where you encountered the issue, a description of the barrier, and the assistive technology or browser you were using (if known).

You can also use our contact form to reach us directly.

If You Are Not Satisfied

If you are not satisfied with our response to your accessibility report, you may contact the relevant enforcement body in your jurisdiction. In the United States, this includes the U.S. Department of Justice (ADA.gov).