Accessibility Statement · LessonSmith

Teaching is not a job you can do only with a mouse and perfect eyesight, and lesson planning should not be either. This page says what we have actually checked, what we have not, and what is known to be broken. It is written to be useful rather than reassuring, so it names problems we have not fixed yet.

1. The standard we aim at

We target Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. We are not claiming to meet it. Nobody outside this company has tested LessonSmith, so treat everything below as our own assessment of our own work.

2. The public site

These pages are the marketing pages, the pricing page, the legal pages, and sign-in and sign-up. As of the effective date above the following have been checked in a browser, not merely intended:

• A Skip to content link is the first thing the Tab key reaches on every page, and it moves keyboard focus into the main region rather than only scrolling to it.
• Every interactive element shows a visible focus outline, and tab order follows the order things appear on screen. Nothing uses a positive tabindex to jump the queue.
• Each page has one h1, headings descend in order without skipping a level, and the page is divided into header, navigation, main and footer regions a screen reader can jump between.
• Every link, button and form control has a name a screen reader can announce. Decorative icons are hidden from assistive technology instead of being read out as meaningless graphics.
• The site works in light and dark themes, and animation is dropped for anyone whose system asks to reduce motion.

3. The planning studio has not been audited

The studio is the signed-in application where you build lesson plans, schemes of work and the term calendar. It is a large, older piece of software with hand-built calendars, dialogs and menus, and it has never been audited for accessibility, by us or by anyone else.

A first pass over its structure found less wrong than we expected: the page declares its language, it has header, navigation and main regions, none of its 80 interactive controls is missing a name a screen reader can announce, and nothing forces itself to the front of the tab order. That is a floor, not a pass. What has not been checked is the part that matters most in an application this interactive: whether focus is handled correctly when its dialogs and menus open and close, whether the calendar grid can be operated by keyboard at all, and whether the reading order makes sense once a screen reader is actually driving it.

We have committed to a first accessibility audit of the studio by 10 August 2026. If you are reading this after that date and it still says the same thing, the audit has not happened and you should hold us to it.

4. Known barriers

Listed because we know about them, not because they are acceptable:

• The studio, in the terms of section 3: dialog and menu focus handling, keyboard operation of the calendar grid, and screen-reader reading order are all unverified. This is the biggest one, and it is the part of the product people spend their time in.
• Colour contrast has not been measured across every one of the studio's themes. The default light and dark themes are the ones we have looked at.
• There is no third-party audit and no VPAT. If your school or district needs one for procurement, tell us and we will say honestly where we are rather than produce a document we cannot stand behind.
• Lesson plans and schemes of work are drafts produced by an AI model. We do not check that the wording they generate meets any readability or accessibility standard for your students.

5. Reporting a barrier

Email support@lessonsmith.ai and describe what you were trying to do, what happened, and the browser or assistive technology you were using. A rough description is fine; you do not need to know the technical name for the problem.

We aim to reply within five working days. We cannot promise a fix by any particular date, and we would rather tell you that than promise one and miss it. If a barrier stops you finishing something, say so and we will look for a way to do it for you in the meantime.

6. If we do not resolve it

If our reply does not settle the matter, you can escalate under Kenya's Persons with Disabilities Act through the National Council for Persons with Disabilities, or through the equivalent body where you live. Nothing on this page limits any right you have under the law that applies to you.

Read together with the Terms of Use and the Support page.