stackabletech / stackabletech/crddocs

Accessibility

Open
#14 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
CSS
Stars
0
Forks
1
PR merge metrics
No merged PRs in 30d

Description

How good is it? What can we improve?

### Tasks
- [x] set html tag lang=en
- [x] footer logo needs alt text
- [x] for the footer FA icons, follow FA accessibility instructions: https://fontawesome.com/v5/docs/web/other-topics/accessibility#web-fonts-with-css-semantic-icons
- [ ] link color is low contrast, especially on grey rows in tables. how to fix?
- [x] browser zoom function apparently disabled by the `maximum-scale` attribute
- [ ] the version `select` element does not have a label
- [ ] the version `select` element uses JS jump navigation. It would be better to have a separate submit button. Or, maybe the whole select element can be replaced with a nav item? I.e: https://www.w3.org/WAI/tutorials/menus/flyout/

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

No source files or tests are named. Start by locating the page styles and version-selector markup and behavior, then review each unchecked accessibility task against the linked Font Awesome and WAI guidance. Done means the link contrast, select labeling, and version navigation concerns are addressed and the resulting page behavior is verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, html, javascript
Domain
accessibility, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.