microsoft / microsoft/BotFramework-WebChat
Test: automate accessibility by implementing text alternative computation
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.8k
- Forks
- 1.6k
- Avg merge
- 22h 58m
- Merged PRs (30d)
- 2
Description
Feature Request
Implement "text alternative computation" according to W3C, https://www.w3.org/WAI/PF/aria-1.1/roles#textalternativecomputation.
Also read, https://developers.google.com/web/fundamentals/accessibility/semantics-aria/aria-labels-and-relationships.
Then, in our test, we can write the following to automate testing for accessibility and reduce regressions:
const alt = getTextAlternative(document.getElementById('.webchat'));
expect(alt).toBe('Activity text region\nYes button');
[Enhancement]
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 W3C text alternative computation specification and the linked Google accessibility guidance. Then inspect the existing test setup to determine where getTextAlternative and the example assertion belong; done means the example produces "Activity text region\nYes button" and accessibility regressions can be tested automatically.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- accessibility, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100