Accessibility

An accessibility statement you can check

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

In the code today

What is built in

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. Dropdown menus open on keyboard focus as well as on hover, 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 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 near-black on white surfaces, and the link and accent shades are deliberately darkened variants selected for contrast against white; the stylesheet documents the link violet at roughly 5:1. The exceptions are listed honestly below.

Accessible forms & status messages

Form fields carry programmatically associated labels, required fields use native validation, and submission feedback is announced through a live status region (role="status", aria-live="polite"). Decorative marks are hidden from assistive technology.

Known limitations

Where we currently fall short

A statement that claims perfection is a statement you cannot trust. These are the gaps we know about.

  • Some fine print and muted captions use the faintest gray in the palette and fall below the 4.5:1 contrast ratio that WCAG AA asks of body-size text.
  • The decorative gradient used for headline emphasis passes through a light amber stop that can dip below the 3:1 ratio expected of large text.
  • 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.

Found a barrier?

Tell us, and a person will respond

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.

Report an issue