Dirtbag aims to be usable with a keyboard, screen reader, browser defaults, and assistive technologies before adding visual design.
Accessibility commitments
- Each page or post has one primary H1.
- A skip link targets the main content.
- Primary and footer navigation are labelled.
- Native HTML elements are preferred over custom controls.
- Disclosure content uses
detailsandsummarywhere possible. - Theme-authored JavaScript is avoided in version one.
Content guidelines
- Use headings in order without skipping levels.
- Write descriptive link text.
- Use tables only for tabular data.
- Add alt text for informative images and empty alt text for decorative images.
- Do not rely on colour alone to communicate meaning.
Accessible table sample
| Check | Expectation |
|---|---|
| Keyboard | All links and controls can be reached and used. |
| Headings | One H1, then logical H2/H3 sections. |
| Images | Alt text matches image purpose. |
Known limitations
User content and user-selected colours can introduce accessibility issues that the theme cannot fully prevent.
The Dirtbag CSS and JS KISS rule
Dirtbag does not write its own frontend CSS or JavaScript. WordPress core CSS and JavaScript are allowed when core blocks need them to render, line up, open, close, or stay accessible.
That means Row, Group, Navigation, Gallery, Media & Text, Search, and other core blocks can use the tools WordPress already ships. Dirtbag does not pack extra tools for a trip around the block.