You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
None of the needs-review document pages are referenced anywhere inside the web extension. Some of the rules that show up in the Needs review tab link to their counterparts of Automated checks document pages.
#### Details
Bug fix to use needs-review document pages for the Needs review tab
link. None of the needs-review document pages were referenced anywhere
inside the web extension. Some of the rules that show up in the Needs
review tab link have document page available but the url under needs
review were of either automated check rule url.
The fix used is, In the rule-resources.tsx file we are checking if the
tab selected is needs-review on the basis of the outcome type and added
a new file named needs-review-rule-resources.tsx is used to create the
needs review url on the basis of rules present in the document page.
![Screenshot 2023-12-07
191019](https://github.com/microsoft/accessibility-insights-web/assets/150002431/24e3769e-ad5a-4a0b-aed8-babc9e4ae31d)
##### Motivation
fix: No links to needs-review doc pages? #7007
##### Context
#### Pull request checklist
- [x] Addresses an existing issue: #7007
- [x] Ran `yarn fastpass`
- [x] Added/updated relevant unit test(s) (and ran `yarn test`)
- [x] Verified code coverage for the changes made. Check coverage report
at: `<rootDir>/test-results/unit/coverage`
- [x] PR title *AND* final merge commit title both start with a semantic
tag (`fix:`, `chore:`, `feat(feature-name):`, `refactor:`). See
`CONTRIBUTING.md`.
- [NA] (UI changes only) Added screenshots/GIFs to description above
- [NA] (UI changes only) Verified usability with NVDA/JAWS
Describe the bug
None of the needs-review document pages are referenced anywhere inside the web extension. Some of the rules that show up in the Needs review tab link to their counterparts of Automated checks document pages.
Specifically:
color-contrast
is detected, the "More information about color contrast" opens https://accessibilityinsights.io/info-examples/web/color-contrast/, which is a different pageExpected behavior
Since these pages exist to add more detail on fixing these issues, I'd expect the pages to be used as reference material by the web extension
Screenshots
Are you willing to submit a PR?
Did you search for similar existing issues?
Additional context
The text was updated successfully, but these errors were encountered: