Open Bug 1688298 Opened 4 years ago Updated 4 years ago

Add accessibility checks for when EventUtils.sendKey is used in browser chrome tests.

Categories

(Testing :: General, task, P3)

Product:
Testing
Component:
General
Version:
Default
Type:
task

Tracking

(Not tracked)

People

(Reporter: yzen, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [a11y-automation])

In cases where the key argument is "return" or "space", we assume that the element must be also accessible. Similar to EventUtils.sendMouseEvent when sending click we would like to check for interactive attributes such as interactive semantics, labelling, focusable, visible and enabled states.

Assignee: yzenevich → nobody
Status: ASSIGNED → NEW
You need to log in before you can comment on or make changes to this bug.