Support assistive tech and cognitive diversity
Use semantic HTML, ARIA only when necessary, and predictable focus order. Provide keyboard parity for every action and announce dynamic changes politely. Offer adjustable motion, text size, and density. Keep forms simple, labels explicit, and instructions persistent. Avoid relying solely on color or iconography. Break tasks into digestible steps, and allow people to revisit instructions without losing progress. Test with screen readers and neurodiverse participants, then fix what they tell you is broken, not just what is convenient.