Skip to content

Repo maintenance: update a11y issue template, and add a11y test to convergence checklist #22363

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
smhigley merged 2 commits into from
Apr 25, 2022
Merged

Repo maintenance: update a11y issue template, and add a11y test to convergence checklist #22363

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
27cd107
update a11y issue template, and add a11y test to convergence checklist
smhigley Apr 6, 2022
25b6c01
add wording about internal tracker
smhigley Apr 6, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions .github/ISSUE_TEMPLATE/bug-report.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,10 +39,11 @@ body:
**PLEASE NOTE:**

1. Do not link to, screenshot or reference a Microsoft product in this description.
2. Our screen reader support is limited to Edge + Narrator.
- Please check ARIA component examples to ensure it is not a screen reader or browser issue.
- Issues that do not reproduce in Edge + Narrator, and aren't caused by obvious invalid aria values, should be filed with the respective screen reading software, not the Fluent UI repo.
3. There is documentation or best practice that supports your expected behavior (review [WAI-ARIA](https://www.w3.org/TR/wai-aria-1.1/) for accessibility guidance.)
2. Please check ARIA component examples to ensure it is not a screen reader or browser issue. If the issue concerns screen reader behavior that reproduces on HTML elements or ARIA Practices examples (https://w3c.github.io/aria-practices/), it should be filed with the respective browser or screen reading software and not the Fluent UI repo.
3. There is documentation or best practice info to support your expected behavior (review https://w3c.github.io/aria/ for accessibility guidance.)

**Additional note for Microsoft employees:**
Please file accessibility issues in our internal tracker (http://aka.ms/fluentui-a11y). This helps with tracking accessibility progress within the company.
options:
- 'yes'
- 'no'
Expand Down
1 change: 1 addition & 0 deletions .github/ISSUE_TEMPLATE/convergence_epic.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,7 @@ completed as part of converging a component. More info can be found here: https:
- [ ] Unit tests
- [ ] VR tests
- [ ] Accessibility behavior tests
- [ ] Create an issue and run [manual accessibility tests](https://github.com/microsoft/fluentui/wiki/Manual-Accessibility-Review-Checklist): (issue link)
- [ ] Write README.md covering basic usage
- [ ] Write initial MIGRATION.md guide (include v8 and v0)
- [ ] Set component ownership in CODEOWNERS
Expand Down