Why accessibility should be part of editorial quality
A journal can no longer assume that every reader will approach an article in the same way. Content needs to behave well on desktop, mobile and assistive contexts. XML JATS helps because it structures meaning before presentation.
What HTML5 gains from a structured source
- Clear heading hierarchy and logical article sections.
- Cleaner transformation of tables, figures and notes.
- Better adaptation across screen sizes.
- More reliable semantic structure for digital readers and tools.
Accessibility is not an add-on at the end
When accessibility is considered only after layout, teams often patch symptoms instead of solving structure. XML JATS makes it easier to build accessibility into the workflow by treating article logic, labels and metadata as first-order editorial material.
Publishing principle
Readable structure creates better digital experiences
Accessibility improvements tend to make content better for everyone, not only for edge cases. Cleaner HTML5 is also clearer, faster and easier to maintain.
Where journals benefit most
- Responsive article reading on web browsers.
- Improved consistency between article sections and metadata.
- Cleaner publishing for mobile and institutional access contexts.
- Better editorial control over captions, notes and structured content blocks.
What we check in practice
- Heading logic and section order.
- Figure and table relationships.
- Alternative text opportunities and caption quality.
- Output behavior in responsive HTML5.
Conclusion
Accessibility and HTML5 are not side benefits of XML JATS. They are central outcomes of a better-structured editorial workflow and a stronger publishing standard overall.