Movatterモバイル変換


[0]ホーム

URL:


Skip to content
DEV Community
Log in Create account

DEV Community

Cover image for Principles of Web Accessibility
Alvaro Montoro
Alvaro MontoroSubscriber

Posted on • Originally published atalvaromontoro.com

     

Principles of Web Accessibility

Heydon Pickering recently shared some "Principles of Web Accessibility," a set of twelve high-level guidelines on how to approach web accessibility.

I highly recommend reading the whole thing –it's a short text–, but here's a summary of them if you want a quick "too long; didn't read" version:

💎 Perfection is the enemy: nothing will be 100% accessible, but you can make a real difference by making it just a little bit better.

➡️ By default or death: accessibility is not something to be added later to a complete product. An inaccessible product is an incomplete product.

⚖️ Parity is paramount: the goal is not to create "better experiences" but "comparable experiences" for different people.

📐 Design for implementation: accessibility shouldn't be an afterthought in the development process, it should be there since the early stages.

📊 Structure first: an intuitive interface that is well-structured and easy-to-use is better than a poorly-structured interface with no discrete errors.

💬 Use your words: develop your writing and editing skills or include writers and editors in your process. What is written is as important as how it's written.

🛠️ Tools are not identities: disabilities are not uniform. Don't design for a single person or user, design to support the capabilities of the assistive software.

↕️ Less is less: don't overdo it! Reducing complexities –keeping things simple– not only reduces errors, it also improves comprehension.

💰 Get paid: accessibility is a job in itself. Include it in your role, be valued, and get recognized for it. Don't let people diminish its (your) importance.

🎣 Fishing, not fish: working on accessibility goes beyond solving specific problems. Set the stage and structure to facilitate it.

🏆 No points for performance: Companies tend to prioritize looking accessible over being accessible. Demand action and not only performance.

👿 Let evil rot: there is plenty of inaccessibility; protect your reputation and mental health, and prioritize working with receptive companies and projects.


What do you think? Anything that you would add or change?

Top comments(1)

Subscribe
pic
Create template

Templates let you quickly answer FAQs or store snippets for re-use.

Dismiss
CollapseExpand
 
contrastchecker profile image
Contrast Checker
Ensure your website is accessible with our free Color Contrast Checker. Test text and background contrast, meet WCAG standards, and improve readability for all users effortlessly.
  • Joined

Great summary of Heydon Pickering’s principles! "By default or death" really resonates. Accessibility isn’t a feature, it’s a foundation. Tools like ouronline contrast checker help with small but crucial steps, like ensuring readable color contrast. Love the focus on practical, real-world impact over just “looking accessible.” Thanks for sharing, Alvaro!

Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment'spermalink.

For further actions, you may consider blocking this person and/orreporting abuse

CSS aficionado ⊆ Web Developer ⊆ Software Developer ⊆ Person(He/Him)
  • Location
    Austin, TX
  • Work
    UI Manager / CSS Aficionado
  • Joined

More fromAlvaro Montoro

DEV Community

We're a place where coders share, stay up-to-date and grow their careers.

Log in Create account

[8]ページ先頭

©2009-2025 Movatter.jp