Skip to content

Legal

Accessibility Statement

This statement describes what this site does today to support accessibility, written from what is actually built, not from a claim we cannot verify.

Target

CedarGrowth Organics aims to meet WCAG 2.1 Level AA. This is a target the team is building toward, not a claim of certified or independently audited conformance.

What is implemented

Keyboard operability and visible focus indicators

Links, buttons, form fields, and the navigation menu are built from standard interactive HTML elements and are operable by keyboard. A skip-to-content link is the first focusable element on every page. Focus is visible: links use an underline that draws in on :focus-visible, and form fields use a visible border on :focus-visible.

Semantic headings and landmarks

Each page has one top-level heading and nested section headings, inside header, nav, main, and footer landmarks, with the primary and legal navigation regions labeled by aria-label.

Form fields with visible labels and programmatic errors

Every form field on this site has a visible label associated with its input through htmlFor, and validation errors are tied to their field with aria-describedby and aria-invalid, and announced through role="alert".

Decorative media handled appropriately

The autoplaying hero video is decorative and is marked aria-hidden, so it is not announced as content. Image placeholders, used until real photography lands, are the opposite case: each carries role="img" with a descriptive aria-label naming the image family and subject, so a screen reader still gets a meaningful description of what will occupy that space.

Reduced motion support

The hero video honors prefers-reduced-motion by holding its first frame static instead of autoplaying, and scroll-triggered reveal animation is gated behind prefers-reduced-motion: no-preference, so content stays fully visible without motion for anyone who has that preference set.

What is outstanding

  • No independent accessibility audit has been performed on this site.
  • Color contrast and screen reader behavior have not been verified across every component and page.
  • A dedicated accessibility contact route has not been published yet.

Contact

UNKNOWNAccessibility contact route, pending publication.