929307 - [AccessFu] Handle disabled elements when uttering.

Status: RESOLVED INVALID

(Core :: Disability Access APIs, defect)

Description

[Yura Zenevich [:yzen] (please use "needinfo")]

I found this issue when testing the phone app, in case where no numbers are entered, the add contact button is disabled (or even just have a class 'disabled'). We need to handle this so it is less confusing to the screen reader user.

Comment 1

[Yura Zenevich [:yzen] (please use "needinfo")]

Marco, would you know what's the most elegant way to go about this? Would it be mentioning that it is disabled?

Comment 2

[Marco Zehe (:MarcoZ)]

There are actually two parts of a fix for this bug. One is to make sure we utter the state if an item is disabled. The word "disabled" or "Greyed" should be used, whichever you prefer.

The second part is in Gaia: The item should be disabled. So if no HTML5 @disabled attribute (without a value) can be used, which is the preferred way, you should add aria-disabled="true" as an attribute when the item is disabled, and remove aria-disabled altogether if not. DO NOT simply rely on a class "disabled" to be present. We have correct semantics for that and should use either HTML5's @disabled attribute or aria-disabled as a fall-back if the other doesn't work.

Comment 3

[Yura Zenevich [:yzen] (please use "needinfo")]

ATM, if aria-disabled is true, AccessFu reports 'unavailable' for example:

'Add contact unavailable button'

Comment 4

[Eitan Isaacson [:eeejay]]

Not sure what the bug is. We handle disabled by uttering unavailable. If I remember correctly, that is because disabled could be confused with enable/disable toggles.