-
Notifications
You must be signed in to change notification settings - Fork 145
chore(Page): updated a11y docs to new template #3880
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
chore(Page): updated a11y docs to new template #3880
Conversation
ebf0590 to
0bacd76
Compare
|
|
||
| **Screen reader users** should be able to navigate through and interact with the masthead of the page using the same interactions as keyboard users. Elements of a page that do not have visible descriptive text, such as toggle icons, should have alternative text for screen readers. | ||
| - Provide a [skip to content](/components/skip-to-content) if more than one page shares the same heading or sidebar content. | ||
| - Give each `nav` element on the page a unique `aria-label`. |
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.
I typically only see this guidance when there is more than one nav. I think it might make sense to clarify that in this bullet? I'm just noticing that you do include that verbiage in the testing section below so I think updating this one makes sense
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.
Ah good catch, agreed we should be consistent in the verbiage.
Though now I'm slightly conflicted, in that I'm wondering if we should say that a nav should have a unique label regardless of amount, i.e. whether there's 7 or only 1. I guess I'm thinking in terms of rotor menus/wherever a list of X element types are listed out (lists, headings, etc). Even with only 1 nav (or list, or whatever) on a page, I feel like providing an aria-label can only help, whereas omitting one could possibly hurt?
For example, if the nav is announced as just "nav' to a user, it could be site navigation, page navigation, breadcrumb navigation, etc. So what the user would be jumping to could be a bit of an unknown.
What do you think, though?
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.
I think it definitely could be helpful, but I'm wondering if it's fully required. I wonder if we could explain how it can be helpful but say that it's only required when there's multiple? (And maybe we could even give the examples you just stated.)
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.
Maybe, "If there are multiple nav elements on the page, give each one a unique aria-label." as the checkbox label, then a description of, "You should also consider providing an aria-label when there's only a single nav on the page, if the purpose of that nav is not the primary navigation."
Or something along those lines? Not sure how I feel about "primary navigation"; "primary site navigation", really just wanting to convey "something that isn't the typical navigation for a page"
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.
Yeah, I think that makes sense! And I think calling it a primary navigation isn't inherently bad. You could even work with those words a bit between both and say something like, "You should also consider providing an aria-label when there's only a single nav on the page, if the purpose of that nav isn't a typical, primary navigation for a page." (To be honest though, I think all of these options are probably fine though and hopefully get the point across.)
| - Provide a [skip to content](/components/skip-to-content) if more than one page shares the same heading or sidebar content. | ||
| - Give each `nav` element on the page a unique `aria-label`. | ||
| - Ensure there is only 1 `main` element on the page. | ||
| - Ensure each page section has an `aria-labelledby` attribute linked to a heading element within the section. |
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.
This is a really good point, and potentially unrelated to this PR, but are we actually following this recommendation in our Page demos?
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.
Can't recall off the top of my head but erring on the side of caution I want to say we may not be. That would require a follow up in Core and React, which I can evaluate which, if any, examples/demos need to be updated and create any necessary followups. Probably need to go through Org as well.
You're referring to the last bullet regarding aria-labelledby, correct?
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.
Right. I'm not sure if we've ever had our sections labelled by the headings. Out of curiosity, what made you think of this one? I'm not sure I'd heard it before, even though it makes a lot of sense.
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.
I thought it was an MDN docs page but maybe not, it may have been traversing through VO's rotor menu again. Or one of our a11y pages that mention sections shouldn't be used if there's no label/our example of providing a label for scrollable content.
If we do want to keep this it would probably make sense to update it to say use either aria-labelledby or aria-label if no visible text is present, but it may actually make sense to remove (even if for now). I want to say the main reason was rotot menu, though; not having a huge section of content announced in the rotor menu and instead have a descriptive aria label of some kind.
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.
Yeah, it makes sense to do, and I'm always up for adding more/better context to help users. I just hesitate to make recommendations if we aren't already walking that walk, so to speak. 🙂
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.
Definitely true. I think my thoughts were get a11y docs up to date and update core/react examples as follow ups according to the updated docs, though it may make more sense to not include stuff that we aren't following yet ourselves.
What do you think about me removing the verbiage about labeling page sections from this PR, opening issues in core/react to add consistent labeling, then once those are closed out we open a followup in Org to add in the verbaige about labeling sections?
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.
I think that would make sense to me!
0bacd76 to
7490316
Compare
|
@jessiehuff patternfly/patternfly-react#10173 and patternfly/patternfly#6431 regarding convo above, otherwise updates have been made here |
jessiehuff
left a comment
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.
LGTM!
* chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * docs(extensions): Updates the extensions landing page to add reference to the component groups extension. (#3849) * (docs(extensions): Updates the extensions landing page to add reference to the component groups extension. * Update packages/documentation-site/patternfly-docs/pages/landing-pages/extensions/extensions-data.json * typo update * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * docs(accessibility-design): Adds new documentation to support content audit. (#3781) * docs(accessibility-design): Adds new documentation to support content audit. * Test page name change * Apply suggestions from code review * Update packages/documentation-site/patternfly-docs/content/developer-resources/accessibility-design.md * Update packages/documentation-site/patternfly-docs/content/developer-resources/accessibility-design.md * Update packages/documentation-site/patternfly-docs/content/developer-resources/accessibility-design.md * Update packages/documentation-site/patternfly-docs/content/developer-resources/accessibility-design.md * Update packages/documentation-site/patternfly-docs/content/developer-resources/accessibility-design.md * Update packages/documentation-site/patternfly-docs/content/developer-resources/accessibility-design.md * Update packages/documentation-site/patternfly-docs/content/developer-resources/accessibility-design.md * Update packages/documentation-site/patternfly-docs/content/developer-resources/accessibility-design.md * Remove table * Removes numbers from headings. * Makes content updates and adds images. * Updates to content describing images. * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * fix: bump puppeteer to fix core (#3860) * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * Update naming for introductory pages across website sections. (#3851) * Update naming for introductory pages across website sections. * Caps change * Adjusts naming for about PatternFly page. * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * docs(accessibility-testing): Updates content as part of content audit. (#3776) * docs(accessibility-testing): Updates content as part of content audit. * Apply suggestions from code review Co-authored-by: Eric Olkowski <[email protected]> * Apply suggestions from code review * Content tweaks in progress. * Works on checkboxes. * Resolves merge conflict. * Update packages/documentation-site/patternfly-docs/content/developer-resources/accessibility-testing.md * Update packages/documentation-site/patternfly-docs/content/developer-resources/accessibility-testing.md Co-authored-by: Eric Olkowski <[email protected]> * Update packages/documentation-site/patternfly-docs/content/developer-resources/accessibility-testing.md Co-authored-by: Eric Olkowski <[email protected]> * Content alterations. * Content changes from review feedback. * Updates to buttons point. * Grammar and typo updates. * Update packages/documentation-site/patternfly-docs/content/developer-resources/accessibility-testing.md Co-authored-by: Eric Olkowski <[email protected]> * Merging. --------- Co-authored-by: Eric Olkowski <[email protected]> * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * fix: bump to latest release candidates ahead of 5.2 release (#3862) * fix: bump to latest release candidates ahead of 5.2 release * bump to latest component groups prerelease * bump react to pull in bug fix * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * updates to images to make icons black (#3856) * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * fix: avoid applying beta tags to nav items for next components (#3868) * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * fix(truncate): typos on guidelines (#3872) * docs(capitalization): Updates capitalization guidelines for better consistency and clarity. (#3855) * docs(capitalization): Updates guidance for capitalization. * Continues editing content. * Content updates progress. * Updates content and images. * Content and image updates. * Final content and image updates. * Updates recs per content team decision. * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * fix: add drag drop deps and remove unused code editor deps (#3866) * fix: add drag drop deps and remove unused code editor deps * bump react-docs to fix error * bump the prerelease versions * chore(Title): updated a11y docs to template (#3873) * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * docs(release-highlights): Adds release highlights for 5.2 release. (#3853) * docs(releases): Adds release highlights for v5.2 * docs(release-highlights): Adds release highlights for 5.2 release. * Update packages/documentation-site/patternfly-docs/content/get-started/release-highlights.md Co-authored-by: Michael Coker <[email protected]> * Adds more highlights. * Adds coming soon section. * Update packages/documentation-site/patternfly-docs/content/get-started/release-highlights.md Co-authored-by: Michael Coker <[email protected]> * Update packages/documentation-site/patternfly-docs/content/get-started/release-highlights.md Co-authored-by: Michael Coker <[email protected]> --------- Co-authored-by: Michael Coker <[email protected]> * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * docs(design): Adds initial information regarding Figma. (#3863) * docs(design): Adds Figma information where Sketch is currently mentioned. * Path update * Update packages/documentation-site/patternfly-docs/content/contribute/design/design.md * Path updates. * Update packages/documentation-site/patternfly-docs/content/contribute/design/design.md * Update packages/documentation-site/patternfly-docs/content/training/design.md * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * feat: release 5.3 (#3878) * feat: 5.3 release * update release highlights * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * fix: Bump topology to 5.2.1 (#3881) * fix: toplogy to 5.2.1 * add yarn.lock * update release highlights * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * Update broken link on develop.md * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * chore(deps): bump ip from 1.1.5 to 1.1.9 (#3895) Bumps [ip](https://github.com/indutny/node-ip) from 1.1.5 to 1.1.9. - [Commits](indutny/node-ip@v1.1.5...v1.1.9) --- updated-dependencies: - dependency-name: ip dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * add edit modal guidance (#3836) * add edit modal guidance * edits * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * chore(release): Updated component groups to 5.1.0 release (#3917) * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] chore(component-groups): Updated component groups to 5.1.0 release chore(component-groups): Updated component groups to 5.1.0 release * Updated version.json * feat(deps): version bump for 5.2.1 release (#3913) * feat(deps): version bump for 5.2.1 release * Update packages/documentation-framework/versions.json Co-authored-by: Evan <[email protected]> * Update packages/documentation-site/patternfly-docs/content/get-started/release-highlights.md Co-authored-by: Evan <[email protected]> * Update packages/documentation-site/patternfly-docs/content/get-started/release-highlights.md Co-authored-by: Evan <[email protected]> * Update packages/documentation-framework/versions.json * chore(deps): bump react-charts, react-docs * Update packages/documentation-site/patternfly-docs/content/get-started/release-highlights.md Co-authored-by: Erin Donehoo <[email protected]> * chore(docs): update release highlights * Update packages/documentation-framework/versions.json --------- Co-authored-by: Evan <[email protected]> Co-authored-by: Erin Donehoo <[email protected]> * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * chore(SkipToContent): updated a11y docs to template (#3871) * chore(SkipToContent): updated a11y docs to template * Updated test item description verbiage * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * feat(deps): version bump and release notes for 5.2.2 patch release (#3919) * feat(deps): version bump and release notes for 5.2.2 patch release * fix(release-highlights): correct listed table version * Update packages/documentation-site/patternfly-docs/content/get-started/release-highlights.md Co-authored-by: Erin Donehoo <[email protected]> --------- Co-authored-by: Erin Donehoo <[email protected]> * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * feat: add pf 6 alpha banner to home page and version switcher (#3896) * feat: add pf 6 alpha banner to home page and version switcher * update wording * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * feat(templates): add templates package to versions.json (#3902) * feat(templates): add templates package to versions.json for docs build * add support for template inline alert * add to patch version, update wording * update wording * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * chore(Page): updated a11y docs to new template (#3880) * chore(Page): updated a11y docs to new template * Removed requirement of aria-labelledby on page sections * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * chore: simplify Babel configuration (#3934) * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * chore(footer): Restructure new homepage footer (#3870) * Restructure footer * Remove PageSection from footer based on conversations * Rework structure * Fix footer height issue * Update flex * Fix typo * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * feat(docs): update medium articles (#3950) * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * docs(release-highlights): Creates release highlights for 5.3 release. (#3941) * docs(release-highlights): Creates release highlights for 5.3 release. * Continues working on content updates. * docs(release-highlights): Adds release highlights for 5.3 release. * Adds more context to menu toggle change. * Update packages/documentation-site/patternfly-docs/content/get-started/release-highlights.md * Update packages/documentation-site/patternfly-docs/content/get-started/release-highlights.md * Adds section for dual list selector. * Updates topology pipeline images. * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * feat(Templates): add to org site (#3947) * feat(Templates): add to org site * update versions, fix Th * hide prev version, update screenshots * chore(release): releasing packages [ci skip] - @patternfly/[email protected] - @patternfly/[email protected] * update documentation-framework version and git ignore * remove react-templates untill merged in react * remove 1 featured post --------- Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: patternfly-build <[email protected]> Co-authored-by: Erin Donehoo <[email protected]> Co-authored-by: Nicole Thoen <[email protected]> Co-authored-by: Eric Olkowski <[email protected]> Co-authored-by: Margot <[email protected]> Co-authored-by: Andrew Ronaldson <[email protected]> Co-authored-by: Michael Coker <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Donald Labaj <[email protected]> Co-authored-by: Austin Sullivan <[email protected]> Co-authored-by: Evan <[email protected]> Co-authored-by: kmcfaul <[email protected]> Co-authored-by: Jon Koops <[email protected]> Co-authored-by: Jessie <[email protected]> Co-authored-by: Titani <[email protected]>
Closes #3874