search

creativecommons / chooser

The new and improved CC license selection tool.
https://chooser-beta.creativecommons.org
MIT License
105 stars 138 forks source link

[Bug] Links are actually buttons #544

Open Serpentarius13 opened 3 weeks ago

Serpentarius13 commented 3 weeks ago

Description

In Choose A License page, there's a section called Confused? Need help? and links there are actually buttons which is a terrible UX. Swap them for actual <a>'s !

Reproduction

Open https://chooser-beta.creativecommons.org/ and scroll to bottom

Expectation

Links should be <a> hyperlinks

Screenshots

image

Resolution

sid0000007 commented 2 weeks ago

@Serpentarius13 @cc-creativecommons-github-io-bot Can you Please assign it to me.I will make sure to complete this

possumbilities commented 1 week ago

After looking through this further, there is a deeper Issue at play here that's difficult to resolve.

These items each looks like a hyperlink in their visual representation. However, under the hood functionally they are in fact buttons. They don't actually navigate anywhere, but instead open popups with further information.

Since this adds complexity to the problem I'm unsure what an adequate route of solution would be. Merely swapping the items from buttons to a would in fact make them more semantically accurate to what they look like, but it would in fact make them less semantically accurate to what they actually behaviorally are, which is buttons.

The underlying issue is that the UX here is at a conflict.

Moving this to https://github.com/creativecommons/chooser/labels/%F0%9F%A7%B9%20status%3A%20ticket%20work%20required until someone comes up with a better route of solution here.

Serpentarius13 commented 1 week ago

After looking through this further, there is a deeper Issue at play here that's difficult to resolve.

These items each looks like a hyperlink in their visual representation. However, under the hood functionally they are in fact buttons. They don't actually navigate anywhere, but instead open popups with further information.

Since this adds complexity to the problem I'm unsure what an adequate route of solution would be. Merely swapping the items from buttons to a would in fact make them more semantically accurate to what they look like, but it would in fact make them less semantically accurate to what they actually behaviorally are, which is buttons.

The underlying issue is that the UX here is at a conflict.

Moving this to 🧹 status: ticket work required Needs more details before it can be worked on until someone comes up with a better route of solution here.

Yea, I'm sorry for misunderstanding. I propose to make them Accordion's, that's how faqs are usually done