TODO: Expand this section with a bit of scope, e.g. MVP for Layout Builder stable release.
This is the main tracker issue for layout builder accessibility issues.
What inputs methods should we support? (What does rest of core support?) WCAG guideline 4.1 says "Maximize compatibility with current and future user agents, including assistive technologies".
Currently for instance re-ordering the blocks relies on Drag and Drop
We expect there will be substantial cross-over between this accessibility plan, and the usability plan at #2940212: [meta] Miscellaneous UI issues for the Layout Builder module → . It's a good idea to study the related child issues for both plans.
TODO: Update this section to describe where we are going, based on the accessibility review collaboaration with the UC Berkeley WebAccess team.
TODO: Describe the accessibility features that help users with different impairments and/or technology choices. Make use of personas and use-case scenarios. Show examples of how the accessiblity features add value for everyone, not just people with disabilites.
Note: this triage is from an accessibility point of view only.
All done? New issues need triage, obviously.
Lots! Otherwise TBD. Design work may be required.
Some optional properties in the *.layouts.yml files look useful, particularly the "description" property which may help us convey a layout overview to visually impaired users. But since layout_discovery module is already stable, we presumably can't make the description property mandatory as that would be a backwards compatibility break. We can improve developer documentation about about best practice, and explain why the description property is highly recommended.
Hopefully none?
Active
11.0 🔥
Last updated
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
Used to alert the accessibility topic maintainer(s) that an issue significantly affects (or has the potential to affect) the accessibility of Drupal, and their signoff is needed (see the governance policy draft for more information). Useful links: Drupal's accessibility standards, the Drupal Core accessibility gate.
Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.
Blocks and Layouts Initiative. See the #2811175 Add layouts to Drupal issue.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Right, these are accessibility bugs (some of them major) that still need to be fixed. It would be great to fix them as part of an effort to add Layout Builder to the Standard Profile.
Absolutely @xjm. But each of those bugs probably will have their own issue.
Adding reference to Windows High Contrast Mode.