Skip to content

Start adding accessibility section to control panel page#745

Open
gcamacho079 wants to merge 29 commits intomainfrom
a11y/additions
Open

Start adding accessibility section to control panel page#745
gcamacho079 wants to merge 29 commits intomainfrom
a11y/additions

Conversation

@gcamacho079
Copy link
Contributor

@gcamacho079 gcamacho079 commented Nov 30, 2025

Description

Adds content related to accessibility features

Related issues

Resolves PT-1906

@gcamacho079 gcamacho079 added the 📦 CMS Craft CMS content related issue label Nov 30, 2025
@netlify
Copy link

netlify bot commented Nov 30, 2025

Deploy Preview for craft-docs ready!

Name Link
🔨 Latest commit 6ea0d6c
🔍 Latest deploy log https://app.netlify.com/projects/craft-docs/deploys/6983a856a0e6780008b5410d
😎 Deploy Preview https://deploy-preview-745--craft-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@linear
Copy link

linear bot commented Nov 30, 2025

@gcamacho079 gcamacho079 marked this pull request as ready for review December 17, 2025 17:35
@gcamacho079 gcamacho079 requested a review from a team as a code owner December 17, 2025 17:35
@AugustMiller
Copy link
Contributor

Coming through these changes and taking another stab at the main development/accessibility.md page I created ages ago!

Craft’s [control panel](../system/control-panel.md#accessibility) is [designed and built to be accessible](https://craftcms.com/accessibility), out-of-the-box.
In addition to built-in interfaces, the content tools you configure for authors are backed by components that we [regularly audit](https://craftcms.com/accessibility/reports) for conformance.

### Image editor
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@AugustMiller I'm wondering if this info can be moved to and combined with the info that's already in the Image Editor section.

Since these details don't affect the accessibility of the front-end, I think we should limit the Image Editor accessibility info to things like the interaction pattern (non-drag abilities for focal point editing, keyboard editing and how to access it, etc.) and either:

  1. Add an accessibility heading under the Image Editor section that outlines those things, or
  2. Add an Image Editor heading under the Accessibility section on the control panel page

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

📦 CMS Craft CMS content related issue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants