Last updated: October 23, 2026

We want everyone to be able to plan and grow a garden with Planter, including people who use a screen reader, a keyboard, switch control, voice control, larger text, or reduced motion. This statement covers:

Our standard

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. Planter hasn't had an independent accessibility audit, and some parts don't meet that standard yet; the ones we know about are listed below. Accessibility is ongoing work, and this page describes where things stand today.

What we've done

In the app

  • We've added screen reader labels to buttons, icons, and images, and errors and confirmations are announced.
  • The garden editor works without dragging. Each square is labelled with what's planted in it. With a keyboard, use the arrow keys to move between squares, Enter or Space to open a square, Shift+F10 for its actions, and Escape to close. In Garden Settings → Placing plants, choose Tap to place and move plants by tapping instead of dragging. Tap mode turns on by itself while a screen reader or switch control is running.
  • Settings → Accessibility has High contrast, for stronger text and button colours, and Reduce motion, which stops decorative animations and starts slideshows paused (it follows your device's setting until you change it).
  • The app supports your device's text size setting.
  • On the web app, screen reader support turns on when you select Flutter's "Enable accessibility" button, press Tab, or turn on Settings → Accessibility → Screen reader support.

On planter.garden

  • We've updated text and button colours to meet WCAG contrast levels.
  • Pages have a "Skip to main content" link, and menus, dialogs, and the plant info cards work with a keyboard.
  • Blog images have text descriptions (alt text), and we require them on new blog posts.
  • Animations and smooth scrolling are turned off when your device asks for reduced motion.

On myfrost.date

  • We've updated text, button, badge, and map label colours to meet WCAG contrast levels.
  • Pages have a "Skip to main content" link, and the info (ⓘ) tips open with a keyboard or a tap and close with Escape.
  • Location search results and errors are announced to screen readers, and Escape closes the results list.
  • Each station on the map has a name, and you can Tab between stations and press Enter to open one or to zoom into a group of them. The search box finds the same stations without the map.
  • The temperature, precipitation, and sunrise and sunset charts each have a table with the same numbers.
  • Pages work at narrow widths (320 pixels) without scrolling sideways.

Known limitations

  • Large gardens are slower with screen reader support on. Moving around a garden with hundreds of squares can lag for screen reader and keyboard users. We'd like to improve this.
  • Older newsletters may have images without alt text.
  • Content from other companies isn't fully in our control: Apple, Google, and Amazon handle payments in the app, RevenueCat and Stripe handle payments on the web, YouTube hosts our videos (captions depend on YouTube), and our cookie banner comes from Silktide.

How we check

We check with automated tools (axe) and by hand with a keyboard, and we try to keep accessibility in mind as we build new features.

Tell us about a problem

If something in Planter is hard or impossible for you to use, please report a bug in the app or email support@planter.garden. Tell us what you were trying to do, the page or screen, and the device and any assistive technology you use. We read every message. Planter is a small team, so a reply can sometimes take a while, but we'll get back to you and, where we can, suggest another way to do what you need while we look into a fix.