Accessibility
Built to be read by anything that reads.
eligrid.ai is a static document site with no custom widgets, which is the largest single accessibility decision on it: almost everything below follows from using the platform’s own controls rather than rebuilding them.
Semantic structure, and a skip link
Every page is a landmark region — header, main, footer — with one h1 and a heading order that does not skip levels. The first focusable element on every page is a "Skip to content" link that becomes visible on focus.
Keyboard first
There is no custom widget on this site: every interactive element is a native link or button, so tab order, activation and focus behaviour are the browser’s rather than ours. Nothing here traps focus, because nothing here manages it.
Text that scales
Type is set in relative units and the layout reflows to a single column without horizontal scrolling. Nothing is sized to a fixed pixel viewport, and no content is hidden at a smaller one.
Contrast measured, not assumed
The palette is transcribed from the product’s own design tokens, and each accent was measured against the ground it sits on rather than picked by eye. Where a brand colour did not clear the ratio it was lifted until it did.
No motion, no autoplay, no interruption
This site has no animation, no carousel, no autoplaying media, no modal and no timed content. There is nothing to pause, and nothing that moves under a reader.
Images carry text alternatives
Decorative marks are hidden from assistive technology rather than described, and the share cards that carry text are duplicated as real page content — a card is never the only place a sentence appears.
What this page does not claim
It does not claim conformance to a standard. “WCAG 2.1 AA conformant” is an assertion about a formal audit, and there has not been one for this site. Saying it anyway is the same move as putting a certification badge on a security page, and it fails the same way.
Automated checking also has a real boundary worth naming: contrast, tap-target size and scroll-region focus cannot be evaluated from exported markup at all — they need a rendering engine — so an automated pass reporting zero issues is not the same as a page being usable.
If something on this site is in your way, tell us and we will fix it rather than log it: sales@mindhyve.ai. Include the page and what happened; you do not need to identify the standard.