# Accessibility Statement

Card Oracle is committed to making tarot and oracle card readings usable by as
many people as possible, including those who rely on assistive technology.

## Conformance target

Card Oracle's public-facing reading interface aims to conform to the
**Web Content Accessibility Guidelines (WCAG) 2.2, Level AA**.

This is a self-assessment by the plugin authors, not a third-party certification.
Because the plugin renders inside your WordPress theme, the *overall* accessibility
of a page also depends on your theme, content, and other plugins.

## What is covered

The following are addressed in the plugin's own markup, styles, and scripts:

- **Text alternatives (1.1.1)** — card images use the card's name as their alt text.
- **Info & relationships / labels (1.3.1, 3.3.2)** — the question and email fields
  have programmatic labels; the email field advertises its purpose (1.3.5).
- **Keyboard operable (2.1.1, 4.1.2)** — face-down cards can be selected with the
  keyboard (Tab to a card, then Enter or Space). Card selection, shuffling, and
  form submission all work without a mouse.
- **Focus visible (2.4.7) & focus appearance (2.4.11)** — interactive controls show
  a clear focus indicator; nothing sticky obscures the focused control.
- **Target size (2.5.8)** — interactive controls are at least 24×24 CSS pixels.
- **Status messages (4.1.3)** — the shuffle control announces its busy/ready state
  to screen readers.
- **Reflow & logical properties** — layouts use CSS logical properties, so they
  work in both left-to-right and right-to-left languages and reflow on small screens.

## Known limitations

- **Author-chosen colours (1.4.3).** The per-reading *accent colour* is set by the
  site owner. The reading editor shows an advisory warning when an accent does not
  meet the 4.5:1 contrast ratio against white button text, but it does not prevent
  saving a low-contrast colour. Owners are responsible for choosing accessible
  colours (and background images) for their readings.
- **Third-party payment fields.** Card payment fields rendered by Stripe are outside
  the plugin's control; their accessibility is governed by the payment provider.
- **Theme and content.** Heading order, page landmarks, and colour contrast of
  surrounding content come from your theme and the text you enter.

## Automated checks

The plugin's end-to-end test suite runs [axe-core](https://github.com/dequelabs/axe-core)
against a reading page and a daily-card page with the WCAG 2.2 A/AA rule set, so
regressions in the plugin's own markup are caught during development.

## Feedback

If you encounter an accessibility barrier in Card Oracle, please report it through
the plugin's support channel so we can address it. Include the page, the assistive
technology you were using, and what happened.