Skip to content
SteadyPress

Accessibility Statement

SteadyPress is built for working developers, and that includes developers and customers who rely on assistive technology. This page describes what we aim for, what we’ve done, and how to tell us if we missed something.

Our commitment

SteadyPress is committed to digital accessibility. Our target is conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA across the marketing site and the product UI.

Standards

We use WCAG 2.1 Level AA as our reference standard. In practice that means:

  • Keyboard navigation works for every interactive element.
  • Semantic HTML throughout — real headings, real buttons, real form labels.
  • Color contrast meets 4.5:1 for normal text and 3:1 for large text and UI components.
  • Images have alt text where they carry information and are marked decorative where they don’t.
  • Form labels are explicit and error messages describe what to fix.
  • Visible focus indicators on every interactive element.
  • No reliance on time limits, motion, or flashing content.

What we’ve done

  • Our design system was built with WCAG-compliant color contrast on every color pair we use.
  • Every interactive component has a visible keyboard focus state.
  • We use native semantic HTML where it works: <details> for accordions, real <button> elements for actions, real <label> elements for form fields.
  • We honor the prefers-reduced-motion media query and suppress non-essential motion when it is set.
  • Skip-to-content links are present on every page.

Known limitations

We are honest about what’s still rough:

  • Decorative screenshots use alt="" and aria-hidden="true". Substantive screenshots include descriptive alt text, but coverage may be uneven on older blog posts.
  • Embedded video content, when added to the blog, may not yet have transcripts. We will add transcripts as a follow-up rather than block the post.
  • Third-party embeds (Stripe checkout, for example) are subject to the vendor’s own accessibility implementation.

Feedback

If you hit an accessibility barrier on this site or in the product, let us know. Please include the page URL, what you were trying to do, and the assistive technology you were using if relevant. We aim to respond within 5 business days.

Continuous improvement

We re-test accessibility on every major release using a mix of automated checks and manual keyboard and screen-reader passes. Issues found are tracked alongside other bugs, not in a separate parallel list.

Date of last review

2026-05-21.