Hi @Volker_E

I've added all the missing states to the progressive and destructive link component in Figma:

• Progressive link: added Disabled state
• Destructive link: added Hover, Active, Focus, Visited and Disabled (we had in Figma the default states but the rest of states were missing)

As we need to add the visited state for destructive link, we need to add the #AA5555 in our global and decision color tokens.

• As global token, we could add it as color-red650 (between red700 and red600).
• As decision token, we could add it as content-color-visited--destructive (in the visited section)

Here you can view the Figma file with the all link states added and the proposal to add #AA5555 as color token.

cc: @iamjessklein

Link colors are a mess, and priority for me has to be T213778, a wholesome approach.
Also, the current Vector 2010 new (red) color has been the influence for the current red visited, which is #aa5858.

Please compare above, we should define the new link visited around #d33, in design harmony and under contrast req perspective.

In T302328#7830509, @Volker_E wrote:

Link colors are a mess, and priority for me has to be T213778, a wholesome approach.

I'm not proposing to update our link colors, with this task I was only trying to define in Figma what we currently have in production. And, defining all states I realized that we currently don't have the visited red link #aa5858 in our color tokens, so we need to think in how to solve it.

Please compare above, we should define the new link visited around #d33, in design harmony and under contrast req perspective.

We shouldn't use #d33 for red visited link since we are already using #d33 for default red link, and we need to visually differentiate between non visited and visited links for both blue and red links.

About using #aa5858 for visited red links, we have the following solutions (I update the solutions since yesterday I talked about it with @iamjessklein
and also with the rest of the design system team during our DST Weekly meeting):

• Option 1: Add #aa5858 as red color: As global token, we could add it as color-red650 as global token and content-color-visited--destructive as decision token (in the visited section of content colors).

• Option 2: Add #aa5858 as visited color. We would rename the "Purple" section to "Visited" and we would have color-visited-purple and color-visited-red.

cc: requesting feedback from @iamjessklein

But wouldn't #aa5858 be a legacy token to start with? Looking at Option 1 it already shows my issue with adding it vividly. The color just doesn't fit in. It has never seen Wikimedia Design team's attention, that was/is an inherited color.
If we tackle it, we should look at the whole link component with all its states and complexity and choose a WikimediaUI palette harmonious color.

In T302328#7841827, @Volker_E wrote:

But wouldn't #aa5858 be a legacy token to start with? Looking at Option 1 it already shows my issue with adding it vividly. The color just doesn't fit in. It has never seen Wikimedia Design team's attention, that was/is an inherited color.
If we tackle it, we should look at the whole link component with all its states and complexity and choose a WikimediaUI palette harmonious color.

@Volker_E I know #aa5858 is not a Wikimedia Design color and it doesn't fit well in the red palette. But, if we decide to add the purple link in our palette (which is not a color form our Wikimedia Design either) the logical solution would be add the visited red link color too, since both purple and red will be used only for visited blue and red links states.

As red visited link doesn't fit in our red palette, what we can do is use the option 2 and add #aa5858 as visited color. We would rename the "Purple" section to "Visited" and we would have color-visited-purple and color-visited-red.

I think that you should move forward with documenting the current red link states and then any changes that need to be made should be added as future issues.

Moving from sprint board to backlog per our defined goals at sprint planning; please holler if there's a reason to bump up the priority.

Removed the Codex project tag since this is a task related with the OOUI Figma library and the Link component for Codex is being worked in T313507