MelSumner / MelSumner/ember-component-patterns
suggestion/question: section addressing ember-a11y-testing
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 19
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
I am wondering if it would be helpful to add a section about how ember-a11y-testing fits into the picture. If these patterns are followed, can the developer rely on the fact that ember-a11y-testing validation will reflect this/can ember-a11y-testing be used as essentially a guide to implementing these best practices?
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 existing component-patterns documentation and the role of ember-a11y-testing described in the issue. Clarify whether its validation reflects these patterns and document how it should guide implementation, if applicable. Done means the relationship and usage guidance are explicit.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100