Wizard page step indicators fail WCAG AA color contrast

Changing the text color of webform-progress-tracker .progress-step .progress-text to #5c5c5c might be all that's needed.

The color contrast between the blue (#2196f3) background behind the active page number (which is #fff) is also too low, at 3.12.

This is also an issue with the form tool tip

The 6.1 version of this project is no longer recommended. Can someone re-test on 6.2.0 and also indicate with which theme you tested?

My screenshot was from 6.2.0-beta6, if that helps.

A foreground text color of #777 against a standard light background #FFF does not pass WCAG AA nor AAA.

Changing foreground #777 to #767676 against white background passes WCAG AA, but not WCAG AAA.
Changing foreground #777 to #595959 against white background passes WCAG AA and AAA.

I think we should meet Level AAA.

After digging in here, it became quickly apparent that:

* The default colors provided by the progress-tracker library that webform uses are also not compliant.
* Webform module overrides some of the colors, most likely for consistency sake. It is not entirely clear why (the additions were made 7 years ago by Jacob).
* Hover effects on elements that cannot be clicked are useless and should be corrected.
* Hovering the "progress-marker" has a different/inconsistent effect than hovering the "progress-text".

These things were all fixable with css changes captured in the previous commit d6179319 "Simplify complete/hover/focus states and pass WCAG AA".

I have rebased the merge request.

@jwilson3 do your additional finding suggest further changes that you would like to make?

do your additional finding suggest further changes that you would like to make?

No, everything I listed there had already been fixed by my commits. My apologies if that wasn't clear.

The issue should be Needs Review at this point for someone else to have a look, and do an accessibility and functional review.

However...

After I'd done the work, you requested in #10 we add WCAG AAA support, which I haven't been able to come back around to work on. My work is explicitly WCAG AA.

I don't know if it makes sense to try for AAA-level support here, or move it to a follow-up. To avoid scope creep, AAA should be addressed on this issue ONLY IF the module supports AAA already. But if the module has many other AAA-compatibility issues, then I suggest moving that to a follow-up, so things can be more holistically approached. Furthermore, AAA color contrast fixes, if done on a component-by-component basis, can end up introducing an even more inconsistent form look-and-feel if not addressed holistically across all components with a color strategy.

I was referring to AAA only for contrast. Usually, it's not hard to find colors which meet that.

okay, right. Color contrast does make sense to keep in scope here, Liam. Thanks.