Document intended usage for disabled Text

[duranmla]

Relates to #96

[rafael-sepeda]

In order to make more clear the purpose of the disabled text color in addition to providing a descrition for this color slot I propose also to:

1. Rename weak to secondary. Word weak might be confused with disabled. Also secondary is more-or-less a standard name for this color slot.
2. Change $color.text.disabled to $colors.brand.authenticBlue.200. Currently it is set to 350 and it has not enough contrast/difference with secondary (weak) . We use actually already use $colors.brand.authenticBlue.200 in disabled states in inputs, and buttons, checkbox and other. $colors.brand.authenticBlue.350 it used for for disable-inverted states in some form controls, text input placeholder and default Tab in the tab bar. And this clashes with the idea of disabled.
3. Give name to the default text color - primary.
4. Describe all the color text slots.

So to be more systematic we can define the purpose of the text color slot this way:

• primary - color for most interface text whether body or headlines.
• secondary - for supplemental information with diminished contrast (often, the “gray text”). Like form microcopy, captions, helper text and other medium emphasised text elements.
• disabled - for text in blocks, form elements or other components that are not available to a user at the moment (due to either permissions, dependencies, or pre-requisites) and need to feature “incidental” states.

Regarding color contrast WCAG 2.0 clearly defines that "incidental" text that is not required to meet the contrast requirements.

[rafael-sepeda]

As and alternative instead of primary we can use default.

[rafael-sepeda]

This issue/discussion is also, probably, related to #97

[rafael-sepeda]

@agonzalezUX any comments from your side?

[rafael-sepeda]

@duranmla , @nlopin so then, what will be the next steps for this topic?

[duranmla]

We need to execute, sorry for the delays.

[github-actions]

🎉 This issue has been resolved in version 1.17.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This issue has been resolved in version 3.0.0-next.1 🎉

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot 📦🚀