Bug 148646 - AX: AXGroup role assigned to div with tabindex of 0 or -1
Summary: AX: AXGroup role assigned to div with tabindex of 0 or -1
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Accessibility (show other bugs)
Version: WebKit Nightly Build
Hardware: Mac OS X 10.10
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2015-08-31 14:31 PDT by Mark Sadecki
Modified: 2015-09-02 09:39 PDT (History)
2 users (show)

See Also:


Attachments
Demonstrates unexpected role assignment when tabindex of 0 or -1 is added to div (2.21 KB, text/html)
2015-08-31 14:33 PDT, Mark Sadecki
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Sadecki 2015-08-31 14:31:48 PDT
Any div with a tabindex value of 0 or 1 gets an accessibilityRole of Group. 
AXWebArea is expected.

See test file for example and steps to replicate.
Comment 1 Radar WebKit Bug Importer 2015-08-31 14:32:39 PDT
<rdar://problem/22506647>
Comment 2 Mark Sadecki 2015-08-31 14:33:04 PDT
Created attachment 260318 [details]
Demonstrates unexpected role assignment when tabindex of 0 or -1 is added to div
Comment 3 chris fleizach 2015-09-02 09:39:35 PDT
This is actually expected behavior. the idea is that if someone has made an object keyboard focusable, we always want to make sure that it appears in the AX hierarchy so VoiceOver can focus on it.

without more info about what kind of object it is, it becomes an AXGroup. you can assign another role="" to that object if you need