Accessibility statement

Accessibility Statement

Statement prepared: 12 August 2026 Last reviewed: 13 August 2026

A Hungarian-language version of this statement is available at https://seasonry.app/accessibility?lang=hu. Both versions describe the same product and the same barriers.

Seasonry wants to be usable by as many people as possible, including people who use a screen reader, navigate by keyboard, need larger text, or find low-contrast interfaces hard to read.

This statement is voluntary. The rules that apply to us do not require it. We have written it because you should be able to know what works and what does not before you rely on Seasonry.

1. What this statement covers

This statement applies to the Seasonry web application at seasonry.app, including the public pages, the plant catalogue, the Learning Academy, the Almanac and the garden planner itself.

2. The standard we measure against

We measure Seasonry against WCAG 2.2 Level AA, the standard referenced by the European standard EN 301 549. It is what our internal audit was run against and what our automated checks test for, so it is the yardstick behind every claim in this statement.

Seasonry does not meet WCAG 2.2 Level AA. Section 3 lists what already works, and section 4 lists the known barriers. We are not setting full conformance as a target we expect to reach: section 5 describes a decision about the garden planner that rules it out for as long as it stands. Three of the barriers in section 4 are deliberate decisions rather than unfinished work, and section 5 explains all three.

3. What we already support

• Controls across the app show a visible focus outline when you navigate with a keyboard, and only when you navigate with a keyboard.
• Buttons, chips, filters, toggles and cards announce themselves correctly to a screen reader and respond to the Space key, and the ones that can be switched on and off say which they are.
• Tab strips, the account menu and the workspace's plant list respond to the arrow keys, so you move within a group with the arrows and between groups with Tab. In the plant list, up and down move between plants and right reaches that plant's "view on plan" button, so a bed is one stop on the way through the panel rather than two for every plant in it.
• Only what is on screen can be reached by keyboard. Panels that are closed and layers that are hidden are skipped rather than left in the tab order.
• Every plant on your garden plan is reachable with the Tab key and announces its name. Its spread and the bed it sits in are not part of that announcement; the plant panel, described below, is where a screen reader gets those.
• The plan has a text summary giving its dimensions and the number of plants on it, and the plant panel lists every plant and object in the garden, grouped under the name of each bed.
• Errors are announced to screen readers rather than only appearing on screen: a save or sync that fails, a sign-in that does not go through, a message that will not send, and anything a form refuses. A save that works is left to the indicator, so nothing interrupts you on every edit.
• Text contrast meets the AA minimum everywhere we have been able to measure it, on both the light interface and the dark version of our landing pages.
• Every page has its own title, a single main heading and a marked-up main region, so a screen reader can jump straight to the content. Our Privacy Policy and Terms carry full heading and list structure, so you can navigate them by section.
• Decorative icons and illustrations are hidden from screen readers, so they do not read out as unnamed graphics.
• Every dialog announces its own name, takes focus when it opens, and scrolls inside itself rather than putting its buttons out of reach when it is taller than the window.
• Everything that loops can be stopped. The Learning Academy's demonstrations and the plant-placing demonstrations each have a Pause button, and the home page's drifting border has a switch in Profile → Settings. All of them start stopped if your system asks for reduced motion.
• The plant catalogue's results grid is a single stop on the way through the page, and the arrow keys move between the plant cards inside it: left and right by one card, up and down by a row, Home and End to the first and last plant of the whole catalogue. Enter or Space opens the card you are on, F2 moves into the card's own controls and Escape comes back out, and F adds the card you are on to your favourites.
• The bloom strip reads out its months in words, so it does not depend on being seen.
• Single-key shortcuts can be switched off in Settings, under Keyboard.
• Controls meet the minimum target size, with the deliberate exception described in section 5.
• Every text field announces what it is for, using the label you can see beside it wherever there is one.
• When a form will not accept something, it says so in words at the field concerned, moves the cursor there, and reads the message out. Nothing is refused by a greyed-out button alone.
• The password box on a shared garden announces a wrong password and a rate limit rather than only showing them.

4. Known barriers

Grouped by the WCAG guideline each falls under.

1.4 Distinguishable. Dividers, and the outlines of card-sized controls such as a plant card in the catalogue or a garden tile on the home page, fall below the 3:1 minimum for non-text contrast. Smaller controls (fields, filters, chips, toggles, dropdowns) meet it, and so does every piece of text we have measured. The bloom strip's month cells are affected too: for a pale-flowered plant, the filled cell is faint against its background. At 400% browser zoom the app switches to its narrow, read-only layout, which removes the planner. That last one is a decision rather than unfinished work, and section 5 explains it.

2.1 Keyboard. The garden planner cannot be operated with a keyboard alone. See section 5. This is the one significant keyboard barrier.

2.4 Navigable. There is no "skip to content" link, so if you navigate by keyboard you tab through the header on each page. A screen reader can jump straight to the main region instead, but a sighted keyboard user cannot.

A note on the shared-garden password box. The password for a shared garden is typed into a field we deliberately do not mark as a password field, so that no browser or password manager offers to save a secret that belongs to a garden rather than to you. The cost is that a screen reader treats it as ordinary text and may read the characters back as you type. If this gets in your way, please tell us. We will take it into account the next time we look at this, though we cannot promise the decision would come out differently.

5. The planner, and what we have decided

The garden planner has to be operated with a mouse, or another pointing device such as a trackpad or a touchscreen. Placing a plant, moving it, resizing it, drawing a bed and adjusting a fence are all done by dragging on the plan, and none of them can be done with a keyboard alone.

This is a deliberate decision rather than something we have overlooked. Making a spatial design canvas work from the keyboard means designing a second way to draw a garden, not adding key handlers to the existing one, and we have decided not to build that. If we revisit the decision, this section will change with it.

A second, smaller decision belongs here too. Plants on the plan are drawn to scale, so a small plant is a small target, and many of them are below the 24-pixel minimum we hold the rest of the interface to. We have deliberately not clamped them to a minimum size: the size is the information on a to-scale plan, and enlarging small plants would make neighbours overlap and steal each other's clicks, so you would select the wrong plant rather than miss the one you wanted. The answer we rely on instead is the plan's own zoom, which goes to 14×.

A third decision, and it is the one behind the 400% zoom barrier. On a narrow screen Seasonry shows a reading layout: you can browse the catalogue, the calendar and your plant details, but you cannot edit a garden. A desktop browser at 400% zoom has the same narrow viewport as a phone, so it gets the same layout, and the planner is not there. We have decided that the narrow layout stays read-only. Separating the two, so that a zoomed desktop window keeps the editor while a phone does not, would mean re-deciding what every part of the app does at that width, and we do not think we could do it without breaking the phone experience for the people who use it today. So this barrier is settled rather than queued, and we would rather say that than leave it looking like something arriving soon. What we can suggest meanwhile is that browser zoom is not the only way to make the garden bigger: the plan has its own zoom, up to 14×, which enlarges the plan and its plants without narrowing the window, so it does not trip the layout over. It does not enlarge the surrounding text, and we would rather point you to the part that does help than imply it solves the whole problem.

We are not comfortable leaving any of this there, so:

• You can read your garden without the canvas. The plant panel lists every plant and object in every bed, as text, with names and sizes. A screen reader can enumerate the whole garden.
• Every plant on the plan is individually reachable by keyboard and announces itself, so you can review a plan by tabbing through it.

If the planner does not work for you, please write to us (section 7) and tell us what you were trying to do. We read every message, and what people tell us here shapes what we build next. We should say plainly that we cannot offer to draw a plan for you or to edit one on request.

6. How we assessed this

This statement is based on our own detailed internal accessibility audit, carried out in August 2026 against WCAG 2.2 Level A and AA, covering every route in the application in both signed-in and signed-out states.

It has not been verified by a third party, and we have not carried out testing with screen-reader users. Both limit how much this statement can tell you.

7. Tell us about a barrier

If something in Seasonry does not work for you, we want to hear about it. Small things are worth reporting too.

Email: support@seasonry.app

Please tell us which page or feature, what you were trying to do, and what happened. If you use assistive technology, telling us which one helps a great deal.

We aim to reply within 30 days. If you are reporting something that stops you using a feature you have paid for, say so in your message: it helps us judge what to look at first.

Version history