Add considerations for screen readers for testing apis
Open
@niklas-wortmann is already working on this.
Since Feb 12, 2020.
- Dominant language
- TypeScript
- Stars
- 31.7k
- Forks
- 3k
- PR merge metrics
- No merged PRs in 30d
Description
We need to look into what marble testing behaves like for people using screen readers. And then address any issues that there may be. I strongly feel that marble diagrams are probably awful to deal with on screen readers.
We will at least need to document how to better test with imperative code that may be easier to follow with a reader.
Alternatively, we may add some apis to the test scheduler to support more imperative creation of testing observables.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.