-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
docs: create anchors for all header elems & fix a11y in guides #21751
Merged
annieyw
merged 1 commit into
angular:master
from
DevIntent:guides-fix-a11y-header-issues
Feb 5, 2021
Merged
docs: create anchors for all header elems & fix a11y in guides #21751
annieyw
merged 1 commit into
angular:master
from
DevIntent:guides-fix-a11y-header-issues
Feb 5, 2021
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Splaktar
added
P2
The issue is important to a large percentage of users, with a workaround
Accessibility
This issue is related to accessibility (a11y)
docs
This issue is related to documentation
target: patch
This PR is targeted for the next patch release
labels
Jan 30, 2021
google-cla
bot
added
the
cla: yes
PR author has agreed to Google's Contributor License Agreement
label
Jan 30, 2021
Splaktar
force-pushed
the
guides-fix-a11y-header-issues
branch
from
January 30, 2021 08:41
267849b
to
a36e269
Compare
crisbeto
approved these changes
Jan 30, 2021
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
Splaktar
force-pushed
the
guides-fix-a11y-header-issues
branch
from
January 30, 2021 20:01
a36e269
to
bbef296
Compare
Splaktar
changed the title
docs(guides): create anchors for h2 elements and fix headers' a11y
docs(guides): create anchors for all header elements and fix headers' a11y
Jan 30, 2021
Splaktar
changed the title
docs(guides): create anchors for all header elements and fix headers' a11y
docs: create anchors for all header elems & fix a11y in guides
Jan 30, 2021
Splaktar
force-pushed
the
guides-fix-a11y-header-issues
branch
from
January 30, 2021 21:19
bbef296
to
2fa693d
Compare
jelbourn
approved these changes
Feb 1, 2021
- Lighthouse's a11y audit wants page headers to progress in order - https://web.dev/heading-order/ - Go through all guides and make the headers consistent - and ordered to pass the a11y audit - fix grammar issues and typos
Splaktar
force-pushed
the
guides-fix-a11y-header-issues
branch
from
February 5, 2021 01:33
2fa693d
to
3528bc0
Compare
annieyw
pushed a commit
that referenced
this pull request
Feb 5, 2021
- Lighthouse's a11y audit wants page headers to progress in order - https://web.dev/heading-order/ - Go through all guides and make the headers consistent - and ordered to pass the a11y audit - fix grammar issues and typos (cherry picked from commit 9db31ee)
annieyw
pushed a commit
that referenced
this pull request
Feb 5, 2021
- Lighthouse's a11y audit wants page headers to progress in order - https://web.dev/heading-order/ - Go through all guides and make the headers consistent - and ordered to pass the a11y audit - fix grammar issues and typos (cherry picked from commit 9db31ee)
wagnermaciel
pushed a commit
to wagnermaciel/components
that referenced
this pull request
Feb 8, 2021
…ar#21751) - Lighthouse's a11y audit wants page headers to progress in order - https://web.dev/heading-order/ - Go through all guides and make the headers consistent - and ordered to pass the a11y audit - fix grammar issues and typos
wagnermaciel
pushed a commit
to wagnermaciel/components
that referenced
this pull request
Feb 8, 2021
…ar#21751) - Lighthouse's a11y audit wants page headers to progress in order - https://web.dev/heading-order/ - Go through all guides and make the headers consistent - and ordered to pass the a11y audit - fix grammar issues and typos
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Accessibility
This issue is related to accessibility (a11y)
action: merge
The PR is ready for merge by the caretaker
cla: yes
PR author has agreed to Google's Contributor License Agreement
docs
This issue is related to documentation
P2
The issue is important to a large percentage of users, with a workaround
target: patch
This PR is targeted for the next patch release
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before