Closed Bug 1218493 Opened 9 years ago Closed 9 years ago

NVDA does not read list items from expanded droplist

Categories

(Core :: Disability Access APIs, defect)

41 Branch
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: kira.reoutt, Unassigned)

Details

(Keywords: access)

Attachments

(1 file)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.71 Safari/537.36

Steps to reproduce:

Tabbed to an arrow, pressed Enter to open hidden droplist, droplist displayed, and then tabbed to each item in the list.


Actual results:

When the drop-list opened, NVDA read that the list was expanded (which is correct behavior), but upon tab to each item, NVDA did not read anything.


Expected results:

NVDA should have read each item in the list.
As a work around, I have tried:
- the technique of moving the li children off the screen and then back (See: http://www.sitepoint.com/javascript-and-screen-readers/)  This doesn't work at all for FF and NVDA.  I think because the ul is set to display none initially via ember with an embedded style;  Attempted to move the ul children off the screen, then back, but that, too, did not work.

- added a <span> around the text in the li, positioned it off-screen, then on; similar to above, but doesn't work.

- added a list-style-type: disc as recommended here (http://www.456bereastreet.com/archive/201109/screen_readers_list_items_and_list-stylenone/); since some screen readers will not read the text without a list style type.  ("type none" seems to be interpreted as "don't read me")  However, this only works a little better with JAWS, but not at all with NVDA.

- I tried adding a title, that doesn't do anything

- the aria-selected attribute doesn't get the li's to be read

- the tabindex=0 also doesn't do anything to get the li to be read
Component: Untriaged → Disability Access APIs
Keywords: access
Product: Firefox → Core
A PNG is not useful for me because I cannot test your example. Note that tabbing to each list item is incorrect keyboard behavior. The list should only have one tabstop, the UL, which should get tabindex="0", and the children should all get IDs and be selected via the arrow up and down keys. The "focused"/selected item is managed via aria-activedescendant, which gets set to the individual ID of each item, along with aria-selected="true" (or "false" for the unselected ones). This patterns works in many auto-completes or drop downs across the web, so I don't see either Firefox or NVDA at fault here, rather authoring error. Closing as INVALID.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: