analyze accessibility metadata
- Dominant language
- JavaScript
- Stars
- 98
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
Right now, Ace summarizes what's present/missing regarding the accessibility metadata in the package document. There are two ways to improve upon this:
* include what's in the content documents (perhaps as a part of content analysis -- see this example of embedded video metadata: https://idpf.github.io/a11y-guidelines/content/meta/schema.org.html#meta010-ex02)
* suggest values for missing metadata
Contributor guide
Research direction
Start by reading Ace's existing package-document accessibility metadata analysis and the content-analysis area, then compare the embedded video metadata example linked in the issue. Done means the checker can include accessibility metadata from content documents and suggest values for metadata that is missing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- accessibility
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100