>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3374716. --> Reported by: [bnjmnm](https://www.drupal.org/user/2369194) Related to !279 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>I ran into this with the Wave scanner. While there's no user need to have sufficient contrast on visually hidden elements, if a scanner reports a contrast error it gives the impression that Gin is less accessible than it really is. While it's true this is ultimately a problem with the A11y scanner, we can update the text color of visually hidden elements pretty easily and in a non-disruptive way, so why not do this to ensure Gin accessibility scans do not report irrelevant errors.</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <p>Run the Wave scanner on any page with the secondary toolbar present and note the contrast errors <a href="https://wave.webaim.org/extension/">https://wave.webaim.org/extension/</a></p> <p>Run that same scanner on pretty much any page in dark mode and note even more contrast errors.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <h3 id="summary-ui-changes">User interface changes</h3> <h3 id="summary-api-changes">API changes</h3> <h3 id="summary-data-model-changes">Data model changes</h3>