-
### Describe the problem to be solved
For now I can search inside Grist documents. But it seems I can't search through my documents list.
If I have lots of documents it can quickly become troubles…
-
The form lacks proper labels and ARIA attributes, making it difficult for screen readers to interpret. I can add accessible form elements including proper labels, aria-* attributes, and improve focus …
-
CENG_3306
Docs: https://react-magma.cengage.com/version/4.3.0/api/input/
Success Criteria: https://www.w3.org/WAI/WCAG21/Understanding/name-role-value
In the Character Counter example, the ch…
-
### Describe the issue
### **User Experience:**
Visually impaired users who depend on assistive technology as screen readers will face difficulty while navigating on nested interactive controls or…
-
## What
Add some introductory content to pages having nothing between their H1 and H2:
- [Install with Node.js package manager (npm)](https://frontend.design-system.service.gov.uk/installing-w…
-
## Type of feedback
//dev
## Description
The element order of `.wp-block-wordpress-playground-playground .wordpress-playground-main-container .wordpress-playground-header` has been shifted usin…
-
**Description**
After closing dialog, navigation should start from the element which opened it not from the first element on the webpage. Otherwise users, especially using only keyboard and/or assisti…
-
### 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…
-
### Checklist
- [x] Read the [docs](http://blink.sh/docs/)
- [x] Searched for [existing GitHub issues](https://github.com/blinksh/blink/issues)
### Configuration
Xcode: 16.0 (16A242d)
Blink…
-
Credit to Rob, mvn building failed in Ubuntu 18.04 and 18.10
surefire report:
`java.awt.AWTError: Assistive Technology not found: org.GNOME.Accessibility.AtkWrapper`
According to these links:
ht…