hackforla / hackforla/accessibility

Epic: Make any missing pages for aria, feature and structural elements guidance

Open
#68 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
0
Forks
3
PR merge metrics
No merged PRs in 30d

Description

### Overview
We need to make sure that the repo has complete guidance for accessibility patterns so that developer can understand which accessibility pattern to use

### Action Items
- [x] Ask ChatGPT for a list of all accessibility patterns
- ARIA
- Features
- Structural Elements
- [ ] Compare against list in spreadsheet to identify missing items
- [ ] Add to spreadsheet
- [ ] Create issue for each page to add as sub issues to this issue

### Resources/Instructions
- 1.0.1 Spreadsheet: [Accessibility: WAVE: Known Issues and Solutions DRAFTS](https://docs.google.com/spreadsheets/d/14cXbfsc2McDpKxmGyXbLPkCgj1aeN7NmlxzeeJqlcsU/edit?gid=0#gid=0)
- W3C: [WAI-ARIA 1.2: Definitions of States and Properties](https://www.w3.org/TR/wai-aria-1.2/#state_prop_def).

Contributor guide

Open the contributing guide

Research direction

Start by comparing the accessibility patterns in the W3C WAI-ARIA 1.2 definitions with the linked Accessibility: WAVE: Known Issues and Solutions DRAFTS spreadsheet. Identify missing ARIA, feature, and structural-element guidance, add the missing items to the spreadsheet, and create one issue for each page as sub-issues. Done means the comparison, spreadsheet updates, and page issues are complete.

Written by the indexing model from the issue text.

Assessment

Domain
accessibility, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.