IAccessible::accRole shouldn't expose weak ARIA roles

NEW
Unassigned

Status

()

Core
Disability Access APIs
6 years ago
6 years ago

People

(Reporter: surkov, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
<div role="log"> should result in 'div' string role rather than 'log' one.

David, agree?
I would be okay with that as long as we don't break anyone.
(Reporter)

Comment 2

6 years ago
(In reply to David Bolter [:davidb] from comment #1)
> I would be okay with that as long as we don't break anyone.

It seems it's another side of bug 765878 you filed recently. It's hard to say if we break anyone but it's unlikely. Those roles aren't accessible roles so it seems it's not reasonable to expose them via roles mechanism.
Yeah we should be able to fix both bugs at once.
(Reporter)

Comment 4

6 years ago
Thinking more we either should
1) map anything to accRole as we do now
2) or known roles only

It doesn't make more sense to filter abstract roles (bug 765878) than to filter misspellings for example both role="buton" and role="roletype" are both senseless from AT perspective. The same can applicable at some range to weak roles as well (this bug).

Mapping anything to accRole allows the AT to handle roles the browser don't know about. So it's extensible but not error prone approach. But it was used for a while and there's no complains (except the spec conflicts).

I suggest to mark this bug 788494 and bug 765878 as wontfix and rise a question to ARIA group.
You need to log in before you can comment on or make changes to this bug.