Jukka said:
Don't take my word for it:
<URL:
http://www.access-matters.com/2005/03/27/111-alt-text-for-custom-list-markers/>
The fact that their scenerio uses image markers coded in HTML isn't
really relevant. Their test page still uses list markup and hides the
marker with list-style-type:none. Virtually all comments agree than
using list markup alone is enough.
This is a fantastic site for real-life web accessibility issues, BTW.
Actual screen reader users input a lot to the site. It's much more
informative than webaim.org, which seems rather stagnant.
foo bar zap zip zap zup ump
Are there seven links, or less?
If it were 7 links, JAWS would read this as:
“List with 7 items foo bar zap zip zap zup ump list end”
with a slight pause after each list item. There is link to a sample
recording of JAWS reading such a list on the above page. It ignores the
bullet marker whether it is shown on screen or not, but does use the
markup to identify it as a list. Window-Eyes also identifies lists from
the markup.
Not all screen readers behave this same way, but JAWS is the most-used
reader so I'd tend to keep it in mind first. I think it's up to the
individual to decide whether to cater to readers that perform less well
than JAWS. To me, it's the same issue as dealing with graphical browsers
that don't handle CSS well. It's likely a waste time trying to
accomodate a tiny percent (even less than 1%?) of your visitors that may
be using a deficient UA. YMMV, of course.