Skip to content
Lessware

Accessibility Statement

Effective: Pre-launch draft · Last updated: August 29, 2026

Lessware is committed to making GetLessware.com usable by as many people as possible, including people who use assistive technologies. This statement describes our goals, approach, and how to report barriers you encounter.

Our commitment

Financial tools only work if people can actually use them. Lessware's public site and future application share a design direction that prioritizes readable typography, clear structure, sufficient contrast, keyboard operability, and visible focus states.

We are pre-launch. Accessibility is an ongoing practice, not a one-time checkbox. We expect to improve the site as we build, test, and receive feedback.

Design and technical approach

GetLessware.com is being built on Material UI components and patterns, selected in part because MUI documents accessibility expectations for core components and provides accessible defaults for many interactive patterns.

  • Semantic HTML — Meaningful headings, landmarks, labels, and relationships between form fields and errors
  • Keyboard access — Interactive controls operable without a mouse where applicable
  • Focus visibility — Visible focus indicators for keyboard and assistive technology users
  • Color and contrast — Light and dark themes designed for readable text and UI boundaries
  • Form accessibility — Explicit labels, validation messages associated with fields, and error summaries
  • Charts and data — Textual or tabular alternatives for critical Open Ledger statistics where feasible
  • Motion — Respect for reduced-motion preferences where supported by the theme and platform

Target standard

We aim to conform with WCAG 2.2 Level AA for GetLessware.com. Pre-launch, we perform automated and human checks rather than claiming full third-party certification. Automated scores alone are not sufficient.

  • Keyboard navigation through header, main content, forms, and footer
  • Visible focus on every interactive control (minimum 2px treatment)
  • Target size of at least 24×24 CSS pixels, with primary controls at least 44px tall
  • Screen reader labels on navigation, buttons, and form controls
  • Zoom and reflow at 200% and 400%, including 320px-wide layouts
  • Light, dark, and forced-colors/high-contrast themes
  • Reduced-motion preferences respected for animation and transitions
  • Textual equivalents for charts and ledger tables, including stacked mobile cards

Known limitations (pre-launch)

As a pre-launch site, GetLessware.com may have temporary gaps, including:

  • Incomplete alternative text on draft marketing imagery
  • Live product charts are not shipped yet; concept dashboards and Open Ledger tables include textual summaries
  • Pages added during rapid iteration before full accessibility retest

We document material known issues here as we become aware of them and work toward fixes.

Feedback and assistance

If you encounter an accessibility barrier on GetLessware.com, please tell us:

Email: accessibility@getlessware.com

Include the page URL, a description of the issue, the technology you use (browser, screen reader, device), and whether you prefer email or phone follow-up.

We aim to acknowledge accessibility feedback within five business days and to propose a remediation path when the issue is under our control.

Formal complaints

If you are not satisfied with our response, you may escalate to legal@getlessware.com with the subject line "Accessibility escalation." We will review escalations in good faith.

This statement does not create contractual rights beyond applicable law.

Updates

We will update this statement as the site evolves, when we complete substantive accessibility improvements, or when we expand testing scope. The effective date at the top reflects the latest revision.