Quantcast
Channel: Issues for Drupal core
Viewing all articles
Browse latest Browse all 296414

Incorporate best practices from A11yFirst into WYSIWYG

$
0
0

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.

Screenshot of A11yFirst Editor

Compare this with Drupal 9:

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

Screenshot of Drupal 9's CKEditor 5 implementation

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


Viewing all articles
Browse latest Browse all 296414

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>