Re: HTML5 DL Element vs. WCAG 2.0 Success Criteria

Hi Steve, everyone--

This has been a very helpful discussion. To address your question, JAWS doesn't appear to read lists differently using control plus the arrow versus the arrow alone.

I've often wondered why it is invalid in lists to put text between <ul> and <li> since it is read in a more helpful way by JAWS (I haven't tried it in NVDA, W-E or VoiceOver). 

When a person presses "l" (as in "list), "<ul>Activities <li>Snorkeling</li><li>Swimming</li> </ul>" is read as "list of two items, snorkeling, bullet snorkeling bullet swimming", whereas Activities isn't read when it is outside of the unordered list element, i.e., "Activities<ul><li>etc."

It still isn't ideal, since I would think that navigating to lists using "l" would both announce the heading ("Activities") and give the number of items in the list ("two"). But to my mind it would be clearer.

Any idea why it is invalid and whether it could be a viable approach?

Mike






On Saturday, February 15, 2014 5:05 AM, Steve Faulkner <faulkner.steve@gmail.com> wrote:
 
hi Jan,



--

Regards

SteveF
HTML 5.1



On 15 February 2014 09:28, Jan Eric Hellbusch <hellbusch@2bweb.de> wrote:

Hi Steve,
>
>
>> Do AT convey the semantics as some would wish them to? probably not, but
>this
>> does not constitute a lack of 'accessibility support'.
>
>Announcing the number of list items is always confusing when nested lists
>are involved, because all items (instead of only the top level items) are
>counted. From a screenreader point of view DL lists are accessible, but they
>do not relay the visual information properly. The semantics are only a part
>of the problem.
>

unclear what you mean, what is the behaviour you get in DL's and what is the behaviour you expect?

where is it defined how the visual information should be relayed properly?


 

>As pointed out in a previous mail in this thread, they are not easy to
>navigate in screenreaders. Using Ctrl+arrow keyes DDs are grouped with the
>followings Dts instead of vice versa in JAWS.
>

it would be helpful to know what the Ctrl+arrow key is supposed to do in list avigation, I had a look in JAWS help and couldn't find it as a defined stroke combo for navigating lists (but it is defined for tables)

 

>Jan
>
>
>