eschutho opened a new pull request, #41769:
URL: https://github.com/apache/superset/pull/41769
### WCAG rule
2.1 SC 1.3.1 (Info and Relationships) / 3.3.2 (Labels or Instructions) —
Level A.
### What changed
The CRON expression text input in `AlertReportCronScheduler` (shown when a
user picks "CRON Schedule" for an alert/report) had no `aria-label`,
`aria-labelledby`, or associated `<label>`. Its only hint was a placeholder
(`t('CRON expression')`) plus a visually adjacent but unassociated `<div
className="control-label">` reading "Schedule". Screen reader users tabbing
into the field heard no accessible name at all.
Added `aria-label={t('Schedule')}` to the `<Input>`, matching the naming
convention already used by the sibling `Select` above it
(`ariaLabel={t('Schedule type')}`, mirroring its own adjacent visible label).
### Behavior
No visual or functional change — this only adds an accessible name for
assistive technology.
### Test plan
1. Open Alerts & Reports → create/edit an alert → in the "Schedule" section,
switch schedule type to "CRON Schedule".
2. Tab to the CRON expression input with a screen reader running (e.g.
VoiceOver/NVDA).
3. Verify the announced label is "Schedule" (previously: no accessible name
announced, or generic "edit text").
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
