E-mail List Archives
Usability vs. Accessibility
From: Kelly Lupo
Date: Mar 21, 2016 10:55AM
- Next message: KP: "Re: Usability vs. Accessibility"
- Previous message: Joe Chidzik: "Re: WCAG Violation for use of tabindex=0 on staticelements."
- Next message in Thread: KP: "Re: Usability vs. Accessibility"
- Previous message in Thread: None
- View all messages in this Thread
I did not want to hijack the tabindex thread, so I figured I'd start a new
one... It was mentioned at one point that there was more of a usability
issue than an accessibility one in one of the examples.
I need to explicitly define the two for an unrelated project, but I find
that I am having a hard time doing so without confusing myself (let alone
the person reading I imagine!). How do ya'll explain this difference to
someone who has little to no experience in web accessibility?
I had started with the analogy of:
- Being directed to a 404 - 'page not found' or having makes the content
inaccessible (thus also unusable),
- Whereas a page in a language you do not speak, and does not provide
pictures or a translation widget, renders the page unusable because you can
access the page - it is just harder to access the content (IE: you need a
translator of some kind).
...And then I got confused by reading other sources which seemed to say the
opposite. Affirmation or dissent and correction would be much appreciated!
Thank you in advance,
Kelly
- Next message: KP: "Re: Usability vs. Accessibility"
- Previous message: Joe Chidzik: "Re: WCAG Violation for use of tabindex=0 on staticelements."
- Next message in Thread: KP: "Re: Usability vs. Accessibility"
- Previous message in Thread: None
- View all messages in this Thread