HexCoreAccessibility statement
HexCore wants everyone to be able to read this site and ask us for a scan, including people who use a screen reader, navigate by keyboard, or zoom the page. This page says what standard we work to, what we have tested, what we have not, and how to tell us when something is in your way.
Standard
We work to the Web Content Accessibility Guidelines 2.1 at Level AA, the standard the US Department of Justice adopted for state and local government websites and the one most often applied to businesses. We check new work against WCAG 2.2 as well.
Status
As of 18 October 2026, the two public pages of this site (the home page and /scanner) have no open automated findings and no open findings from our manual review. The last substantive issue, 25 low-contrast text instances caused by one colour token, was fixed on 17 October. Earlier the same day, before that fix, the site would not have passed. We say so because the record is the point.
| Check | Method | Result |
|---|---|---|
| Automated rules (axe-core 4.10) | HexCore's own scanner, real browser, 3 passes | 0 findings |
| Keyboard | Full Tab-order walk; skip link; focus visible on every stop | Pass |
| Structure | Landmarks, heading order, link text, names on all controls | Pass after fixes to plan headings and footer levels |
| Screen-reader semantics | Accessibility tree review of every page region | Pass after hiding decorative glyphs and grouping statistics with their sentences |
| Reflow at 320 px (1.4.10) | Chromium at 320 and 640 px wide | No horizontal scrolling; navigation reachable |
| Text at 200 % (1.4.4) | Root font size doubled at desktop width | No clipped or overlapping text |
| Motion | prefers-reduced-motion honoured by the background animation | Pass |
What we have not done
- A live session with VoiceOver, NVDA or JAWS and a human listener. The accessibility tree we reviewed is what those tools read from, but we have not yet heard the output.
- Testing with people who rely on assistive technology day to day. If that is you and you are willing, we would like to pay for an hour of your time.
- The operator dashboard at
/adminis behind a login and is used by one person; it is reviewed separately and is not covered by this statement.
How the site is built
Plain HTML and CSS with a small amount of JavaScript for the background animation and the dashboard. There is no accessibility overlay or widget on this site, and we will not add one; the fixes are made in the markup. Fonts load from Fontshare and Google Fonts. No page requires JavaScript to read or to contact us.
Tell us about a barrier
If any part of this site is hard or impossible for you to use, email [email protected] and tell us the page and what happened. A person reads that inbox. We reply within two business days, and we will record the report and the fix in the same ledger we keep for our clients, so you can see when it was done.
If you prefer not to use email, write to HexCore Corp., 3031 Tisch Way, 110 Plaza West, San Jose, CA 95128.
About this statement
Written by HexCore on 18 October 2026 after a self-evaluation using our own scanner and the manual checks listed above. It will be updated whenever the site changes materially or a reported barrier is fixed. Back to the main site.