On 5/2/09 23:17, Sandy wrote:
> Do screen readers not read generated list counters?
JAWS and Window-Eyes do not currently read text inserted with the
"content" property, although they do reflect list-style-type values.
> How would you let a screen reader know that you are in a list if you are
> using real numbers?
[snip]
> Is there another reason than accessibility that numbers as real text are
> what we need?
Well, if the numbers are part of the content (e.g. certain legal
documents), then they belong in the content layer (HTML) not the
skinning layer (CSS).
Remember a user isn't necessarily seeing your skin; they might be
applying their own CSS or viewing with a user agent that doesn't support
CSS.
There's no satisfying way of doing this, but the following are all
viable approaches:
<ul>
<li>1. foo</li>
<li>2. bar</li>
</ul>
<p>1. foo</p>
<p>2. bar</p>
<dl>
<dt>1.</dt>
<dd>foo</dd>
<dt>2.</dt>
<dd>bar</dd>
</dl>
<h2>1.</h2>
<p>foo</p>
<h2>2.</h2>
<p>baz</p>
Personally, I'd normally go for the first option.
I would avoid:
<ol>
<li>1. foo</li>
<li>2. bar</li>
</ol>
since you could end up with the user being presented a confusing
double-numbering of items (once from the "ol" and once from the text
content of the "li").
--
Benjamin Hawkes-Lewis
______________________________________________________________________
css-discuss [[email protected]]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
