Visit for a surprise – Eric Bailey
ericwbailey.website · 1,097 words · saved by 1 readers
Could spoiling a joke be an accessibility issue? You better believe it.…
Visit for a surprise – Eric Bailey Skip to main content Home ➞ Writing Visit for a surprise Could spoiling a joke be an accessibility issue? You better believe it. Web Content Accessibility Guidelines Success Criterion 2.4.4: Link Purpose (In Context) instructs us to ensure that a link’s accessible name makes sense when separated from its surrounding context. It’s why “learn more about elephants” is a far more effective link name than “click here.” Providing instructive names for your interactive controls is really important. The practice allows everyone to quickly know what to expect when you
saved by
related reading
- Web Interface Guidelinesrauno.me
- Web Interface Guidelinesvercel.com
- Web Interface Guidelinesinterfaces.rauno.me
- aria-label is a code smell – Eric Baileyericwbailey.website
- Designing for Web Accessibility – Tips for Getting Startedw3.org
- What is Accessibility? — updated 2026 | IxDFinteraction-design.org
- Wishcessibility - Nic Channicchan.me
- Designing For Accessibility And Inclusion — Smashing Magazinesmashingmagazine.com
- 10 Usability Heuristics for User Interface Design - NN/Gnngroup.com
- Understanding Success Criterion 2.4.3 | Understanding WCAG 2.0w3.org
- The Design of This Websiteturntrout.com
- The Dangers of Surprising Codeparadigm.xyz