2.2.x roadmap and discussion

It's working!

A couple of ideas for the road map that I received as feedback from a client.

1. At the moment when you start going through the found issues on the page, you can see the total number of issues found on the page but once you start going through the list you cannot anymore track your progress. Would be really nice to see how you progress the page for example just showing a pagination that at the moment you are on issue 5/10 found from the page.
2. At the moment it seems like you are able to navigate to the next issue but there is no way to navigate to the previous issue. Would be nice if there were both previous and next links. You can for example by accident click on the next button twice and then there is no easy way get back to the previous issue.

Thanks heikkiy.

From rkoller in Slack:

[...]on large screen monitors the editoria11y widget in the bottom right corner of the screen is located quite far away from its context (the wysiwyg field ) you as the user are working in. so you have to jump visually between the wysiwyg field (if you want to check the remaining number of errors for example) and the widget [...] i wonder if it would be possible in case of the wysiwyg integration to add some sort of status bar at the bottom of the ckeditor field containing the functionality and information of the widget.
That would also benefit in regards of the position in the DOM. at the moment the elements contained in the widget are at the end of the DOM move to some sort of “(status) bar” underneath the ckeditor textarea, these elements would also be right next in the for example rotor list in voiceover?

[...] you can have the case that a content type has more than one long formatted text with summary. but editoria11y is still displaying the overall number of errors for all available ckeditor fields on the node edit form. i am not sure if it would be desirable to distinguish between ckeditor fields in that summary or not, or if it should be configurable, or if there should be an option to have separate status bars as suggested in the previous point for the different ckeditor fields.

[...] if you expand the widget and you have a low number of errors the widget turns yellow. the collapsed circle has a blackish outline within therefor it is easier to spot but that expanded state is yellow only. against white background the color contrast for yellow is only 1.4:1.

[...] i was testing the new recipe for the [StarShot] privacy track with the latest version of drupal cms. [...] the module shipping with the privacy module has also a widget that is shown in the bottom right corner of the screen. on wide viewports editoria11y is hiding the button

Summary of tasks resulting from feedback so far

1. Continue work adding next/previous buttons to tips to reduce eye travel, and restore missing transfer-keyboard-focus button.
2. Add manual and offset parameters with automatic detection of Starshot module widgets.
3. Considering integrating main toggle into CKEditor toolbar instead of showing it at all on admin pages, or somehow pin to each editor instance.
4. Consider appending tips right after the contentEditable region rather than at the end of the body, to ease keyboard access. (note that I might punt on this until after Gutenberg integrations are done; some functions assume tips are still present, and other scripts modifying the wrapper might break that)

Revised tip for beta 2 incorporating @heikkiy suggestions:

Tagged 2.2.x Beta 3 → . Unless new bugs show up, I think this is ready for release.

New bugs always show up.