Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

a11y - edit page - block identification - cms ui #5211

Open
Wagner3UB opened this issue Sep 21, 2023 · 0 comments
Open

a11y - edit page - block identification - cms ui #5211

Wagner3UB opened this issue Sep 21, 2023 · 0 comments
Assignees
Labels

Comments

@Wagner3UB
Copy link
Contributor

Describe the bug
The blocks are created without proper identification. When read by a screen reader, they describe the content and the type of the input, but do not identify which block they belong to. This compromises navigation, as users move from input to input without being able to determine if they are within or outside the same block.

To Reproduce
Steps to reproduce the behavior:

1- Go to https://demo.plone.org/edit
2- enter in edit mode by clicking on the edit button (top-left)
3- Press enter with a screen reader on to access a new text block.

Expected behavior
When entering a block, it should be identified and contain a minimum of necessary information to assist the user. This identification should correspond to the type of block found within the 'add block' tab. For example, a text block should be labeled with something like 'Editable Text Block: Type text...'. In another example, when accessing the Teaser block, it reads the content within the block as 'Please choose an existing content as the source for this element,' but no further information is provided on how the user should proceed after accessing the block.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: To do
Development

No branches or pull requests

2 participants