ARIA Is Not Duct Tape
Use ARIA to describe real component behavior, not to patch over missing HTML, keyboard support, labels, focus, or state.
Tommy Truong
Button vs Link
Use buttons for actions and links for navigation so people can predict what will happen before they activate a control.
Name, Role, and Value
Check whether custom controls expose what they are called, what they are, and what state they are in before ARIA becomes guesswork.
Color Contrast
Check whether text, icons, controls, and meaningful visual boundaries are easy to see before contrast becomes a late review finding.
Headings and Page Structure
A practical Field Guide page about using headings to make screens easier to scan, navigate, and review.
Accessible Names
A practical Field Guide page about how controls get the names people hear, see, speak, and navigate by.
Link Text and Button Labels
A practical Field Guide page about writing link text and button labels that make sense before someone activates them.
Native HTML First
A practical Field Guide page about starting with built-in HTML elements before reaching for custom components or ARIA.
How to Review a Web App for Accessibility for the First Time
A practical first-pass guide for reviewing a real web app screen before accessibility issues become late rework.
Vendor Accessibility Questions Checklist
A practical checklist for asking vendors what their accessibility evidence actually covers.
