Resources
What does good accessible markup look like when you build it from the beginning?
Good Markup Resources
Start with native HTML when it already provides the semantics and behavior you need.
- Semantic HTML MDN explains how headings, landmarks, lists, buttons, links, and forms provide useful structure and native behavior.
- Forms and labels W3C WAI covers <label>, fieldset and legend, accessible names, instructions, validation, and error feedback.
- Buttons and links Links go somewhere; buttons do something: use native <a href> and <button> elements for their intended purposes.
- Images and alternative text Use the W3C WAI decision tree to choose appropriate alt text, including empty alt text for decorative images.
- Keyboard and focus MDN explains keyboard operability, visible focus, logical focus order, and why native controls help.
- ARIA: read this first W3C explains the responsibilities that come with ARIA: No ARIA is better than bad ARIA.