← Back to Blog

Accessibility in the Block Editor

Create accessible content in Gutenberg while recognizing that the editor preview is not the complete public page.

Veyra Admin

2 min read

  • Article
  • 2 minutes read
  • Reviewed August 4, 2026

The Block Editor provides structured content blocks and several accessibility-oriented controls.

It can help editors create accessible pages, but it does not prevent every error. The theme, block implementation and editorial choices determine the public result.

Use the Correct Block

Choose blocks by meaning:

  • Heading for headings.
  • List for lists.
  • Quote for quotations.
  • Table for data.
  • Button for calls to action.
  • Image for images with appropriate alternative text.

Avoid using visual styling to imitate another semantic structure.

Document Outline and List View

Use the document outline to review heading levels.

List View helps identify nested blocks, groups and unexpected structure. It is especially useful when visual selection becomes difficult.

Colour Controls

The editor can warn about selected contrast combinations in some contexts.

Treat warnings as assistance, not complete testing. Theme styles, overlays, gradients and states may change the final contrast.

Images and Media

Review alternative text, caption, crop and link behavior.

Do not repeat alt text in the caption unnecessarily. Test responsive output and the public template.

Write descriptive labels. Avoid several identical “Learn more” buttons without contextual names.

Check whether a block styled as a button is actually a link or an action.

Tables

Use the Table block for data and enable header sections where appropriate.

Complex tables can require custom markup or a different presentation.

Patterns and Locked Layouts

Patterns can guide editors toward tested accessible structures.

Locking layout controls can protect critical heading, form or navigation structures while still allowing content editing.

Editor Preferences and Keyboard Shortcuts

Editors can configure interface preferences and use keyboard shortcuts.

Documentation and training should include the workflows used by keyboard and screen-reader users, not only pointer-based instructions.

Preview and Test Public Output

The editor canvas does not include every theme, plugin or responsive behavior.

Always test the published page with keyboard, zoom and assistive-technology checks.

Frequently Asked Questions

Does Gutenberg guarantee accessible content?

No. It provides useful semantics and tools, but editors and extensions can still create barriers.

Should every custom block be tested?

Yes, including its editor interface and public output.

Continue Learning

Previous: [Choosing Accessible Themes and Plugins](/resources/wordpress-manual/accessibility/choosing-accessible-themes-plugins/)

Next: [How to Test a WordPress Website for Accessibility](/resources/wordpress-manual/accessibility/test-wordpress-accessibility/)