Problem/Motivation

See #1037.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Comments

Wim Leers created an issue. See original summary.

Wim Leers credited bnjmnm.

wim leers’s picture

Based on analysis of https://github.com/ckeditor/ckeditor5/labels/domain%3Aaccessibility by @bnjmnm ~2 weeks ago. @bnjmnm is an accessibility maintainer of Drupal core.

Crediting @bnjmnm.

xjm’s picture

Issue tags: +Drupal 10 beta blocker
catch’s picture

https://github.com/ckeditor/ckeditor5/issues/1037 and https://github.com/ckeditor/ckeditor5/issues/12258 are both closed, so I think we just need a dependency update here.

wim leers’s picture

Status: Postponed » Needs review
Issue tags: -Needs upstream bugfix

Checked the status of this together with @nod_ and @lauriii.

Confirmed that all blockers have been solved upstream, so this is ready for re-assessment (to ensure the next CKEditor 5 release will have this accessibility aspect solved) 👍🥳

bnjmnm’s picture

Tried the fix on the CKEditor 5 nightly build and it works great. Excited to get this into core when it's released.

wim leers’s picture

Title: [upstream] CKE5 dropdown screenreader support » [PP-1] [upstream] CKE5 dropdown screenreader support
Status: Needs review » Reviewed & tested by the community

Yay, thanks @bnjmnm!

Blocked on the Aug 31 release per https://github.com/ckeditor/ckeditor5/issues/12107 then! 🥳 To signal this aspect is done, marking RTBC & titling as postponed.

wim leers’s picture

Created the issue to update core's CKEditor 5, i.e. the issue that this issue is actually blocked on: #3306153: Update CKEditor 5 to 35.1.0.

wim leers’s picture

Title: [PP-1] [upstream] CKE5 dropdown screenreader support » [upstream] CKE5 dropdown screenreader support
Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.