- Status changed to Active
10 months ago 4:03pm 22 February 2024
At the moment the onboarding for screen reader users, aside the general a11y related issues upstream, to communicate the basic concepts of ECA and BPMN, is sort of challenging - it is simply difficult near to impossible to orient and grasp the general basic structure without any visual queues. An aspect that is even potentially an issue for some sighted users.
It might be beneficial to add tours for the Tour module in Core. I've already created four working tours with a differing number of tips in a local install. i would suggest these four tours. I've only added the basic outline of tips for each tour without any descriptions added yet. wanted to get a consensus first if the addition of the feature would make sense and if the outline makes sense:
ECA main tour (route: entity.eca.collection):
=> ideally it would be good to add a tip to several or even each of the columns available but i am not sure with which selector that could be accomplished. so far i lean towards having a single tip for #edit-eca-entities thead
=> I wouldn't create a dedicated tour for the import and log pages.
ECA Settings tour (route:eca.settings):
=> not sure yet if tip 5-8 is necessary and tip 4 might be already enough
ECA parameters tour (route: entity.eca.parameters):
ECA model tour (route: entity.eca.edit_form):
=> there are two problems first i dont know if and how to expand a section in the properties panel. if i target a selector of a field inside a collapsed section the tip isn't expanding the section nor it is shown. the other problem it is probably also impossible to provide tips for elements of a model? if one is creating a new model and hits the tour button right after only the toolbar and properties panel would be covered the canvas would be empty without any components on it yet. would it make sense to ship eca with one demo model out of the box? then it might be possible to target specific elements for that model - because the model name as well as the elements of that model are known and the tour wouldn't be shown for each and every model?
=> adding a tip for the element template chooser is also tricky to accomplish first the button to open the template chooser is hidden in a collapsed section and second to reach the chooser it is also necessary to click the aforementioned inaccessible button.
Active
2.0
User interface
Makes Drupal easier to use. Preferred over UX, D7UX, etc.
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
