-
Notifications
You must be signed in to change notification settings - Fork 152
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.
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
fix: Updating NavLinkButton to announce current page #4677
fix: Updating NavLinkButton to announce current page #4677
Conversation
…dated the snapshots for their unit tests to account for the new text
…n have aria-current support for links.
@@ -2187,11 +2187,16 @@ | |||
resolved "https://registry.yarnpkg.com/@types/ms/-/ms-0.7.31.tgz#31b7ca6407128a3d2bbc27fe2d21b345397f6197" | |||
integrity sha512-iiUgKzV9AuaEkZqkOLDIvlQiL6ltuZd9tGcW3gwpnX8JbuiuhFlEGmmFXEXkN50Cvq7Os88IY2v0dkDqXYWVgA== | |||
|
|||
"@types/node@*", "@types/node@>= 8", "@types/node@^12.0.12", "@types/node@^14.14.6", "@types/node@^14.17.15": | |||
"@types/node@*", "@types/node@>= 8", "@types/node@^14.17.15": |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are all these changes to yarn.lock
expected? Many don't seem connected to the office-ui-fabric-react update.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. When I bumped the office-ui-fabric-react version, it appears that it updated also updated the yarn.lock entries for packages that are dependencies. I believe this happened in the "linking dependencies" and "build fresh packages" steps; that resulted in the reformatting (e.g. moving @types/node@^12.0.12" from line 2190 and creating a separate entry below on 2195.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Read through, ran and verified behavior.
Approving with one question in yarn.lock
.
Details
When using the Left Nav from results view in Unified, JAWS/NVDA users were not able to know if they had navigated to a list item that was selected or unselected. By adding the "aria-current" attribute to each item, the selected list item is announced as "current page", so they have the necessary context.
Motivation
Addresses the following Unified bug: https://dev.azure.com/mseng/1ES/_workitems/edit/1859838
Context
Pull request checklist
yarn fastpass
yarn test
)<rootDir>/test-results/unit/coverage
fix:
,chore:
,feat(feature-name):
,refactor:
). SeeCONTRIBUTING.md
.