Fix screen reader issues

Open
#90 0 comments 0 reactions 1 assignee View on GitHub

@CooperRedhat is already working on this.

Since Jul 25, 2022.

Assessment

This issue has not been assessed yet.

Description

This collection of issues is a bunch of easy fixes that will help the screen reader experience quite a bit. Some of these are documentation/demo issues but are still important to show consumers the correct way to do it.

Testing tool | Issue | Type | URL | Specific Location | Suggested Solution
– | – | – | – | – | –
VO | Headings skip level (1 > 3 > 5) | Structure | all | Page and card headings | Headings should go in sequential order and convey structure
VO | Show prerequisites buttons should be unique | Labeling | all | preqs button | They should make sense out of context (i.e. "Show {title} prereqs")
VO | Status select should have a label | Labeling | https://quickstarts.netlify.app/quickstarts-props | Status select/dropdown | Should have some kind of label ("Status"), currently just expanded and collapsed button

Jira Issue: PF-1891

Dominant language
TypeScript
Stars
15
Forks
47
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from patternfly/patternfly-quickstarts

All issues in patternfly/patternfly-quickstarts

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.