Accessibility Coding Standards
.toc-jump { text-align: right; font-size: 12px; } .page .toc-heading { margin-top: -50px; padding-top: 50px !important; }
Topics
- HTML Semantics
- Heading structure
- Semantics for Controls
- Dynamic Content
- Color Contrast
- Links: underline or no underline?
- Keyboard Accessibility
- Images and Icons
Warning: This page has been moved here
Please do not edit this page.
These are standards that WordPress features should meet for accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) in order to be merged into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. All new or updated code released in WordPress must conform with the WCAGWCAG WCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/. 2.0 guidelines at level AA. These basic guidelines are intended for easy reference during development, but do not cover all possible accessibility issues.
In the Accessibility [...]