-
### Prerequisites
- [X] I [searched for any existing report](https://github.com/darkreader/darkreader/issues?q=is%3Aissue) about this website issue to avoid opening a duplicate.
- [X] I can reprod…
-
Screen Reader Mobile vs Desktop, Voice over-NVDA, Chrome (on mobile) Firefox (on desktop)
- One participant tested twice (once on mobile, and compared to desktop)
- On mobile, user experienced the pag…
-
### Describe the bug
When using button from ui5 and using a screen reader, it's announcing button + button label + design [ie.
"Default" | "Positive" | "Negative" | "Transparent" | "Emphasized" | "…
-
**Description**
Dot is not being announced when you are listening to screen reader. But for some elements on the page it is being announced after the name of the element.
**Preconditions**
Stateful I…
-
**Description**
It should be clear and informative for users performing Search what is happening, what results they are getting. For screen reader users as well.
**Preconditions**
Stateful Indices ->…
-
**Description**
Announcement should be made for the element on which user is at the moment, for him/her to understand what element it is, how to interact with it. Especially for users using assistive …
-
### Reproduction link
[](https://codesandbox.io/p/sandbox/w928py)
### Steps to reproduce
Use any screen reader (t…
-
**Description**
When user activates an element and it's state change takes time, user has to be informed about it to clearly understand that he/she did activate it.
**Preconditions**
Stateful Web Cra…
-
**Description**
Errors are clear and announced for the user, that user would know how to easily fix it. Especially for the users using assistive technology.
**Preconditions**
Stateful Web crawlers -…
-
**Description**
All instructions, explanations which belongs to the input field should be programmatically determined that screen readers would announce it to the user.
**Preconditions**
Stateful Web…