-
Notifications
You must be signed in to change notification settings - Fork 691
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
Issue 10254: Improve coach tabs accessibility of Reports Lesson Tab #11606
Issue 10254: Improve coach tabs accessibility of Reports Lesson Tab #11606
Conversation
Hi, @MisRob Another one has been fixed! Please review it. I think all the mentioned follow-up issues are fixed. Yayy 🎉 |
Build Artifacts
|
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 all the mentioned follow-up issues are fixed. Yayy 🎉
Yes, amazing!
Thank you @muditchoudhary, code is looking good and it seems to work well too. I added one non-blocking, nice-to-have, suggestion. And I'll also ask @radinamatic to test before we merge.
@@ -227,6 +271,12 @@ | |||
} | |||
}, | |||
}, | |||
$trs: { | |||
coachReportsLesson: { |
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.
Apologies I forgot to mention this in previous work (and probably also use myself in the PR I recommended as a template). We're migrating away from placing strings into components. Could you please move this string to commonCoachStrings
and import it from there?
In regards to importing the string, we'd appreciate if you could use this fairly new way of using setup()
https://kolibri-dev.readthedocs.io/en/develop/i18n.html?highlight=translate#common-string-modules. Even though you may see translation mixins being used all over the codebase, whenever possible we'd like to use this pattern for all new code additions.
Okay I'll have a commit soon. Please wait till then before merging. |
Thank you @muditchoudhary! I also wanted to mention I won't be able to follow-up here this year as this is my last day before few weeks of time off. Someone else may jump in, but the whole team's availability will too soon be limited until the second week of January. Thank you and hopefully see you next year :)! |
Any reason why is this PR targeted to |
@radinamatic Yes, the original intention was to target |
More accurately, a contributor couldn't create data because of broken quiz creation and therefore it was impossible to navigate to the place they needed to update because it assumed existence of at least one quiz, I believe @muditchoudhary this is not related to your work |
acb9036
to
e727dd0
Compare
There was a conflict. I resolved it |
Please review it. I do not exactly understand how we use string from a common module with setup. |
Thank you, @muditchoudhary. I've just returned from my vacation and will have a look at it again in the next couple of days. |
Okay. Alright. I hope you had a great vacation. Until then I'll look into some new issues. Thank you! |
The latest updates are looking good to me, thank you @muditchoudhary. @radinamatic could you please try this out? |
Hi @muditchoudhary, we'll get to test and merge this, we just need to prioritize QA of the release branch rather than the |
Okay, got it. Thank you for letting me know. |
Installed the EXE asset from this PR on Windows 10 in both Chrome and Firefox, but I'm unable to open a report for a lesson, using neither the keyboard, nor the mouse. Report for quiz apparently opens correctly.
|
Currently working on this: #10491 I'll check it after completing it. |
I think it will have something to do with the new way of using strings I recommended. I see you followed the documentation so if you don't mind, I would have a look @muditchoudhary rather sooner what's going on so we can eventually fix it (we'd like to use strings in this way in other work) |
okay 👍 |
@muditchoudhary We have a typo in documentation. I fixed it in this PR and will open a PR to fix documentation too. @radinamatic you can now test the page, thank you. |
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.
Manual QA & A11y testing passed, yey for more accessible tabs in Kolibri! 💯 👏🏽
Thank you for your contribution @muditchoudhary!
Yey! Thanks @radinamatic and @muditchoudhary! |
Docs failure is not related to this PR and should be fixed on develop, so merging. |
Summary
Use KTabs to improve the accessibility of the Reports Lesson Tabs.
References
Closes #10254
Reviewer guidance
To review, Go to Coach -->Select a Class --> Reports --> Lesson --> Select a lesson. Then test the tabs with keyboard tabs key.
Testing checklist
PR process
Reviewer checklist
yarn
andpip
)