Accessibility API mapping for EditContext editors
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 48
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
We should have something similar to https://w3c.github.io/aria/html-aam/#att-contenteditable for EditContext.
Hopefully we can just link to that with some wording about treating an element with an EditContext the same as contenteditable.
(This could also be put in the AAM spec. Not sure which is better.)
Contributor guide
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 reading the referenced HTML-AAM section for contenteditable and compare its mapping to the EditContext behavior described here. Determine whether the guidance belongs in the EditContext specification or the AAM specification; done means documenting the appropriate mapping and linking or adapting the relevant wording.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- accessibility, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100