The migration execution form was added at #2470882: Implement running migration processes through the UI, but have some accessibility and usability flaws:

  • the submit (execute) button is located before the operations description and the options, making hard to SR (screen reader) users reach the rest of the form
  • operation descriptions are separated from the operation field, forcing users to 'jump' between the selector and the definitions area
  • the migration label is not present in the title or somewhere else, so there is no clue (except the URL) about what migration we are operating on

There are also some other things that can be improved:

  • the global "operations" fieldset seems to be superfluous
  • the "Limit to" field can be a number field
  • the operation field is required and have an initial default value, so there is no need for explicit validation for empty
  • there is a call to "\Drupal::routeMatch()" that should be converted to "$this->getRouteMatch()" (FormBase method)
CommentFileSizeAuthor
#3 migrate_tools-execution_form_accessibility_usability-3064965-after.png52.33 KBmanuel.adan
#3 migrate_tools-execution_form_accessibility_usability-3064965-before.png49.1 KBmanuel.adan
#3 migrate_tools-execution_form_accessibility_usability-3064965-2.patch7.31 KBmanuel.adan

Comments

manuel.adan created an issue. See original summary.

manuel.adan’s picture

manuel.adan
Location 🌌
commented
Issue summary: View changes
manuel.adan’s picture

manuel.adan
Location 🌌
commented
Status: Active » Needs review
StatusFileSize
new migrate_tools-execution_form_accessibility_usability-3064965-2.patch7.31 KB
new migrate_tools-execution_form_accessibility_usability-3064965-before.png49.1 KB
new migrate_tools-execution_form_accessibility_usability-3064965-after.png52.33 KB

Current form:

execute migration form screenshot, current

After the patch:

execute migration form screenshot, after patch n. 2

manuel.adan’s picture

manuel.adan
Location 🌌
commented
Title: Make the migrate execution form accessible and usable » Make the migrate execution form accessible and more usable
Assigned: manuel.adan » Unassigned
mgifford’s picture

mgifford
he/him
Primary language English
commented

I haven't tested this out, but really like the work that's been done here to make this admin tool accessible. Great to have this additional information added to Migrate!

  • heddn committed a1c2322 on 8.x-4.x authored by manuel.adan 
    Issue #3064965 by manuel.adan, heddn: Make the migrate execution form...
heddn’s picture

heddn
Primary language English
Location Illinois
commented
Status: Needs review » Fixed

I like it. A lot. I made a couple small changes. Mainly to make the details toggled closed since they are optional and not used all the time.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

andrewmacpherson’s picture

andrewmacpherson commented

the submit (execute) button is located before the operations description and the options, making hard to SR (screen reader) users reach the rest of the form

This can indeed be an issue, but the explanation is slightly off. It's not hard to reach the rest of the form, if you want to. You just keep going.

The issue is that screen reader users often assume that the when you get to the submit button, that's the end of the form. There's no incentive to continue exploring, so they don't read the rest.

The issue is described towards the end of this Drupalcon session (starting around 24 minutes): Mobile accessibility: the good, the bad and the ugly. (It's not limited to the mobile experience.)