The-Strategy-Unit / The-Strategy-Unit/data_science
Simple accessibility tips
Open
Nobody has claimed this yet.
session: C&C ☕
- Dominant language
- Jupyter Notebook
- Stars
- 11
- Forks
- 5
- Avg merge
- 5h 34m
- Merged PRs (30d)
- 1
Description
Making shiny apps fully WCAG compliant can be hard but starting to think about accessibility when producing outputs isn't!
- colour palettes
- skip links
- alt text in quarto
- using headers correctly
- contrast
- language tags
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reviewing the issue's listed accessibility topics: colour palettes, skip links, alt text in Quarto, headers, contrast, and language tags. Done should mean that clear guidance covering the selected topics is added, but the issue does not identify a documentation file or test to use.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100