Inclusion is part of the publishing model.
Litera targets WCAG 2.2 AA for its workspace and treats accessible learner output as a release requirement.
Designed for authors and learners.
Accessible output starts with an authoring experience that makes structure, language, narration and alternatives easy to understand.
Authoring with awareness
Fix barriers while the work is still fluid.
The workspace makes reading order, alternatives, language and interaction status visible beside the content. Guidance arrives where teams can act on it, not in a report after release.
Release confidence
Quality is visible before publishing.
Teams see actionable checks in the same context where they write and review, reducing late surprises.
- Reading order and heading structure
- Text alternatives for meaningful media
- Narration status by language
- Keyboard and responsive presentation
Perceivable
Text, media and narration offer meaningful alternatives.
Operable
Keyboard routes and clear focus support different ways of working.
Understandable
Consistent language and feedback reduce cognitive effort.
Accessibility questions, answered.
Open a question to learn how Litera fits into real publishing work.
Does Litera guarantee conformance automatically?
No automated system can replace expert and user review. Litera makes requirements visible, catches common issues and supports evidence-based human approval.
Is keyboard access considered in the workspace?
Yes. Authoring actions are designed to have non-pointer routes and visible focus behaviour.
How are images handled?
Meaningful media can carry reviewable text alternatives, while decorative elements can be identified appropriately.
What about smaller screens?
Content is designed to reflow and remain usable across phones, tablets and larger displays.
Can accessibility block a release?
Required alternatives, associations and other quality evidence can be configured as visible release gates.