Contrib.social

Incorporate best practices from A11yFirst into WYSIWYG

Open on Drupal.org →
Created on 15 August 2022, over 2 years ago
Updated 29 February 2024, 10 months ago

Problem/Motivation

The default editor isn't set up to support accessibility best practices.

A11yFirst took CKEditor and revised it so that it would give editors an accessibility-first approach as an editor.

Why not try to borrow from the A11yFirst model for our Full HTML editor and make this the default for Drupal

  • Heading: Assists you in choosing the proper heading levels to make the heading structure in your document more meaningful to readers.
  • Paragraph Format: Provides special formatting for blocks of text (e.g. paragraphs) within your document.
  • Character Style: Provides styling to highlight or emphasize a word or group of words (i.e. characters) within a block of text.
  • Toolbar: Reorganizes the toolbar buttons to place higher-level block actions, such as heading, list and paragraph format, in the top row and lower-level inline actions, such as character style and insert special character, in the bottom row.
  • Help: Provides explanations of how to use the features and why they matter for accessibility.

Compare this with Drupal 9:

  • All on the same line
  • Priority by styling, not structure
  • No help
  • Starting with an H1

Proposed resolution

Lets reformat the buttons and customize this to better meet the needs of authors.

Remaining tasks

User interface changes

Backend WYSIWYG Editor

API changes

None

Data model changes

None

Release notes snippet

✨ Feature request
Status

Closed: works as designed

Version

11.0 🔥

Component
CKEditor 5  →

Last updated about 19 hours ago

Created by

🇨🇦Canada mgifford Ottawa, Ontario

Live updates comments and jobs are added and updated live.
  • Accessibility

    It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Comment over 1 year ago →
    🇺🇸United States smustgrave

    Should this be reopened?

  • Status changed to Closed: works as designed 10 months ago
  • Comment 10 months ago →
    🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺

    It's still open?

    There is literally nothing to do here for Drupal. Like I implied in #5 and wrote explicitly in #10: this must be implemented upstream, not in Drupal.

    IOW: this feature request is filed against the wrong project. Closing, albeit with a sad heart…

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024