=== Accessibility Statement ===

Takt is developed with keyboard access, readable content and compatibility with
assistive technology in mind. Accessibility checks are part of development and
release review. A complete accessibility conformance audit has not been completed,
and Takt does not currently claim the WordPress.org accessibility-ready tag or
full conformance with WCAG.

== Quick Information ==

Accessibility audit completed: No

== Testing Tools and Methodology ==

The development checks recorded on 15-17 October 2026 combine source review,
native WordPress integration tests and browser interaction. They cover selected
templates and representative content, rather than every possible configuration.

* Chrome 155: keyboard focus, menu operation and focus recovery, forced-colors
  focus visibility, and page reflow at 200% and 400% zoom.
* Lighthouse 13.4.1: all 27 scored accessibility checks passed in a desktop
  snapshot of the representative club article. This result describes that page
  and automated check set; it is not a full accessibility audit.
* Safari 27.0.1: keyboard navigation, mobile menu focus and return behavior,
  heading and partner names in the accessibility tree, and comment-field labels.
  Responsive views at 320, 390 and 768 CSS pixels were checked in desktop Safari.
* VoiceOver with Safari: the publisher confirmed that the heading rotor was
  available and the representative article's headings were spoken clearly.
  A complete spoken walkthrough of all templates and controls was not performed.
* Local integration and markup checks: skip-link targets, authored main anchors,
  translated controls, headings, image alternatives, table names, duplicate IDs,
  and label references. The gallery was operated with the keyboard, and checkout
  validation was checked without submitting an order.
* Native block rendering tests verify ordinary external links, author-selected
  targets and the explicitly enabled historical link filter. Supplied navigation
  landmarks use concise translated names; author-selected names are retained.
  Core's generated stylesheet includes a non-color-only hover change for text links.

The unreleased 2.0 work received additional focused checks on 17 October:

* Chromium and desktop Safari at 320 CSS pixels: optional mobile action labels,
  menu focus recovery, and undocking the action bar while a menu or input is active.
  Long labels fall back to ordinary document flow instead of being squeezed.
* Optional event registration: required fields, consent labels, wrapping and the
  submit focus indicator; light/dark variants were checked in Chromium and the
  dark variant in Safari. No participant information was submitted in this check.
* The palette assistant was operated at 390 CSS pixels, including invalid color
  feedback, generated contrast results and discarding an unsaved draft.
* Ticket-camera focus transitions have automated regression coverage. A physical
  camera and permission-dialog walkthrough is still outstanding.

Changes affecting these behaviors receive focused regression checks. Test records
are kept with the development source; the installation package does not include
test fixtures or diagnostic screenshots.

The recorded checks do not cover physical mobile devices, NVDA or Firefox. A
complete text-spacing review, all optional style combinations, and all controls
in recommended integrations still need assessment before a conformance claim.
Reduced-motion handling has been inspected and exercised, but every animation
has not been individually timed. No playable demonstration video is supplied,
and no publisher-provided video has been assessed for captions or audio description.

== Screen Reader Text Class ==

The theme uses `.screen-reader-text` to hide text visually while keeping it
available to assistive technology. Focusable elements using this class become
visible when they receive keyboard focus.

== Accessibility Features ==

* A visible-on-focus skip link targets the main content, including templates with
  an authored anchor or without a saved main ID.
* Keyboard focus indicators remain available on links and controls, with specific
  handling for forced-color displays and responsive navigation.
* Native HTML and WordPress blocks provide landmarks, headings, form controls and
  navigation semantics. Optional menus retain keyboard focus when they close.
* Links retain their native browsing behavior unless the author chooses a target
  or the site explicitly enables the historical new-tab filter. Sites enabling
  that filter are responsible for warning visitors about the new tab.
* Default text links have a single underline that changes on hover without
  relying only on color. Saved author styles remain editable.
* Reduced-motion preferences disable theme transitions and animations and remove
  smooth scrolling from the back-to-top action.
* Responsive layouts and light/dark color modes support different reading
  preferences. Site owners retain control over their saved styles and content.

Site owners should review their own colors, headings, links, image alternatives,
media captions and plugin choices. Content or design changes can affect
accessibility after installation.

== Accessibility Help Contact ==

Ask for help in the [Takt support forum](https://wordpress.org/support/theme/takt/).

== Where to Report Issues ==

Report accessibility issues in the
[Takt support forum](https://wordpress.org/support/theme/takt/). Include the theme
version, browser and assistive technology where relevant, the affected page or
template, and the steps needed to reproduce the issue. Do not post passwords,
private account information or other confidential data.
