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: Frank M. Palinkas <fmpalinkas@gmail.com>
Date: Fri, 14 Feb 2014 14:57:25 -0800
Message-ID: <CAN6dTQWGUqkGZLGf+c91O38WTjvJDZcM33PACvxn1GCU0mTO1Q@mail.gmail.com>
To: Steve Faulkner <faulkner.steve@gmail.com>
Cc: Duff Johnson <duff@duff-johnson.com>, Sailesh Panchang <sailesh.panchang@deque.com>, WAI Interest Group <w3c-wai-ig@w3.org>
Just curious...

Regarding AT's handling of lists, especially <dl>:

In any of the ATs, is there a switch that a user can turn on to enhance the
list discovery and announcement process, outside of the default?

I believe a "switch" is available to turn the @title attribute on and off,
so therefore my question.

Kind regards,

Frank M. Palinkas
Senior Technical Writer
Quixey, Inc., Mountain View, California
Mobile: +1 650 248 5315
Web Accessibility and Standards tutorials:
http://dev.opera.com/author/947856


On Fri, Feb 14, 2014 at 2:32 PM, Steve Faulkner <faulkner.steve@gmail.com>wrote:

> "To clarify; so <dl>, <dt> and <dd> are not presently
> accessibility-supported by JAWS or NVDA? Dare I even ask about VoiceOver?"
>
> I would seriously question this, as what the 'accessibility support'
> requirement is for these elements is not defined anywhere.  What is clear
> is that both JAWS and VoiceOver identify definition lists as definition
> lists and allow users to access the items. Some browsers (Safari and
> Firefox) expose the definition list semantics via accessibility APIs
>
> Do AT convey the semantics as some would wish them to? probably not, but
> this does not constitute a lack of 'accessibility support'.
>
> --
>
> Regards
>
> SteveF
> HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>
>
>
> On 14 February 2014 22:08, Duff Johnson <duff@duff-johnson.com> wrote:
>
>> Sailesh,
>>
>> To clarify; so <dl>, <dt> and <dd> are not presently
>> accessibility-supported by JAWS or NVDA? Dare I even ask about VoiceOver?
>>
>> If so, then the only types of lists with accessibility support in HTML at
>> this time are Ordered and Unordered?
>>
>> 6 years after publication of WCAG 2.0?
>>
>> I'm not trying to rub it in, but it has to be said:
>>
>> Ouch.
>>
>> Perhaps screen-readers should prefix: "Label" before <dt> content and
>> "list item" or "content" before the <dd>. The model needs to be as generic
>> as possible, or so it seems to me…
>>
>> Duff.
>>
>>
>> On Feb 14, 2014, at 3:51 PM, Sailesh Panchang <sailesh.panchang@deque.com>
>> wrote:
>>
>> > I suggested this to FS to improve support for DL:
>> > "As one navigates a definition  list using "I", JAWS should perhaps
>> > prefix the  word "Term" before the contents of the DT element.
>> > When a DT has more than one DD elements associated with it, JAWS
>> > should  say "Term with <n> definitions" before the value of the DT
>> > element, where 'n' corresponds to count of associated DD elements."
>> >
>> > The response I got:
>> > The definition list issue was discussed with product management and
>> > development, and it was agreed that it is a good idea.
>> > It has been added it to our developer data base as a feature
>> enhancement action.
>> >
>> > I have also filed a bug for NVDA and hoping for  a response.
>> > Thanks,
>> > Sailesh
>>
>>
>
Received on Friday, 14 February 2014 22:58:32 UTC

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