CKEditor 5 has its own focus styles, should use the admin theme's (e.g. Claro's)

So CKEditor's styles. Do they meet the color contrast requirements? Is it just that they look different, or can't be easily updated? Consistency is definitely a plus for usability. What WCAG SC would it lie under?

#20: @bnjmnm is a (provisional) accessibility maintainer of Drupal core (just like you!) and he reviewed CKEditor 5's accessibility in detail, and specifically reviewed it for regressions compared to CKEditor 4. Hence also his detailed comment at #6.

On the roadmap issue ( #3238333: Roadmap to CKEditor 5 stable in Drupal 9 → ) there is a long list (23 issues!) of "accessibility" issues to be addressed prior to marking it stable, @bnjmnm identified most of those. See #3239423: Toolbar UI accessibility review: round 2 → in particular.

Clarifying that the original report is tightly coupled to Claro, which explains why the parent issue is #3163810: [META] Assess conformance with WCAG SC 2.4.7 "Focus Visible" → .

Tagging for WCAG SC

https://www.sarasoueidan.com/blog/focus-indicators/

I hear the CKEditor 5 team is investigating this too as they encountered this problem while working on https://www.drupal.org/project/ckeditor5_premium_features → 😊

Really curious to get their feedback!

Wim Leers → credited mherchel → .

Closed 🐛 CKEditor 5 focus indicator is insufficient and is completely invisible in forced colors Closed: duplicate as a duplicate. Transferred tags & credit.

How is what we implemented different than what you can see in their demo https://ckeditor.com/ckeditor-5/demo/feature-rich/

The contrast I see for the focus of the boarder is #3879EB / #FFF which is 4.1.2. That's good enough for SC 1.4.11 Non-Text Contrast (Level AA) if the visual presentation only needs a contrast ratio of 3:1 against adjacent color(s).

I didn't see a corresponding problem in their issue queue https://github.com/ckeditor/ckeditor5/issues

but the bigger issue is that i couldn't replicate this in their demo.

Related: 📌 Add outline to buttons with active state. Fixed just landed.