Open Bug 636158 Opened 14 years ago Updated 1 year ago

duplicated accessible states: sensitive and enabled, plus reverse unavailable

Categories

(Core :: Disability Access APIs, task)

Product:
Core
Component:
Disability Access APIs
Type:
task

Tracking

()

People

(Reporter: tbsaunde, Unassigned)

References

(Blocks 2 open bugs)

Details

User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b12pre) Gecko/20110222 Firefox/4.0b12pre Build Identifier: spun off from bug 634218 comment 18 we have to states for accessible objects sensitive and enabled which we currently treat as the same. ATk considers these states to be distinct, describing enabled as reflecting something in the application and sensitive as can react to user input. I don't believe IA2 / msaa defines these states. We should either get rid of the dupplicate state, or use them differently. Reproducible: Always
Summary: dupplicated accessible states sensitive and enabled → duplicated accessible states: sensitive and enabled
Severity: normal → S3

Enabled and sensitive are also set if unavailable is not set. Aside from the redundancy, this also makes it difficult to know which event to listen for or fire without diving into the code. We may also be firing redundant and/or inconsistent events.

Blocks: cleana11y
Severity: S3 → --
Type: defect → task
Summary: duplicated accessible states: sensitive and enabled → duplicated accessible states: sensitive and enabled, plus reverse unavailable
See Also: → 1898654
You need to log in before you can comment on or make changes to this bug.