You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
at AccessibilityService.assertValidAxeReport (a11y.ts:75:13)
at AccessibilityService.testAppSnapshot (a11y.ts:48:10)
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at Context. (ml.ts:400:11)
at Object.apply (wrap_function.js:73:16)
The text was updated successfully, but these errors were encountered:
peteharverson
changed the title
[ML] VIOLATION │ [aria-allowed-attr]: Ensures ARIA attributes are allowed for an element's role on ML notifications button
[ML] [aria-allowed-attr]: Ensures ARIA attributes are allowed for an element's role on ML notifications button
Mar 24, 2023
Kibana version: Main
Browser version: chrome latest
Browser OS version: OS X
Describe the bug: ML notifications button is violating "Ensures ARIA attributes are allowed for an element's role" validation rule.
a11y error trace:
ml Accessibility for user with full ML access with data loaded anomaly detection create advanced job open wizard
Failures in tracked branches: 0
Buildkite Job
https://buildkite.com/elastic/kibana-pull-request/builds/114819#01870b39-92e0-4b01-ad60-85338a068613
Error: a11y report:
VIOLATION
[aria-allowed-attr]: Ensures ARIA attributes are allowed for an element's role
Impact: serious
Help: https://dequeuniversity.com/rules/axe/4.6/aria-allowed-attr?application=axeAPI
Elements:
-
at AccessibilityService.assertValidAxeReport (a11y.ts:75:13)
at AccessibilityService.testAppSnapshot (a11y.ts:48:10)
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at Context. (ml.ts:400:11)
at Object.apply (wrap_function.js:73:16)
The text was updated successfully, but these errors were encountered: