Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[8.x] fix: [Stateful: Home page] Not accessible element, showing numb…
…er of active API keys, via keyboard (#197456) (#198804) # Backport This will backport the following commits from `main` to `8.x`: - [fix: [Stateful: Home page] Not accessible element, showing number of active API keys, via keyboard (#197456)](#197456) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Alexey Antonov","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-11-04T14:47:33Z","message":"fix: [Stateful: Home page] Not accessible element, showing number of active API keys, via keyboard (#197456)\n\nCloses: #195209\r\n\r\nThis PR is based on the following comment: \r\n\r\n> @cee-chen / @bhavyarm, could you please validate this issue? I'm not\r\nsure if the badge should be keyboard accessible. On the other hand, I\r\nthink it might make sense to move active API keys inside the badge.\r\nHowever, this is more of a design question rather than an a11y one.\r\n\r\n_Originally posted by @alexwizp in\r\n[#195209](https://github.com/elastic/kibana/issues/195209#issuecomment-2429091670)_\r\n\r\nThis PR move text inside badge to address a11y concerns.\r\n\r\n## Screen: \r\n\r\n<img width=\"734\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/66b2d4f5-75ee-4a1a-b286-03cd346d9aeb\">","sha":"0a1ec8f846cb0c78cfe3ddd0f2c1b4ccd1b3365b","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Project:Accessibility","release_note:skip","v9.0.0","Team:Search","backport:prev-minor"],"title":"fix: [Stateful: Home page] Not accessible element, showing number of active API keys, via keyboard","number":197456,"url":"https://github.com/elastic/kibana/pull/197456","mergeCommit":{"message":"fix: [Stateful: Home page] Not accessible element, showing number of active API keys, via keyboard (#197456)\n\nCloses: #195209\r\n\r\nThis PR is based on the following comment: \r\n\r\n> @cee-chen / @bhavyarm, could you please validate this issue? I'm not\r\nsure if the badge should be keyboard accessible. On the other hand, I\r\nthink it might make sense to move active API keys inside the badge.\r\nHowever, this is more of a design question rather than an a11y one.\r\n\r\n_Originally posted by @alexwizp in\r\n[#195209](https://github.com/elastic/kibana/issues/195209#issuecomment-2429091670)_\r\n\r\nThis PR move text inside badge to address a11y concerns.\r\n\r\n## Screen: \r\n\r\n<img width=\"734\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/66b2d4f5-75ee-4a1a-b286-03cd346d9aeb\">","sha":"0a1ec8f846cb0c78cfe3ddd0f2c1b4ccd1b3365b"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/197456","number":197456,"mergeCommit":{"message":"fix: [Stateful: Home page] Not accessible element, showing number of active API keys, via keyboard (#197456)\n\nCloses: #195209\r\n\r\nThis PR is based on the following comment: \r\n\r\n> @cee-chen / @bhavyarm, could you please validate this issue? I'm not\r\nsure if the badge should be keyboard accessible. On the other hand, I\r\nthink it might make sense to move active API keys inside the badge.\r\nHowever, this is more of a design question rather than an a11y one.\r\n\r\n_Originally posted by @alexwizp in\r\n[#195209](https://github.com/elastic/kibana/issues/195209#issuecomment-2429091670)_\r\n\r\nThis PR move text inside badge to address a11y concerns.\r\n\r\n## Screen: \r\n\r\n<img width=\"734\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/66b2d4f5-75ee-4a1a-b286-03cd346d9aeb\">","sha":"0a1ec8f846cb0c78cfe3ddd0f2c1b4ccd1b3365b"}}]}] BACKPORT--> Co-authored-by: Alexey Antonov <[email protected]>
- Loading branch information