-
### Is your feature request related to a problem? Please describe.
In highly repetitive contexts, screen reader users lose orientation while using the NVDA element list when the elements have the s…
-
I not sure where's the glossary ? Or they didn't put them in ug because the glossary is on one page whereas there's the part below it doesn't look like glossary. I assume they forgot to put in.
![Scre…
-
### Prerequisites
- [X] I [searched for any existing report](https://github.com/darkreader/darkreader/issues?q=is%3Aissue) about this bug to avoid opening a duplicate.
- [X] I can reproduce this bug …
-
## Description
I feel that the readability of the 'Use cases' section in the DG could be improved with better formatting.
Currently, there is no formatting distinction (e.g. font size, bold, italics…
-
**Issue**
The commands in the sequence diagram on page 20 ("Adding a contact") are not very readable by the human eye unless the reader zooms into the diagram by a few hundreds of percents.
**Sugges…
-
### 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 reproduce…
-
**Description**
Visually present text on the element should be announced for the user in order not to confuse them. Especially for the users using assistive technology.
**Preconditions**
Stateful Pl…
-
**Issue**
In page 5 of the DG, there is a `1` multiplicity sitting above `UIWindow`. It could be attributed to either `UIWindow`'s association to `Logic` or its association to `UIManager`. However, th…
-
**Description**
Element behavior should be the same while using keyboard with or without screen reader. In case It is not possible to make it behave the same way, alternative should exist.
**Precondi…
-
**Description**
When user is on element, announcement of element should be made for user to understand where at the moment he/she is, how to interact with the element.
**Preconditions**
Stateful Conn…