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
Bug 1847074: PF fix for filter bar layout issues at some screen widths on search page #6771
Bug 1847074: PF fix for filter bar layout issues at some screen widths on search page #6771
Conversation
@jcaianirh: This pull request references Bugzilla bug 1847074, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/test analyze |
/retest |
1 similar comment
/retest |
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.
Thanks @jcaianirh. I think we should hold this one for 4.7 due to the PF bump.
@@ -19,7 +19,7 @@ const AlertSeverityIcon: React.FC<AlertSeverityIconProps> = ({ | |||
fontSize, | |||
color: 'var(--pf-global--danger-color--100)', | |||
}} | |||
alt="Monitoring Alert" | |||
aria-label="Monitoring Alert" |
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'm not sure this is right. Are these SVGs? I believe they should be alt
.
cc @jessiehuff
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.
Truthfully, svgs are tough, and I've never seen a consensus on that debate between documentation and experts. One of the best comparisons I've seen is from deque (who created Axe) which essentially ends up stating that they found that one solution was not necessarily superior over the other. They cover all combinations of alt, roles, title/desc, and aria, and conclude:
"On the flip side, there was no clear frontrunner for “best in show” for the different patterns when relaying basic alternative content. This is actually good news! Since many of the patterns were able to render the alt content, that equates to more pattern choices for designers and developers. For SVGs needing more descriptive alternative content, pattern 11 <svg> + role="img" + <title> + <desc> + aria-labelledby="[ID]"
was the most reliable choice for the different browser and screen readers that were tested."
I've often still recommended alt because it's not just for screen readers, it's frequently used for low bandwidth users as well (when an image can't load, it will show the alt instead). I have read in some articles that svgs have limited support with alt or that it needs role="img"
for it to be valid, but it looks like there's a lot of different ways for us to make this accessible. I think if it sounds good in testing, I'm ok with whatever solution we choose.
Some other notable documentation/articles that are interesting to include is this comparison by Scott O'Hara, the more old school recommendations by Leonie Watson (both O'Hara and Watson are considered a11y experts), and the Appendix H on svg accessibility by W3.
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.
Thanks @jessiehuff. @jcaianirh I'd stick with the existing alt
unless there is a specific reason we need to change. Does this cause problems with the new Patternfly version?
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.
@spadgett pf has been updated to support alt tags again. I will put this on hold and update the pr.
/bugzilla refresh |
@jcaianirh: This pull request references Bugzilla bug 1847074, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/hold |
@jcaianirh: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
1a38e53
to
a82fbf5
Compare
frontend/packages/container-security/src/components/summary.tsx
Outdated
Show resolved
Hide resolved
/hold cancel |
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jcaianirh, spadgett The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@jcaianirh: All pull requests linked via external trackers have merged: Bugzilla bug 1847074 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1847074
After: