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.

Sign up for GitHub

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

Jump to bottom

Special Character dialog has empty elements which confuses screen readers #3544

Closed
f1ames opened this issue Oct 7, 2019 · 1 comment
Closed

Special Character dialog has empty elements which confuses screen readers #3544

f1ames opened this issue Oct 7, 2019 · 1 comment
Assignees
@msamsel
Labels
plugin:specialchar The plugin which probably causes the issue. status:confirmed An issue confirmed by the development team. support:2 An issue reported by a commercially licensed client. target:minor Any docs related issue that can be merged into a master or major branch. type:bug A bug.
Milestone
4.13.1

Comments

@f1ames
Copy link
Contributor

f1ames commented Oct 7, 2019

Type of report

Bug

Provide detailed reproduction steps (if any)

Screen reader should be used during below steps, however the issue is also visible without it.

  1. Go to https://ckeditor.com/docs/ckeditor4/latest/examples/fullpreset.html.
  2. Open "Select Special Character" dialog.
  3. Navigate the screen using Caps + Arrows (screen reader virtual cursor traversing accessibility tree).

image

Expected result

​
Screen reader should navigate to the disabled text. Or empty td should not be there to not confuse screen readers.

Actual result

Unable to navigate to next item using Caps + Arrows after the end of visible special character. On screen next item is disabled text on which the screen reader focus is not moving.

Other details

The possible solution is to add role="presentation" attribute to empty td elements or just remove them.

  • Browser: Checked on Chrome.
  • OS: 4.5+
  • CKEditor version: full preset
  • Installed CKEditor plugins: special character
@f1ames f1ames added type:bug A bug. status:confirmed An issue confirmed by the development team. plugin:specialchar The plugin which probably causes the issue. target:minor Any docs related issue that can be merged into a master or major branch. support:2 An issue reported by a commercially licensed client. labels Oct 7, 2019
@f1ames f1ames added this to the 4.13.1 milestone Oct 7, 2019
@msamsel msamsel self-assigned this Oct 10, 2019
@msamsel msamsel mentioned this issue Oct 10, 2019
Merged
2 tasks
@Comandeer
Copy link
Member

Fix was merged into master and will be released in 4.13.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@msamsel msamsel

Labels
plugin:specialchar The plugin which probably causes the issue. status:confirmed An issue confirmed by the development team. support:2 An issue reported by a commercially licensed client. target:minor Any docs related issue that can be merged into a master or major branch. type:bug A bug.
Projects
None yet
Milestone
4.13.1
Development

No branches or pull requests
3 participants
@f1ames @Comandeer @msamsel