-
**Describe the bug**
The Maps feature is inaccessible to users of assistive technology. The map itself does not allow the screen reader user to gesture or select
**To Reproduce
Steps to reproduc…
-
things should be easy to understand in the UI so user knows what to do next
- [ ] tutorial in reviewing UX against some examples
- [ ] identify common UX mistakes
- [ ] how to report other potential i…
-
### Issue Summary
The input fields for the address info question type are missing proper labels, making them inaccessible to screen readers. A placeholder is currently used, but placeholders do not a…
-
**Description**
For user using assistive technology it's better to hear the element name and placeholder text which would be either an example what to enter or explaining more about the search field. …
-
**Description**
All field names and their help text has to be accessible for the users. Especially for the ones using assistive technology as they cannot see what is on the screen.
**Preconditions**
…
-
### Package
@carbon/react
### Browser
Chrome
### Operating System
MacOS
### Package version
1.63
### React version
React
### Automated testing tool and ruleset
N/A
### Assistive technology…
-
Example: https://www.w3.org/WAI/ARIA/apg/patterns/alert/examples/alert/#assistivetechnologysupport
According to specifications, iframe elements typically necessitate an accessibility name, with exc…
-
This issue exists to track converting the web-component switch to use ElementInternals rather than the current FormAssociation behavior.
As part of this change, we should:
- Get the DOM as clean a…
-
### Bug Description
When attempting to include focusable content such as links, buttons, or any interactive elements inside a carousel, an accessibility error occurs.
Accessibility issue:
**Ro…
-
### Describe the bug
When viewing a `` with HTML/CSS/JS tabs in Safari, the tabs are invisible.
### Screenshots
![Screenshot of a code block in safari with invisible HTML/CSS/JS tabs](https://gith…