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

Primer DetailsComponent does not support opener customization from caret #2339

Open
megan-arellano opened this issue Oct 27, 2023 · 8 comments
Assignees
Labels
rails Stale Automatically marked as stale.

Comments

@megan-arellano
Copy link

Hello! I have been working on an accessibility issue where the remediation was to use a DetailsComponent. The DetailsComponent replaced an chevron-right that, when clicked, reveals more text. To approximate the same functionality, I did component.with_summary(button: false) to get a standard details element with a caret opener. However, the standard caret does not match GitHub's progressive disclosure standard; instead, the opener should still be a chevron-right. As best I can tell, the DetailsComponent doesn't support this currently. Could the DetailsComponent support customizing the opener?

@lesliecdubs
Copy link
Member

lesliecdubs commented Oct 28, 2023

Thanks for filing this request!

I'd like to get Primer Design's confirmation that the Details component should technically not rely on the caret (as it currently does in Rails) as per this progressive disclosure advice - and should instead use a chevon icon pointed right. Is that correct?

Temporarily removing the rails label so this gets into the design queue first for assurance before eng starts.

@lesliecdubs lesliecdubs removed the rails label Oct 28, 2023
@megan-arellano
Copy link
Author

😅 Sorry about the delayed response @lesliecdubs !

I'd like to get Primer Design's confirmation that the Details component should technically not rely on the caret (as it currently does in Rails) as per this progressive disclosure advice - and should instead use a chevon icon pointed right.

^ Yes, this is what I believe should happen.

@megan-arellano
Copy link
Author

@lesliecdubs Apologies again for letting this languish. Small nudge/I'm curious -- is there any other information I can provide? Will this issue be the best way for me to follow any decisions regarding this request?

@lesliecdubs
Copy link
Member

@megan-arellano 👋 no other information is needed from my understanding, although Primer Design will be best positioned to weigh in on that when they have the chance. I can confirm this is in the team's inbox for further design review.

This issue should be the best place to stay updated.

cc @tallys

@mperrotti
Copy link
Contributor

@megan-arellano - can we get a screenshot of what you're building so we can have more context?

@megan-arellano
Copy link
Author

Hi @mperrotti, I was replacing an existing component with a Primer Details one. In the video below is the original behavior, where a user can click or tab on a right facing chevron to reveal more information about their classroom assignments.

280866880-6203a3d3-c0e8-4ec7-a570-65575b0b5a8a.mov

When replacing the existing container with the Details component, the chevron becomes a triangle pointed right, which is the violation of progressive disclosure as I understand it. This is shown in the video below.

280871023-206d3aa7-c8b3-4f94-9f31-dadcaa441544.mov

@mperrotti
Copy link
Contributor

Ok, I think I understand the issue now. I think we just need to update the Rails implementation to align with the progressive disclosure guidelines.

What do you think @jonrohan ?

@jonrohan jonrohan self-assigned this Nov 27, 2023
Copy link
Contributor

Hi! This issue has been marked as stale because it has been open with no activity for 180 days. You can comment on the issue or remove the stale label to keep it open. If you do nothing, this issue will be closed in 7 days.

@github-actions github-actions bot added the Stale Automatically marked as stale. label May 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
rails Stale Automatically marked as stale.
Projects
None yet
Development

No branches or pull requests

5 participants