Skip to content
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

Merged
merged 23 commits into from
May 27, 2024

Conversation

EdwinKato
Copy link
Contributor

@EdwinKato EdwinKato commented May 14, 2024

Changelog

Fixed

  • Fix accessibility issues on event cards

Copy link

@cl-dev-bot
Copy link
Collaborator

cl-dev-bot commented May 14, 2024

Warnings
⚠️

The changelog is empty. What should I put in the changelog?

⚠️ The PR title contains no Jira issue key (case-sensitive)
⚠️ The branch name contains no Jira issue key (case-sensitive)
Messages
📖

Run the e2e tests

📖 Check translation progress

Generated by 🚫 dangerJS against 65bda2b

@EdwinKato EdwinKato marked this pull request as ready for review May 15, 2024 03:54
@EdwinKato
Copy link
Contributor Author

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:

  • Make sure all cards used as lists are in list element syntax. (This would entail looking at each card and it's use case and styling outside where it is used)
  • Look at the structure of each card and ensure we are using proper html syntax for all of them

@EdwinKato EdwinKato force-pushed the TAN-1589-18831-make-event-cards-accessible branch from dd6bba9 to 4e15241 Compare May 15, 2024 05:56
@EdwinKato EdwinKato requested a review from brentguf May 15, 2024 05:57
Copy link
Contributor

@brentguf brentguf left a 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?

front/app/components/HorizontalScroll/index.tsx Outdated Show resolved Hide resolved
front/app/components/HorizontalScroll/index.tsx Outdated Show resolved Hide resolved
front/app/components/HorizontalScroll/index.tsx Outdated Show resolved Hide resolved
front/app/components/EventCard/EventInformation/index.tsx Outdated Show resolved Hide resolved
front/app/components/EventCard/EventInformation/index.tsx Outdated Show resolved Hide resolved
front/app/components/EventCard/index.tsx Outdated Show resolved Hide resolved
@brentguf brentguf added the a11y label May 21, 2024
@EdwinKato
Copy link
Contributor Author

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.

@EdwinKato EdwinKato requested a review from brentguf May 22, 2024 08:35
Copy link
Contributor

@brentguf brentguf left a 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.)

@EdwinKato EdwinKato merged commit 2a34839 into master May 27, 2024
10 checks passed
@EdwinKato EdwinKato deleted the TAN-1589-18831-make-event-cards-accessible branch May 27, 2024 06:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants