Accessibility

01Our commitment

We aim to meet WCAG 2.1 Level AA across Inkrafted (see the docs repo's UI_GUIDELINES.md), and we treat an accessibility barrier as a bug with the same priority as a broken payment. The reader is the part we hold to the highest standard, because it's where people spend hours.

02Reading experience

Every reading control is intended to work without a mouse and without sighted guidance.

• Adjustable type size, line height and margins, plus light, sepia and dark themes.
• Full keyboard navigation for the in-app reader.
• Reduced-motion support that removes page transitions and animated progress.

03Screen readers

We plan to test with VoiceOver on macOS and iOS, NVDA on Windows and TalkBack on Android. Chapter structure is exposed as real headings and landmarks.

04What we ask of authors

Submission validation checks accessibility basics before a book can be sent for review.

• Alternative text for meaningful images, including maps and diagrams.
• A real table of contents with correctly nested heading levels.
• Text as text, not as images of text, and no colour-only meaning.

05Known gaps

We're honest about what's not built yet — this page will be updated as the reader and author tools ship.

• The in-app reader itself doesn't exist yet — it's planned for a later stage of the build (see the docs repo's ROADMAP.md).
• Automated accessibility validation for submissions isn't built yet.

06Report a barrier

Email access@inkrafted.com or use the contact form and choose accessibility feedback. We aim to acknowledge within two working days.