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.

Owner responsibilities

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

Testing approach

Automated regression tests are necessary but insufficient. Releases also require manual keyboard, focus, zoom, narrow-screen reflow, contrast, reduced-motion, and representative screen-reader checks. Any conformance assessment must record its scope, date, environment, and unresolved limitations.

Known limitations

Dabbily does not currently claim independently verified WCAG 2.2 Level AA conformance. 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.

Contact

Email dabbilytheblogger@gmail.com.