Audit Report
on AccessibilityJoomla! ATAG Audit

When editing an article, the toolbar is at the top of the view. Using keyboard-only navigation, users have no efficient way to navigate to the toolbar to save or cancel the edit.

From the editing view (which is not shown as interactive in the graphic) at tab stop 16, getting back to the save button at tab stop 3 will take thirteen shift+tab interactions, from the last form field (Version Note) at 27, it will be 24 interactions.

While there are additional keyboard shortcuts (such as J then S to “Save and Close”), they are not obvious from the editing screen and also do not include all functionality of the toolbar.

Suggestion: Use skip links to give users easy ways back to the toolbar after the edit field and the sidebar.

Note: While Implementing ATAG suggests that landmarks might be used for this, keyboard navigation does usually not include landmarks by default, so it is not seen as accessibility supported.

When editing content, the session time can run out and lead to unsaved changes. Ensure that changes are automatically saved so that a user an pick up the work from where they left off.

In the Cassiopeia Theme, the editing view does follow the theme which is light mode only. There is no way to follow the dark mode of the system as a dark mode does not exist.

The ATAG standard has no exception for themes that do not have dark mode available, so the theme naturally fails this success criteria. As users can often chose their own theme or use the backend to edit, this failure was marked as Minor.

While the interfaces have some additional accessibility functionality, like the user settings for the backend theme or the additional keyboard shortcuts, these features are not centrally documented and also difficult to find. Some features, like the shortcuts are not documented where they would be useful (on the Dashboard despite applying to editing views).

Ensure that there is a consistent way to find accessibility feature documentation.

While the backend editing flow can show a preview of the generated content with an accessibility checker embedded, the frontend editing does not allow to checke accessibility in the same way.