#33728: Tab order should match visual order for admin model forms’ submit
buttons
-------------------------------------+-------------------------------------
Reporter: Thibaud Colas | Owner: nobody
Type: Bug | Status: new
Component: contrib.admin | Version: dev
Severity: Normal | Resolution:
Keywords: accessibility, | Triage Stage:
keyboard, ux | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------
Description changed by Thibaud Colas:
Old description:
> In the Django admin, in a model form, the tab order of the submit buttons
> is different from the visual order. Here is a screenshot of the tab
> stops:
>
> In LTR languages, focus should follow the reading order of the page, top-
> to-bottom, left to right. Here, the correct focus order for those buttons
> would be:
>
> 1. Save and add another
> 2. Save and continue editing
> 3. SAVE (not sure why this one is shouting)
>
> We need to change the order of the buttons in the DOM so it matches the
> visual order. Or if we do want the default button to be reached first,
> then remove the styling that changes the visual order currently. I assume
> this implementation was done intentionally, but it’s confusing for
> keyboard users if focus moves counter to the expected sequential flow of
> the elements.
New description:
In the Django admin, in a model form, the tab order of the submit buttons
is different from the visual order. Here is a screenshot of the tab stops:
[[Image(https://code.djangoproject.com/raw-attachment/ticket/33728/tab-
stop-modelform.png)]]
In LTR languages, focus should follow the reading order of the page, top-
to-bottom, left to right. Here, the correct focus order for those buttons
would be:
1. Save and add another
2. Save and continue editing
3. SAVE (not sure why this one is shouting)
We need to change the order of the buttons in the DOM so it matches the
visual order. Or if we do want the default button to be reached first,
then remove the styling that changes the visual order currently. I assume
this implementation was done intentionally, but it’s confusing for
keyboard users if focus moves counter to the expected sequential flow of
the elements.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/33728#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070180de90d41d-9a4f9c0a-c80a-4cd9-9210-2c32ea4d12a1-000000%40eu-central-1.amazonses.com.
