Why Good Markup Matters for All Users
summary
Shows concrete code comparisons: anchor vs span, anchor + tabindex/role, native button vs anchor-with-role, textarea vs contenteditable div, and how many extra attributes ARIA needs to match native behavior. Argues use native elements where possible, uses the W3C Authoring Practices Guide and live examples, and discusses the password-role proposal, datepicker styling limits, and tabs complexity tested with WordPress users — practical, code-focused advice and progressive-enhancement guidance.
AI-written summary · about
chapters (11)
- 0:00Start
- 8:03span class="link"
- 9:05So what is a link?
- 12:42So what is a button?
- 16:40So what is a textarea?
- 21:29If this is a typical layout
- 22:28Then why isn't this typical markup?
- 23:29function position
- 24:29Why is there ARIA?
- 28:20Native vs. ARIA
- 29:08Authoring Practices Guide
related talks
11mIt's the Markup that Matters
28mHumanizing The Markup Language: Thoughtful Semantics for Better Web Experiences
33mIt's the markup that matters
34mHTML Best Practice
28mDeveloper's Guide to Accessibility Mechanics
33mMarkup matters
27mMaking Interactions Accessible to All Users
25mBe an ally! In the battle for an inclusive and accessible internet!