Accessibility

What the framework provides

The trusted renderer uses semantic HyperText Markup Language (HTML), a logical heading structure, landmarks, labelled search, keyboard-operable controls, visible focus, reflow-friendly layouts, restrained motion, and escaped structured content.

Article images require alternative text. Code examples include a programmatic label and remain keyboard-scrollable when their width exceeds the reading column.

What publication owners must do

Framework safeguards do not make every article, custom template, uploaded image, or deployment conformant. Publication owners remain responsible for meaningful alternative text, plain-language instructions, accurate headings and link names, media alternatives, colour choices, and testing any trusted custom code.

Testing approach

Automated regression tests are necessary but insufficient. Each release should also receive manual keyboard, focus, zoom, narrow-screen reflow, contrast, reduced-motion, and representative screen-reader checks. The scope, date, environment, and unresolved limitations of any conformance assessment must be recorded.

Known limitations

The project does not currently claim independently verified WCAG 2.2 Level AA conformance for isnta.com. Trusted administrators can publish raw HTML, Cascading Style Sheets (CSS), and JavaScript in full-code templates; that capability can defeat built-in accessibility safeguards and requires its own review.

Report a problem

Email accessibility@isnta.com with the affected address, the problem encountered, the assistive technology or browser used when relevant, and any suggested resolution. Do not include passwords or other sensitive information.