WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: controlling a CMS for access

for

From: Lucy Greco
Date: Aug 28, 2013 1:40PM

I don't really have a single word for it but I think it follows in the can
a user get what they need in under 30 seconds rule. I do say a screen
reader user might take a minute but it's the same idea can you catch the
user and give them what they need to get them to stay on the page and
learn more or do they go some wear else thinking they missed it.
Lucia Greco
Web Access Analyst
IST-Campus Technology Services
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces


-----Original Message-----
From: <EMAIL REMOVED>
[mailto: <EMAIL REMOVED> ] On Behalf Of McMorland,
Gabriel C
Sent: Wednesday, August 28, 2013 12:34 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] controlling a CMS for access

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.


-----Original Message-----
From: <EMAIL REMOVED>
[mailto: <EMAIL REMOVED> ] On Behalf Of Lucy Greco
Sent: Wednesday, August 28, 2013 3:26 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] controlling a CMS for access

We always try to keep headers in order to keep the screen reader users
from hunting for what they might have missed. But mostly because we like
good semantic structure. I am also a screen reader user and I do find it a
little off setting when the first thing I hit on a page is a h3 or h5
witch yes does happen. I try and teach proper structure at least on the
home page to keep people from looking for what they might have missed. Yes
today it's not as important as it was say 5 years ago but I am stuck in my
old ways and don't think things should start at 4 or 5. I do not mind the
nab being at a 2 and then a 1 but starting a page at 3 always makes me
wonder. And then there is always the argument of the web search hits
smile Lucy Lucia Greco Web Access Analyst IST-Campus Technology Services
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces

-----Original Message-----
From: <EMAIL REMOVED>
[mailto: <EMAIL REMOVED> ] On Behalf Of McMorland,
Gabriel C
Sent: Wednesday, August 28, 2013 12:18 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] controlling a CMS for access

Who is affected by the out of order headers? Is it a visual experience
issue?

I'm a blind JAWS user, and I'm very interested in your anser.
messages to <EMAIL REMOVED>
messages to <EMAIL REMOVED>
messages to <EMAIL REMOVED>