fix(docs-infra): apply various a11y aio improvements#45209
fix(docs-infra): apply various a11y aio improvements#45209dario-piotrowicz wants to merge 5 commits into
Conversation
635d4b3 to
3233964
Compare
jessicajaniuk
left a comment
There was a problem hiding this comment.
LGTM 🍪
I love seeing this a11y work, @dario-piotrowicz. Keep up the great work!
|
@gkalpak could you have a quick look at this one please? 😊 |
|
You can preview 2e2280f at https://pr45209-2e2280f.ngbuilds.io/. |
gkalpak
left a comment
There was a problem hiding this comment.
Great work, @dario-piotrowicz 👏
BTW, in the future, it is a good idea to break up such changes into separate commits 😉
There was a problem hiding this comment.
While this increases the contrast between the anchor text and the background, it makes it harder to distinguish the anchor text from the regular text, which is not good a11y/UX either. Could we maybe make this a little lighter (and still meet contrast requirements)?
There was a problem hiding this comment.
I'll have a look 🙂👍
There was a problem hiding this comment.
It is a bit too vibrant for my taste. It feels a lit out of place with the test of our color-palette 😞
(We could really use a designer 👀 😛)
|
@gkalpak thanks a lot for the speedy review! ❤️ 😍 ❤️ 😍 ❤️ 😍 ❤️ 😍 |
About the commits, yeah sorry I did started that way but then things were intertwining and I just figured I could just mash it into a single one 😅, as part of my next changes to this PR I can put the effort and try to divide stuff in ways that make sense, I am totally fine with that, it should not be too much of an issue if you want 🙂 (also the commits would be a bit small, hopefully you don't mind that 😄) |
No, no need for that. Just something to keep in mind for future PRs 😉
We certainly don't mind small commits (as long as they are self-contained) 😃 |
3233964 to
64f091f
Compare
|
@gkalpak I've addressed your comments, please have another look 😊 |
5c53094 to
718f709
Compare
|
You can preview 718f709 at https://pr45209-718f709.ngbuilds.io/. |
There was a problem hiding this comment.
Note: If we decide to keep this (or any color we end up with), we need to make sure that links inside code-blocks have the same color (and the color has to be accessible with both the default white-ish background and the gray code-block background).
currently the navigation ul used in aio-top-menu has a role of navigation, but listitems should be owned by list parents (see more: https://www.w3.org/TR/wai-aria-1.1/#listitem) so wrap the ul in a nav and remove the role="navigation" from the ul element to fix such issue resolves angular#44562 resolves angular#16938 (the second point)
wrap the main aio mat-toolbar in a header element to provide better accessibility resolves angular#16938 (the first point)
remove redundant main role as pages should always have a single element with a main role (also remove the role assigne to the main tag as that is implied)
assign different aria labels to the primary nav and the one used for guides and docs, so that impaired users can more easily distinguish the two
718f709 to
7409b7e
Compare
|
You can preview 7409b7e at https://pr45209-7409b7e.ngbuilds.io/. |
7409b7e to
1bb321e
Compare
update (decrease) the value of some of the accessibility MIN_SCORES_PER_PAGE after recent changes
1bb321e to
8077771
Compare
|
@gkalpak I've removed the color changes as those seems to be a bit tricky and could be handled separately, please have another look 🙂 (also now unfortunately the a11y scores are now going slightly down instead of going up 😭) |
|
You can preview 8077771 at https://pr45209-8077771.ngbuilds.io/. |
|
This PR was merged into the repository by commit 16e635c. |
currently the navigation ul used in aio-top-menu has a role of navigation, but listitems should be owned by list parents (see more: https://www.w3.org/TR/wai-aria-1.1/#listitem) so wrap the ul in a nav and remove the role="navigation" from the ul element to fix such issue resolves #44562 resolves #16938 (the second point) PR Close #45209
remove redundant main role as pages should always have a single element with a main role (also remove the role assigne to the main tag as that is implied) PR Close #45209
assign different aria labels to the primary nav and the one used for guides and docs, so that impaired users can more easily distinguish the two PR Close #45209
update (decrease) the value of some of the accessibility MIN_SCORES_PER_PAGE after recent changes PR Close #45209
remove redundant main role as pages should always have a single element with a main role (also remove the role assigne to the main tag as that is implied) PR Close #45209
assign different aria labels to the primary nav and the one used for guides and docs, so that impaired users can more easily distinguish the two PR Close #45209
update (decrease) the value of some of the accessibility MIN_SCORES_PER_PAGE after recent changes PR Close #45209
|
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. |


changes:
ulused inaio-top-menuhas a role ofnavigation, but listitems should be owned by list parents
(see more: https://www.w3.org/TR/wai-aria-1.1/#listitem)
so wrap the
ulin anavand remove therole="navigation"from theulelement to fix such issueaccessibility
resolves #16938
resolves #44562
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
Does this PR introduce a breaking change?