Editor should have unique label

[Teresa Monahan]

At present the aria-labelledby element of the editor contains the value "Rich Text Editor". This means that if 2 editors are on the same page, there is no way for JAWS users to differentiate between the application landmarks for the editors. The aria-labelledby element should instead contain a unique value for each editor.

One simple way to address this is to include the editor name in the value e.g. "Rich Text Editor, editor1", "Rich Text Editor, editor2" etc. This can be achieved by replacing:

voiceLabel: editor.lang.editor,

with:

voiceLabel: [ editor.lang.editor, editor.name ].join( ',' ),

on line 327 of core/creators/themedui/js.

This is an accessibility requirement for us so is a high priority. Can this please be included in the upcoming 4.1.2 release?

[Jakub Ś]

I believe this is a duplicate of #10042.

AFAIK JAWS reads something like Rich Text Editor, editor one.

@tmonahan I'm closing this as duplicate. If you think otherwise please leave a comment.

[Teresa Monahan]

Replying to j.swiderski:

I believe this is a duplicate of #10042.

AFAIK JAWS reads something like Rich Text Editor, editor one.

@tmonahan I'm closing this as duplicate. If you think otherwise please leave a comment.

Hi, thanks for the link to ticket #10042 - that is interesting and will definitely be useful for us. Unfortunately this ticket requires a little more. The issue described here does not relate to what JAWS reads out when users tab to the editor. Instead it is about how users can identify landmarks on a page. There is a shortcut in JAWS which lists all available landmarks - Ctrl + Insert + ;

Currently all editors on the page are listed as "Rich Text Editor Application" because the element with role=application has "Rich Text Editor" as its associated label. We need editors to be distinguishable on this list. Changing the voiceLabel in themedui.js to use the new editor.title value should be enough to achieve this:

voiceLabel: editor.title,

[Jakub Ś]

Thanks for clarification. I will forward this ticket.

[Olek Nowodziński]

Since the problem only refers to a11y and the solution seems non-intrusive, it's possible to have it in 4.1.2.

[Teresa Monahan]

Replying to a.nowodzinski:

Since the problem only refers to a11y and the solution seems non-intrusive, it's possible to have it in 4.1.2.

Great, thanks!

[Olek Nowodziński]

Pushed the fix to ​t/10510 branch.

[Olek Nowodziński]

Merged fix into master, dev (​​git:a9dc6c374653eb).