✳flâneur — a map of the web's best reading
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
Explore this link on the map →saved by
related reading
- Say precisely what you mean.index.how
- Web Interface Guidelinesvercel.com
- What is Accessibility? — updated 2026 | IxDFinteraction-design.org
- Designing For Accessibility And Inclusion — Smashing Magazinesmashingmagazine.com
- aria-label is a code smell – Eric Baileyericwbailey.website
- Link Preview API & Service | Peekalinkpeekalink.io
- gabbi soonggabbisoong.com
- The Rhetoric of the Hyperlink — Ribbonfarmribbonfarm.com
- The controversy of accessible type | by Alex C | Queer Design Club | Mediummedium.com
- Annamarley-surprise.netlify.app
- netcs.cornell.edu
- Accessibility Audit Toolvercel.com