An accessibility statement you can check
Accessibility
This page states what is actually built into hivesilo.com today, the standard we build toward, and where we currently fall short. WCAG 2.1 AA is our target, a goal we design against, not a certification we hold, and we would rather tell you that plainly.
- WCAG 2.1 AA target
- Keyboard navigable
- Reduced motion respected
What is built in
In the code today
Everything below is verifiable in this site’s markup and stylesheet, in the same spirit as the rest of our claims.
Semantic structure
Every page is written in semantic HTML: labeled header, navigation, main, and footer landmarks, a heading hierarchy, native details/summary elements for expandable FAQs, and a declared page language on every document.
Keyboard access
Interactive elements are reachable and operable by keyboard. Each dropdown menu in the header opens from its arrow button with Enter or Space, as well as on hover, so Tab moves across the bar without opening them, and the mobile menu button exposes its state to assistive technology through aria-expanded and aria-controls.
Visible focus & skip link
A visible focus indicator, a two-pixel outline, is applied site-wide via :focus-visible, form fields show a distinct focus ring, and every page begins with a “Skip to main content” link that appears when it receives focus.
Reduced motion
The stylesheet honors prefers-reduced-motion: reduce: animations and transitions are effectively disabled, smooth scrolling is turned off, and content that would otherwise animate into view is simply shown.
Contrast-conscious palette
Body text is dark ink on the warm light sections and pale lavender on the dark violet and ink sections, and each section sets its own accent and label shades for the ground they sit on. Measured in a browser against each line’s own background, on every page at phone and desktop widths, the lowest contrast of any text is 5.3:1, a small label, above the 4.5:1 that WCAG AA asks of body-size text. Where we fall short is listed below.
Accessible forms & status messages
Form fields carry programmatically associated labels, required fields are checked against the browser’s own validation rules and each missing field is named in a message tied to that field while it shows, and submission feedback is announced through a live status region (role="status", aria-live="polite"). Decorative marks are hidden from assistive technology.
Where we currently fall short
Known limitations
A statement that claims perfection is a statement you cannot trust. These are the gaps we know about.
- On a screen 320 pixels wide, the “compounding problem” diagram on the For Enterprises page runs past the edge of its card, and its three labels are cut off at the side of the screen.
- On the homepage, the headline and its first request sit in the page’s banner, above the main content, so “Skip to main content” moves past them.
- The site has not yet been audited by an independent accessibility firm or tested end-to-end with screen-reader users; the review behind this statement is our own.
We treat these as defects against the AA target rather than acceptable trade-offs, and this page will be updated as they are resolved.
The standard we build toward
We design and review this site against the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. That is a target and a working practice, not a conformance claim or a certification: consistent with how we describe everything else, we will not state it as done until it is true everywhere. New pages are checked against the same target before they ship.
Tell us, and a person will respond
Found a barrier?
Email briefings@hivesilo.com with “Accessibility” in the subject, or use the contact form. A real person replies within hours, 9am to 6pm ET, Monday to Friday, and we read every report.