Markup
Structure
Semantic header, navigation, main, section, article, table, form, dialog, and footer landmarks.
Accessibility
Accessibility is part of technical quality
The theme uses semantic landmarks, keyboard-operable navigation, visible focus, responsive layouts, reduced-motion support, and system fonts. Accessibility still depends on the content and plugins added by the site operator.
EnterpriseGovernmentPartners
Accessibility model
Theme-level practices
Accessibility is treated as an operating requirement rather than a decorative audit item.
Input
Keyboard
Skip link, keyboard-operable menus and dialogs, logical focus, and visible focus indicators.
Layout
Responsive content
Layouts reflow, controls remain touch-sized, and long labels are allowed to wrap.
Perception
Motion and contrast
Reduced-motion preferences are respected and interface states use more than color alone.
Reliability
Local assets
System fonts and first-party assets reduce blocking and unexpected third-party interfaces.
Editorial
Content responsibility
Editors must preserve heading order, link meaning, alt text, captions, table headers, and plain language.
Feedback and maintenance
Report an accessibility barrier
A useful report includes the page, task, browser, assistive technology, viewport or zoom, and what prevented completion.
- Page address or title
- Intended task
- Observed barrier
- Browser and operating system
- Assistive technology if used
- Preferred contact method
Start with a bounded decision
Accessibility issues should produce a tracked correction.
Use the contact path and include public-safe reproduction details.