Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Badge is inaccessible for keyboard, screen reader users #8064

Closed
L1nBra opened this issue Oct 7, 2024 · 2 comments
Closed

Badge is inaccessible for keyboard, screen reader users #8064

L1nBra opened this issue Oct 7, 2024 · 2 comments
Labels
accessibility answered Issues answered by the EUI team - auto-closes open issues in 7 days if no follow-up response

Comments

@L1nBra
Copy link

L1nBra commented Oct 7, 2024

Description
Badge, containing information which can change, is not accessible for the user using only keyboard, screen reader. The user who cannot see, won't be able to see/understand what information is present on the badge.

Preconditions
Stateful Home page (Overview) is opened.

Steps to reproduce

1.Navigate to New button while using only keyboard by pressing Tab key.
2.Press Enter.
3.Navigate to the Name input field.
4.Fill in any name (Test).
5.Navigate to Create API key button.
6.Press Enter key.
7.Press Esc key.
8.Refresh the page (pressing F5).
9.Navigate to active API keys element using only keyboard.

Environment

  • Windows 11 Pro
  • Chrome Version 129.0.6668.70 (Official Build) (64-bit)
  • Screen Reader NVDA
  • Cloud, QA environment

Proposed solution

Element should be defined with using attributes: role, name, value, for user to be able to access it.

and it should be imported as per Elastic UI component for badge
demo code snippet:

import React, { Fragment, useState } from 'react';
import {
  EuiBadge,
  EuiFlexItem,
  EuiFlexGroup,
  EuiSpacer,
  EuiSwitch,
  EuiText,
  EuiTitle,
} from '@elastic/eui';
...

WCAG or Vendor Guidance (optional)

Screenshots or Trace Logs

Badge on the webpage + html used to define it
Image

Created from Stateful Search issue #195209

@L1nBra L1nBra changed the title Not accessible element, showing number of active API keys, via keyboard Badge is inaccessible for keyboard, screen reader users Oct 8, 2024
@cee-chen
Copy link
Contributor

@L1nBra We need more clarification as to what you mean by "inaccessible". If the badge is not an interactive element/button and isn't clickable, then it's fully expected it's not reachable via just keyboard alone. Screen reader users however should fully be able to navigate to via standard screen reader navigation methods.

CC @alexwizp - any chance you can step in and help triage as to whether this is an issue in EUI?

@alexwizp
Copy link
Contributor

Hi, we discussed that with @L1nBra. No need to be fixed

@cee-chen cee-chen added the answered Issues answered by the EUI team - auto-closes open issues in 7 days if no follow-up response label Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility answered Issues answered by the EUI team - auto-closes open issues in 7 days if no follow-up response
Projects
None yet
Development

No branches or pull requests

3 participants