-
Regarding Eli's service alert email, relevant description below:
> When a patron searches any variation of "Kids Book / Readers" or "Kids/ Books/ Reader" because they are trying to emulate the cal…
-
**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**
After deleting any entry, announcement about successful delete should be made for the user without any additional confusing announcements. Especially for the users using assistive tech…
-
**Description**
Elements should not only be defined clearly how they look on the page, but also programmatically. Especially for assistive technology users in order to understand with what element he/…
-
**Description**
Errors present for the fields should be announced for the users. Especially for the users using assistive technology, that they understand that error exists and how to fix it.
**Preco…
-
**Description:**
The participation page does not contain a level-one heading (``). This heading is important for screen reader users to navigate directly to the main content of the page.
**Steps to…
-
I'm trying to open this page in the reader:
https://de.wikipedia.org/wiki/Liste_der_Herrschaftsformen
I have no idea how to do that. Searching for the title didn't work. I think an easy way to fix th…
-
Describe: Hinders reader's reading flow as the diagram is said to be below but is on the next page
Screenshot:
![image.png](https://raw.githubusercontent.com/nus-cs2103-AY2425S1/pe/master/files/74580…
-
**Description**
The element on which user is at the moment should be announced. Otherwise it can be confusing, hearing two elements announcement when user navigates to the field. Especially, for the u…
-
**Description**
Buttons should be clear and named so, that users would easily understand what is the purpose of the button, how to interact with it.
**Preconditions**
Stateful Web crawlers -> View C…