-
Notifications
You must be signed in to change notification settings - Fork 715
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
Coach accessibility improvements #10212
Conversation
to improve a11y
to improve a11y
to improve a11y
to improve a11y
to improve a11y
to improve a11y
to improve a11y
Build Artifacts
|
I'm not sure yet why the Licenses check failed, it doesn't seem to be related to code changes, but I will check on it later. |
:tabsId="PLAN_TABS_ID" | ||
:activeTabId="PlanTabs.QUIZZES" | ||
> | ||
<div class="filter-and-button"> |
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.
If that'd make review easier, I'm fairly confident I didn't make any updates to the code that is now newly wrapped within KTabsPanel
, and these large diffs are caused by deeper nesting that resulted from that. This applies to all other files containing KTabsPanel
.
The license check failure here has been fixed on develop, so this should be fine to merge, irrespective of that. |
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.
HI @MisRob! Great job on this, pr generally LGTM!
Thank you, @akolson. @radinamatic I know we did some testing already as I was developing the component. However, this PR introduces it to more places and also has some logic that wasn't in the previous work. Would it make sense to test it before merging? |
Hey @MisRob, apologies for the delay! 🙏🏽 @pcenov did the regression testing and everything seems to be running smooth 👍🏽 Regarding the keyboard navigation and markup in regards to a11y, I tested the visually hidden headings and the new below implemented tabs, all good! 💯
@marcellamaki reminded me that the scope of this PR covered only the above pages, so could I ask you to open a follow up issue to also implement the tabs on the following pages:
|
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.
More accessible tabs, yey! Thank you @MisRob 👏🏽 💯
Please do not merge yet, I need to test it after resolving conflicts. I will merge after I'm done. |
@radinamatic Thank you. Yes, I can open the follow-up issues. |
Summary
Improves accessibility of Reports and Plan pages in Coach by
References
Reviewer guidance
Test the following tabs (visual and functional regressions, keyboard navigation, markup in regards to a11y)
Test the visually hidden h2 titles General information and Details on Reports lesson pages
Test the visually hidden h2 titles General information and Details on Reports quiz pages
Test the visually hidden h2 title General information on a Plan lesson page
Test the visually hidden h2 title General information on a Plan quiz page
Testing checklist
If there are any front-end changes, before/after screenshots are includedPR process
Reviewer checklist
yarn
andpip
)