=== Accessibility Statement ===

Kestra is built so that accessibility is checked on every change rather than
audited once at the end. Contrast, reflow, keyboard operation, accessible names
and template structure are all enforced by automated gates that run before a
release is packaged, and a release that fails any of them is not built. The
theme targets WCAG 2.2 level AA.

That said, automated testing has limits, and this statement says plainly where
they are. Tooling can confirm that a control has an accessible name; it cannot
confirm the name is useful. It can measure a focus ring's contrast; it cannot
tell you the ring was clipped by an ancestor. Both gaps have produced real
defects in this theme, and both have since been turned into checks. The
outstanding limitation is recorded under Testing Tools and Methodology below.

== Quick Information ==

Accessibility audit completed: No
Most recent audit date: 2026-09-29
Tested to standard and conformance level: WCAG 2.2 AA (supports)

An accessibility-ready review by the WordPress Accessibility Team on 2026-09-29
identified failures in keyboard focus visibility, focus indicator contrast, link
hover styling, and accessibility documentation. All four have been corrected in
version 1.0.4. Several criteria in that review were not evaluated, so the audit
is not complete and is not claimed as such.

== Testing Tools and Methodology ==

Automated gates, run against a live site before every release:

* axe-core, driven over the Chrome DevTools Protocol across the home, blog and
  archive templates.
* Contrast measurement of every rendered text and UI pairing, in all six style
  variations and all three section styles, against 4.5:1 for text and 3:1 for
  user interface components.
* Reflow at 320px and 640px, failing on any horizontal document scroll.
* A keyboard walk of every tab stop, checking focus indicator presence, computed
  contrast against the colour actually behind the element, and whether an
  ancestor clips the indicator. Skip link, focus trap, Escape and focus restore
  are checked on the navigation overlay.
* An accessible-name review built from the browser's accessibility tree, which
  reports names reused within a single container.
* Template completeness and translation readiness of all user-facing strings.

Manual testing: keyboard-only operation, 200% zoom, and browser text-spacing
overrides.

Known limitation: a full screen reader pass with NVDA, JAWS or VoiceOver has not
yet been carried out. Accessible names, roles, states and landmark structure have
been verified programmatically through the accessibility tree, but that is not a
substitute for listening to the theme, and this statement does not claim it is.

== Screen Reader Text Class ==

screen-reader-text

Applied to text intended only for assistive technology. It is clipped to a single
pixel rather than hidden with display or visibility, so screen readers still
announce it. The class used for the skip link is skip-link, which uses the same
technique and becomes visible on focus.

== Accessibility Features ==

* Skip link to the main content, visible on focus.
* Landmark roles on header, navigation, main and footer, with accessible names
  where more than one landmark of a type exists.
* A focus indicator built from two contrasting tones, so it remains visible
  against any background colour a style variation or section style produces.
* Links in body text are underlined by default; the underline is removed on
  hover, so the state change does not rely on colour.
* Navigation overlay traps focus while open, closes on Escape, and returns focus
  to the control that opened it.
* All animation and transition is disabled under prefers-reduced-motion.
* Six style variations, each contrast-checked independently.
* Full right-to-left language support.
* Decorative images ship with an empty alt attribute; informative images carry
  translatable alternative text.

== Accessibility Help Contact ==

https://kiyanoosh.com/

== Where to Report Issues ==

https://kiyanoosh.com/
