Changes between Initial Version and Version 1 of Ticket #36511


Ignore:
Timestamp:
Jul 19, 2025, 6:41:13 AM (4 months ago)
Author:
Thibaud Colas
Comment:

Thank you @laurenherregodts, makes sense based on our testing.

Sample page: ​django static demo releases changelist. On this page, here are the numbers of tab stops as-is, with 4 items in the changelist, each with three fields

  • Worst case: 78
  • Skipping the sidebar: 43
  • Using "skip to main content": 41

The target would be for the number of tab stops to be the same regardless of the content of the table. Ideally:

  • 3 or 5 tab stops. Placing the filters after the "Add" button in object-tools, or after the search bar
  • Or worst case after the toplinks (number of tab stops dependent on number of top links)

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #36511

    • Property Triage Stage Unreviewed → Accepted
    • Property Summary Optimize accessibility of filters in django admin console → Optimize accessibility of filters in django admin

  • Ticket #36511 – Description

    initial v1  
    1 I'm not seeing any previously logged tickets for this, so adding a new ticket to report.
    2 When using tabs to navigate a page in the django admin console, the filter panel is only accessed as last part of the page. This means users will have to tab through entire tables. The issue was identified using AXE tab stops during accessibility testing.
     1When using keyboard tabs to navigate a page in the django admin interface, the filter panel is only accessed as last part of the page. This means users will have to tab through entire tables. The issue was identified using [https://accessibilityinsights.io/docs/web/getstarted/fastpass/#complete-the-assisted-test-for-tab-stops AXE tab stops] during accessibility testing.
     2
    33I believe there are no changes to the styles needed, just move the template so the DOM order is more correct and filter panel is accessed earlier.
Back to Top