1882207 - Investigate the datepicker cells that are failing a11y_checks when clicked in tests for UI Widgets

Status: RESOLVED FIXED

(Toolkit :: General, task)

Description

[Anna Yeddi [:ayeddi]]

The following tests are flagged by a11y_checks:
1. toolkit/content/tests/browser/datetime/browser_datetime_datepicker_min_max.js - Node is not accessible via accessibility API - td
2. toolkit/content/tests/browser/datetime/browser_datetime_datepicker_mousenav.js - Node is not accessible via accessibility AP - td.weekend.outside
3. toolkit/content/tests/browser/datetime/browser_datetime_datepicker.js - Node is not accessible via accessibility API - td.outside
4. toolkit/content/tests/browser/datetime/browser_datetime_change_event.js - Node is not accessible via accessibility API - td.outside (bug 1882173)

Comment 1

[Anna Yeddi [:ayeddi]]

Attachment: Bug 1882207 - Handle the datepicker cells that are failing a11y_checks when clicked in tests for UI Widgets. r=emilio,Jamie!

The gridcells are not expected to be interactive and focusable individually, but it is allowed to manually manage focus within the grid per ARIA Grid pattern (https://www.w3.org/WAI/ARIA/apg/patterns/grid/).

Example of a such grid would be a datepicker where one gridcell can be selected and the focus is moved with arrow keys once the user tabbed into the grid.

In grids like a calendar grid, only one element would be included in the focus order and the rest of grid cells may not have an interactive accessible created. We need to special case the check for these gridcells.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/38dd14d1a2a5
Handle the datepicker cells that are failing a11y_checks when clicked in tests for UI Widgets. r=emilio,Jamie

Comment 3

[Narcis Beleuzu [:NarcisB]]

https://hg.mozilla.org/mozilla-central/rev/38dd14d1a2a5