W3C home > Mailing lists > Public > public-html-a11y@w3.org > September 2010

[Bug 10450] Allow lists to be used as menus or tab sets

From: <bugzilla@jessica.w3.org>
Date: Tue, 14 Sep 2010 14:56:16 +0000
To: public-html-a11y@w3.org
Message-Id: <E1OvWvg-0003Kd-7m@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10450


Martin Kliehm <martin.kliehm@namics.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
                 CC|                            |martin.kliehm@namics.com
         Resolution|FIXED                       |




--- Comment #4 from Martin Kliehm <martin.kliehm@namics.com>  2010-09-14 14:56:15 ---
The reason why <li role="presentation"> is required is the following use case:

Take a tab navigation, where <ul role="tablist">. The current implementation in
some browsers only supports role="tab" on immediate children of the tablist,
i.e. <li role="tab">.

If the author chooses to apply the role to a deeper element, like

<li><a role="tab">Tabitem</a></li>

(feel free to add more presentational spans), then the element that has the tab
role isn't recognized as a child element of tablist. Thus the "tab" role is not
announced in screenreaders.

However,

<li role="presentation"><a role="tab">Tabitem</a></li>

has the desired effect. So it is imperative that role="presentation" is
allowed, otherwise it will break screenreader support.

See the website of Deutsche Bahn (German railways) with several billion yearly
visitors as use case: http://www.bahn.de

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 14 September 2010 14:56:22 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:14 UTC