A comprehensive overview of The Web Content Accessibility Guidelines (WCAG)
Key Takeaways:
1. Inclusive design fosters inclusivity for all users.
2. Accessibility benefits everyone, including you and me.
3. Accessible design principles are applicable across various fields, from web design to game development, mobile app development, hardware with user interfaces, and even poster design. Accessibility knows no bounds!
3. “Web accessibility means
that websites, tools, and
technologies are
designed and developed
so people with disabilities
can use them.”
-W3C WAI Introduction to Web Accessibility
https://www.crestdatasys.com/blogs/web-accessib
ility-how-to-enable-access-for-everyone/ img src
4. 15%
According to WHO:
about
Of the world
identifies as having
a disability.
https://easterseals.ca/en/disabil
ity-in-canada-facts-figures/
https://www.crestdatasys.com/blogs/web-accessib
ility-how-to-enable-access-for-everyone/ img src
13. Which button one is red?
Don’t convey information with just colors.
https://www.theodinproject.com/lessons/node-path-advanced-html-and-css-accessible-colors
14. Which button one is red?
Don’t convey information with just colors.
https://www.theodinproject.com/lessons/node-path-advanced-html-and-css-accessible-colors
16. Responsive Across
Devices
https://www.w3.org/WAI/WCAG21/
Understanding/target-size.html
How to make a website responsive is
another topic I won’t cover today.
Done through css by using a mix of media
queries, flex/grid, responsive font size,
responsive images, meta-viewport,
avoiding fixed width/height etc.
Chrome dev tool is a great way to check if
your website is responsive across all
devices without actually using those
devices.
20. Importance of Semantic HTML
Sections your website.
More readable HTML code.
Provides meaning and
context.
Default focusable by
keyboard navigation.
Helps Section a
Website:
● <header>
● <main>
● <section>
● <footer>
● <aside>
● <nav>
● <form>
● <h1> … <h6>
Provides content and
function accessible by
keyboard:
● <button>
● <p>
Semantically neutral
(not picked up by
screen readers):
● <div>
● <span>
21. Importance of Semantic HTML in keyboard navigation
https://youtu.be/vAAzdi1xuUY?list=PLNYkxOF6rcICWx0C9LVWWVqvHlYJyqw7g&t=83
22. Divs and Spans are Not Focusable!
https://www.theodinproject.com/lessons/node-pat
h-advanced-html-and-css-semantic-html
28. Avoid having important information on images
Screen readers cannot read text on an image.
Google translate cannot translate text on an
image.
Text on image should be decorational. It’s nice
to have them there but it shouldn’t be essential
to know.
31. Meaningful text - Links
Rules:
1. Text content of <a> should briefly
indicate where the link redirects
you.
2. If a link opens or downloads a file:
indicate the type and file size.
3. If a link takes you to a new tab, you
should indicate to the user that it
does so.
32. Meaningful text - Useful Error Messages
https://neal.fun/password-game/
Good!
Bad!
36. Aria-labels
Overrides native HTML labels and
provides descriptive text instead.
Also useful in hiding elements from tab
focus with aria-hidden=‘true’.
Only modifies semantic context:
- can’t change tab order
- can’t make divs/spans focusable
https://www.youtube.com/watch?v=
9Irk7PIjHBE
37. Additional Mentions
● Avoid Time Sensitive Tasks
● Don’t use blinking/flashing content or
colors.
● Don’t have distracting background
audio, or at least provide a way to
turn it off.
● Always have ways to adjust volume
on audio media.
● Provide multiple ways to find the
same content
○ Search bar
○ Nav bar
○ Assistive chat bot