Accessibility

Effective Date: May 6, 2026 · Last Updated: May 6, 2026

Our commitment

LearnNearby aims to meet WCAG 2.1 Level AA across the website. Accessibility is part of how we ship: each pull request runs automated checks for color contrast, keyboard reachability, and screen-reader semantics, and we treat violations as bugs rather than nice-to-haves.

We’re a small team and we won’t pretend we’re perfect. If something is hard to use with a screen reader, magnifier, voice control, or keyboard, we want to hear about it and fix it.

What this page covers

LearnNearby is a marketplace: learners book classes from independent instructors who set their own price, schedule, and venue. Two different things contribute to whether a class is accessible to you:

  • The platform itself— the website, the booking flow, the messages and emails we send. This is our responsibility, and what this page is mostly about.
  • The class itself— the venue, the physical space, the format of instruction, materials handed out, and any accommodations the instructor can offer. That part lives with the instructor. We’ll help you reach them, and we’ll enforce our community guidelines if you’re refused service for a protected reason.

Requesting an accommodation

If you need help using the LearnNearby website, an alternative format for any of our content, or assistance booking a class, here are the two fastest paths:

We aim to respond within seven calendar days. If your request is time-sensitive (you’re trying to book a class that starts soon), please say so in your message and we’ll prioritize it.

For accommodations duringa class — seating, signed interpretation, large-print materials, scent-free environment, etc. — please reach out to the instructor directly through the booking page’s message link before booking. If you’re not sure how, contact us and we’ll help relay the request.

What we’re working on

Honest list of known gaps and ongoing work:

  • Map-based search uses MapLibre with a list-view fallback for screen readers and keyboard users; we’re iterating on the fallback’s parity with the visual map.
  • Some older sections of the site still rely on global CSS rather than per-component styles. Migration is in progress and tracked internally; visual results should be the same, but it’s worth flagging if you spot a regression.
  • Mobile apps follow the same WCAG 2.1 AA target as the web. Tell us what platform and assistive tech you’re on when you report an issue — it materially shortens the fix time.

Civil-rights and discrimination concerns

If you believe an instructor refused service to you for a reason protected under California’s Unruh Civil Rights Act, the Americans with Disabilities Act, or any other anti-discrimination law, please report it through the channels above. We’ll investigate, document our findings, and act under our Community Guidelines.

You can also pursue rights independently with the California Civil Rights Department or the U.S. Department of Justice ADA office. Reporting to us doesn’t waive that.

Standards and references