E-mail List Archives
Re: controlling a CMS for access
From: McMorland, Gabriel C
Date: Aug 28, 2013 1:34PM
- Next message: Lucy Greco: "Re: controlling a CMS for access"
- Previous message: Lucy Greco: "Re: controlling a CMS for access"
- Next message in Thread: Lucy Greco: "Re: controlling a CMS for access"
- Previous message in Thread: Lucy Greco: "Re: controlling a CMS for access"
- View all messages in this Thread
Oh, good point. The idea that you might have missed something or that a feature might be inaccessible is such an important accessible design concept. I've often wished I had a word to sum up this concept. Do you have a word for this?
Users can lose time on a wild goose chase for phantom content they believe is missing, or misinterpret available information because they assume content is missing. I have also given up on tasks when I assumed they were inaccessible, only to later discover that I could complete the task but didn't have proper instructions or context.
With all that in mind, I never really paid attention to what level of heading tag I was reading. I always just jump from heading to heading to skim page content or get back to something that I need. You have a good point, though.
- Next message: Lucy Greco: "Re: controlling a CMS for access"
- Previous message: Lucy Greco: "Re: controlling a CMS for access"
- Next message in Thread: Lucy Greco: "Re: controlling a CMS for access"
- Previous message in Thread: Lucy Greco: "Re: controlling a CMS for access"
- View all messages in this Thread