You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The interface completely lacks visible focus indicators when navigating with the Tab key. All components should be reconsidered. A recommended approach is to replace Semantic-UI components with the new aria-components for better accessibility.
The search bar need to be updated to a modern an more accessible one:
Use aria-live="polite" on the results container so screen readers are notified of changes without being disruptive.
Use aria-controls to link the search field with the results container, improving accessibility.
Add the number of results for screen readers. This can be visually hidden with .visualy-hidden class (if defined)
If this form becomes a live search, the magnify lens icon is not necessary.
use the Table component from aria-components to build the table
The description text needs to be rethought. The two icons are not compliant with accessibility rules. Text and images should not be used together to represent a description; only one should be used. If images are necessary, their description must be accessibility-compliant.
The Save and Cancel buttons are in the wrong order when navigating using the Tab key. The Cancel button should come first, followed by the Save button, left to right.
@jmevissen is currently working on this. @sneridagh@fredvd we need to investigate a little what is missing in order to assign issues, I cannot assign this to Jan at this time.
Activity
[-][CMSUI] - Sharing[/-][+][CMSUI] - Sharing route[/+]Wagner3UB commentedon Sep 11, 2025
A11Y analysis (volto 18 layout):
<search>tag when building the form to improve semantic structure and accessibility https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/searcharia-live="polite"on the results container so screen readers are notified of changes without being disruptive.aria-controlsto link the search field with the results container, improving accessibility.@plone/cmsui- Aurora CMSUI as a standalone app #3@plone/cmsui- Aurora CMSUI as a standalone app #3pnicolli commentedon Jun 8, 2026
@jmevissen is currently working on this. @sneridagh @fredvd we need to investigate a little what is missing in order to assign issues, I cannot assign this to Jan at this time.
Add sharing route (#29) (#127)