creativecommons / creativecommons/chooser

Change wording from "what do the icons means?" to "what do the terms mean?" to better explain question terms

Open
#576 1 comment 0 reactions 0 assignees View on GitHub
✨ goal: improvement 💻 aspect: code 🚧 status: blocked 🟩 priority: low
Dominant language
CSS
Stars
160
Forks
199
PR merge metrics
No merged PRs in 30d

Description

## Description
A request came in via email:

> Hello Creative Commons team,
> I recently visited the renewed [ license chooser](https://creativecommons.org/chooser/) tool on your website.
While the previous iteration showcased the meaning of several important terms on a prominent spot, the new iteration does not.
The same explanations are now found under the question: ‘What do the icons mean?’, but icons only appear after making some choices.
> I understand extra text or hover effects may not be optimal for mobile users.
Instead, could you rename the question ‘What do the icons mean?’ to ‘What do these terms mean' so people unfamiliar with these terms can quickly find an explanation?

## Additional context

There's a lot of other changes we could make to help make this clearer, so I think the root of the issue is an assumption that people would be arriving at the Chooser knowing nothing about the licenses at all (reasonable), and that the terms "Attribution", "Commercial Use", etc. in the questions are not grounded in enough context to make things more readable for those arriving with very little knowledge about the licenses and the terms associated with them.

Others have suggested things like tooltips, or descriptions below the pathway questions, but this suggestion, while not as aggressive, is possibly the most subtle way to resolve that tension.

## Implementation

- [x] I would be interested in implementing this feature.

Contributor guide

Open the contributing guide

Research direction

Start at the license chooser entry point linked in the issue and search the chooser source for the question text “What do the icons mean?”. Change that label to explain the terms instead, then verify the updated wording appears in the chooser and remains clear after making choices.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, html, javascript
Domain
content, frontend
Issue type
Feature
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.