Skip to main content
WildroseMarkets

Accessibility

Accessibility

How Wildrose aims to keep marketplace tasks usable.

CurrentVersion 2026-08-01.1Last updated 1 August 2026

Full policy

Open only what you need.

01TargetAccessibility is part of building and reviewing each feature.

Target

Wildrose targets WCAG 2.2 Level AA for public and account pages and tests real tasks, including errors, empty results, sign-in, media, checkout, messaging, and reports. This is an ongoing target, not a claim of independent certification.

02Interaction baselineMeaning and completion do not depend only on a pointer, colour, motion, or JavaScript.

Interaction baseline

  • Semantic headings, landmarks, labels, links, buttons, and form controls.
  • Keyboard access, visible focus, sensible order, and no keyboard traps.
  • Text zoom, reflow, touch targets, and reduced motion.
  • Text alternatives for meaningful images.
  • Status and errors that are not communicated by colour alone.
  • Useful server-rendered content when enhancement code does not run.
03Content, maps, and mediaComplex detail must have a clear text path.

Content, maps, and media

Wildrose prefers plain instructions, status, pricing, and error recovery. Maps need search and list alternatives, keyboard access, privacy-safe descriptions, and a warning that map geometry is not a legal survey. Images must not carry essential facts that the text omits.

04Feedback and another way to complete a taskReport the page, task, barrier, and preferred response format.

Feedback and another way to complete a task

You may report an accessibility barrier without disclosing a diagnosis. Include the page or task, what happened, device or browser, assistive technology if you choose, and your preferred response format. Wildrose will provide a reasonable alternative path or format where practical while a barrier is addressed.

05ReviewAccessibility checks cover the full task, not only a component sample.

Review

Review includes keyboard-only use, screen readers, zoom and reflow, forced colours, reduced motion, touch, slow connections, error recovery, printing where relevant, and no-JavaScript reading paths. Confirmed barriers are prioritized by task impact and user harm.

Help

How can we help?