We want SmartKDP to be usable by as many publishers as possible, including people who use screen readers, keyboard navigation, or magnification.
This statement is honest about where we are rather than aspirational. An accessibility statement that claims full conformance when the product has known gaps is worse than none, because it tells someone the barrier they just hit does not exist.
Our target
We are working towards WCAG 2.1 Level AA. We are not there across the whole product yet.
What conforms today
The marketing site, the free tools, the blog, and the sign-in and account pages are built to meet Level AA. Specifically:
- Semantic HTML with proper heading structure and landmarks.
- All functionality reachable by keyboard, with visible focus indicators.
- Colour contrast meeting AA ratios in both light and dark themes.
- Text that reflows and remains readable when zoomed to 200%.
- Form fields with associated labels, and errors announced rather than only shown in colour.
- Images carry alternative text; decorative graphics are hidden from assistive technology.
- A dark theme that follows your system preference, and a manual override.
Known gaps
The canvas editor is our significant gap. The puzzle book editor renders onto a graphics canvas for performance, and a canvas is opaque to screen readers by nature: the elements on the page are drawn pixels, not DOM nodes an assistive technology can read or focus.
Today the editor's surrounding interface — the toolbars, panels, menus, and dialogs — is keyboard-navigable and labelled, but direct manipulation of objects on the canvas is not usable with a screen reader, and some canvas interactions require a pointing device.
We are not going to pretend this is a small thing. We consider it a real limitation and are working on it: an accessible object list that exposes canvas content as a navigable, editable tree is the approach we intend to take.
Other known items:
- Some exported PDFs do not yet carry a full tagged-document structure.
- A small number of older interface components have not been re-audited since a redesign.
Alternatives while we improve
If the canvas editor is not usable for you, please email us. Depending on what you are trying to do we can often help directly — including generating and exporting puzzle sets on your behalf so you are not blocked from publishing.
Assistive technologies we test with
We test with recent versions of VoiceOver on macOS and iOS, NVDA on Windows, keyboard-only navigation, and browser zoom. Coverage is manual and not exhaustive.
Tell us about a barrier
If something on SmartKDP blocks you, we want to know — it is the fastest route to getting it fixed.
Email support@smartkdp.com with what you were trying to do, the page you were on, and the assistive technology and browser you use. We aim to respond within one business day and will tell you honestly whether a fix is quick or a longer piece of work.
Feedback and enforcement
If you are not satisfied with our response, email support@smartkdp.com and we will escalate it internally. We would much rather resolve an accessibility complaint directly than have you pursue it elsewhere, but nothing here removes any legal right you have.
Review
We review this statement whenever the product changes materially, and at least once a year.