Contrib.social

The different stages of the add and install process aren't announced in screenreaders for the Svelt UI for install controllers

Open on Drupal.org →
Created on 2 November 2022, almost 2 years ago
Updated 11 May 2024, 4 months ago

Problem/Motivation

i've tried to add a module with voiceover activated on macos monterey. currently there is nothing announced what is currently happening during the add process of a module - there different stages the add and install goes through are inaccessible to the screenreader user. in the current example (see voiceover.mp4) when the process takes too long with no user input voiceover starts to announce again and stated "you are currently in a group. to exit this group,...". that could be confusing for the screenreader users as well.
at the end of the process it sounds a bit distracting/confusing to get a "view password" web dialogue with two items and then a "download of view password complete".

*i've recorded the video with a previous version of the patch. functionally in regards of screenreader output it is still the same but the time an add and install took differs significantly. to illustrate the case if the insall process takes too long without any user input and the screenreader starts talking again is illustrated in that older example much better.

Steps to reproduce

Proposed resolution

  • it might be helpful to announce the different states changes of the add and install process with drupal.announce().
  • at the end when the process is successfully finished i wonder if it wouldnt be enough to simply announce module x was successfully installed instead have have the user close a modal with no additional value. it is just an unnecessary extra click. that applies to sighted users as well. the modal has not real extra value. that the module was successfully added and or installed is already communicated via the button label

Remaining tasks

  • ✅ File an issue about this project
  • ☐ Manual Testing
  • ☐ Code Review
  • ☐ Accessibility Review
  • ☐ Automated tests needed/written?
✨ Feature request
Status

Active

Version

1.0

Component

User experience

Created by

🇩🇪Germany rkoller Nürnberg, Germany

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Comment over 1 year ago →
    🇺🇸United States chrisfromredfin Portland, Maine

    If someone comes to this issue it would be nice to re-check the current status using VoiceOver or Jaws, etc. and validate comments in #4 and/or propose a solution.

  • Comment 11 months ago →
    🇺🇸United States chrisfromredfin Portland, Maine
  • Comment 4 months ago →
    🇩🇪Germany rkoller Nürnberg, Germany

    I've recorded the current state, see install_vo.mp4 . The current output in the visual and the aural interface compared:

    Revisiting this issue after a while and seeing everything with fresh eyes I wonder if the following changes would make sense:

    On the inline label end. It might make sense to consider changing the first label from Installing to Adding. The actual Install part happens in the second part, the first part is all about adding and it would be in line with the button label and the terminology in core in general. And some of the labels start in lowercase but all the labels should start uppercase consistently.

    The aural interface was way too verbose and redundant. the "Adding module Webform," snippet was frontloaded way too many times. In my suggestion I've only made the initial announcement more verbose than the interface text by adding the module name so you get "Adding Webform module". That way the context is set for screenreader users. an reassurance that the correct module is being added and installed. The rest of the announcements is in line with the interface text. only in cases like requring the module an "in progress" is being added at the end if an announcement comes a second or third time. In the last step there was no announcement at all that the module got installed. This might be a good place to announce the module name again. for example Successfully installed Webform module . the event of a successful install is being frontloaded. that way someone remembering the context of which module is being installed gets the direct feedback that the install successfully ran through and can jump off while others with a small working memory still get reminded to the overall context of which module was just installed.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024