-
Notifications
You must be signed in to change notification settings - Fork 33
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
TAN-1589: Issue id - 18831: make cards accessible #7879
TAN-1589: Issue id - 18831: make cards accessible #7879
Conversation
|
On this one, I have fixed the key issues pointed out. That is, relating to using the role button on cards. There are a number of cards in the app that could be improved but that will take more effort than needed if they are not issues that been reported directly. Some of the improvements that could be made would be:
|
dd6bba9
to
4e15241
Compare
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.
Before looking at the issues with the existing code, I wonder if we shouldn't first take a step back and reimplement the card as they do in the guide linked to by AnySurfer. Have you been able to take a look at that?
I am actually doing that in the primary event card. I have picked things in the implementation that apply to the use case. The pseudo content trick for example is what we are using to extend the link area in the event card in EventInformation. |
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 am approving this because it works functionally, but there are some code changes that I would very much like to see merged into this one. :) See this PR. (For some reason, the focus states of the event preview cards work better in the branch of that PR as well.)
Co-authored-by: Edwin <katedwin88@gmail.com>
Tan 1589/18831 code review
Changelog
Fixed