-
**Actual:** Screen reader reads "Font button menu".
**Expected:** Screen reader should read "Font combo box"
Steps to produce issue:
- Launch JAWS( Screen Reader )
- On launch of CKEditor pr…
-
Swoptact should use a higher contrast color scheme (no lavender background) and we need to test (and possibly add) screen-reader compatibility. It may be a good idea to look into more requirements fo…
-
### Steps to reproduce the problem
1. Navigate to a timeline/list which shows a post that has truncated text. (Sorry, not sure how to reproduce this reliably. [Here](https://social.luca.run/@luca/109…
-
### Reviewing Trevor project
You did a good job applying Bootstrap to your Project 💯 . But there are some things you can do to improve your codes 👍 .
- [ ] I recommend writing a README file to …
-
### Current behavior
Selecting a view type or filter using the keyboard or screen reader shifts the focus back to the top of the page.
### Steps to reproduce
Example page: [Spotlight Accessib…
-
## User Story
_"As a VFS team member, I want to find accessibility information relevant to my role, so that the products I build are accessible."_
Assignee:
Peer Reviewer:
## Description
This issue …
-
Jira issue originally created by user @unknown-jira-user-1:
## Description
The objective of this technique is to show how to use PDF tags to provide non-visual access to the content hierarchy in a…
-
### Describe the bug
CSS hidden accessibility for screen readers is not compatible with the NVDA/Firefox screen reader/browser combination. The issue arises due to Firefox's interpretation of the `tr…
-
**Steps to Reproduce**
1. Enable NVDA screen reader.
2. Open page in Google Chrome.
3. Use TAB or TAB + SHIFT to navigate to the kebab menu and close buttons.
4. Notice the lack of meaningful name…
-
In the [markup house style](https://github.com/springernature/frontend-playbook/blob/master/markup/house-style.md) page there's a very long section explaining why we write HTML 5 (instead of XHTML). T…