W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2014

Re: HTML5 DL Element vs. WCAG 2.0 Success Criteria

From: Sailesh Panchang <sailesh.panchang@deque.com>
Date: Fri, 7 Feb 2014 10:01:02 -0500
Message-ID: <CAJi9CqrNHHsdThit8Bu8iTBR4hasBokVO7t-RnNOKLXht8QD9Q@mail.gmail.com>
To: w3c-wai-ig@w3.org
All,
I filed bug# 3858 on nvaccess.org
Hopefully NVDA will implement the fixes as suggested.
Regards,
Sailesh


On 2/7/14, Jan Eric Hellbusch <hellbusch@2bweb.de> wrote:
> Thanks, Ramón,
>
>> Definition lists are not accessibility supported. Period.
>
> As a screen reader user I have always thought of definition lists as bad
> web
> design. I use JAWS and of course it is the way JAWS deals with definition
> lists. My usual way of navigating through content ist with Ctrl+arrow keys
> and when it komes to definition lists, JAWS will join the DD with the
> following DT and not the DT with its following DDs. I am running JAWS 13
> with IE11 here and it is still that way.
>
> [...]
>
>> I admit that tables might not be the best solution and that they look
>> "ugly" in terms of semantics, but they are quite more accessibility
>> supported and far more easy to understand. Even simple <ul> or <ol>
>> lists have better support; at least the screen readers announce a
>> "nesting level" that conveys an extra piece of "relationship".
>
> You get the nesting levels with DL as well.
>
> Tables are a lot easier to use in a screen reader than DL for 2 column
> data.
> In some situations it might be semantically prettier to use DL, but what
> counts is how users can deal with code.
>
> Jan
>
>
> --
> Jan Eric Hellbusch
> Tel.: +49 (231) 33005825 oder +49 (163) 3369925
> Accessibility-Beratung: http://2bweb.de
> Blog: www.chemnitzer-14.de
> Bücher, Artikel: www.barrierefreies-webdesign.de
>
>
>
>
>
Received on Friday, 7 February 2014 15:01:34 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:50 UTC