AccessibilityLast reviewed 2026 · 05 · 01

Accessibility.

We aim for the site and the product to be usable by everyone. We’re not perfect yet — here’s what we hold ourselves to and where we know the gaps are.

The standard we target.

We design and build to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. That is the bar referenced by the European Accessibility Act (Directive (EU) 2019/882), which becomes enforceable on 28 June 2025, and it is the bar courts in the United States have consistently applied under Title III of the Americans with Disabilities Act. We treat WCAG 2.2 AA as a floor, not a ceiling.

What’s in place today.

  • Semantic HTML — landmarks, headings, lists, and form elements that mean what they say.
  • Keyboard navigation — every interactive element on this site can be reached and operated without a mouse.
  • Visible focus — the focus ring is not removed; it is styled to remain visible against the parchment background.
  • prefers-reduced-motion is respected — if your system asks for less motion, we drop the fade-ins and any other transitions.
  • Form labels are programmatically associated with their inputs. No placeholder-as-label tricks.
  • Body text meets the 4.5:1 contrast ratio against the page background.

Known gaps.

We’d rather name these than pretend they don’t exist.

  • Brand amber on cream. Our amber accent (#C8893D) on the parchment background may fall below the 4.5:1 contrast ratio for small uppercase labels and metadata. We are auditing every use and will either darken the token, increase the type size, or move to ink for affected instances.
  • Pipeline diagram. The Goal → Strategy → Tactic SVG on the homepage is currently marked as decorative with an aria-label summary. That summary does not convey the full structure of the diagram to screen-reader users. A long-text equivalent is on the to-do list.
  • PDF assets. The brand book and any other PDFs we link to have not been audited for tagged structure, reading order, or alt text. Treat them as visual-only artifacts until we publish a remediated version.

How to report a barrier.

If something on this site or in the product blocks you, write to us. Plain email is fine; you do not need to know the WCAG criterion.

Email bryan@perseidechocreations.com or bryan@perseidechocreations.com. Tell us the page or screen, the assistive technology you were using if any, and what got in your way. We will respond within seven business days with an acknowledgement, an estimated fix window, and a workaround if one exists.

Last reviewed.

2026 · 05 · 01. We review this statement at least annually and after any material change to the site or product. The next scheduled review is May 2027.

— If anything on this page is unclear, write to us. We’ll fix the wording.

Back

Back to Bristlecone.

Home