Text editor
The element path feature at the bottom of the editor does not have a clear label. This makes it difficult for assistive technology users to understand its purpose. This fails WCAG 2.2 Success Criterion 1.3.1 Info and Relationships and will be resolved by the end of January 2026.
Editor keyboard shortcuts are not communicated to assistive technology users. This makes it difficult to interact with functionality within the editor unless you already know the correct keyboard shortcuts. This fails WCAG 2.2 Success Criterion 1.3.1 Info and Relationships and will be resolved by the end of January 2026. As a temporary solution a tooltip has been added above the most common instances of the editor to help communicate useful shortcuts.
When tabbing through buttons in the editor it isn’t possible to move past the last button under certain circumstances. This causes navigation to become interrupted, and the user should instead be returned to the first button in the menu to allow cyclical navigation. This fails WCAG 2.2 Success Criterion 2.4.3 Focus Order and will be resolved by the end of January 2026.
- Feedback is not provided for assistive technology users when using buttons or keyboard shortcuts to perform actions such as bold or insert a link. This is confusing as users can’t confirm an action has been applied. This fails WCAG 2.2 Success Criterion 4.1.3 Status Messages and will be resolved by the end of January 2026.
Contextual toolbars that allow users to quickly apply formatting such as headings or bold are not easily communicated to assistive technology and keyboard users. This causes some users to miss out on quick editing options unless they know the correct keyboard shortcut. This fails WCAG 2.2 Success Criterion 2.1.1 Keyboard and will be resolved by the end of January 2026.