Accessibility
Accessibility Statement
Last updated: July 2026
KeevaathTech is committed to making this website usable by everyone, including people with disabilities. We also sell accessibility conformance audits, which means this site should meet the standard we assess other people against. If it does not, we want to be told.
Our standard
We build and test toward the Web Content Accessibility Guidelines version 2.2 at Level AA. Version 2.2 is the current recommendation and it is the standard we assess client products against, so it is the one we hold ourselves to. Section 508 of the Rehabilitation Act references an earlier version, and conformance to 2.2 Level AA meets or exceeds it in the areas covered.
What is built in
- Semantic structure and landmark regions, so assistive technology can navigate the page in a logical order
- A skip to content link, and full keyboard operation with a visible focus indicator on every interactive element
- Color pairings checked against the contrast ratios required at Level AA
- Text alternatives for meaningful images, with decorative artwork marked so that it is skipped
- Labeled form fields, with errors identified in text and never by color alone
- Respect for the reduced motion setting, which disables every animation and transition on the site
- Layouts that reflow and remain usable when zoomed to two hundred percent
How we test
Automated scanning establishes a baseline. Beyond that we navigate the site by keyboard alone, test with a screen reader on at least one desktop and one mobile combination, and manually review contrast, focus behavior, error handling and reading order. Automated tools alone find only a minority of real barriers, which is why we do not rely on them.
Something we deliberately do not do
We do not use an accessibility overlay or widget on this site, and we advise clients against them. Overlays do not deliver conformance, and their presence has become something plaintiff firms treat as worth investigating. Real remediation is slower, and it is the only approach that works.
Known limitations
Accessibility is never finished. Where we know of a barrier we record it here instead of leaving it unstated. Testing against this standard is in progress, and any barrier we find will be recorded in this section with the date it was identified and the date it was resolved. We review as we add content and features, and we will update this section as anything is found.
Tell us where we fall short
If you encounter a barrier, or need information in a different format, write to [email protected] or call +1 571 293 6317. Please tell us the page and what happened. We aim to acknowledge within two working days and to tell you what we intend to do about it.