#34832: Use `banner` landmark or `<header>` element for the admin header area
-------------------------------------+-------------------------------------
     Reporter:  Thibaud Colas        |                    Owner:  Sarah
         Type:                       |  Abderemane
  Cleanup/optimization               |                   Status:  closed
    Component:  contrib.admin        |                  Version:  4.2
     Severity:  Normal               |               Resolution:  fixed
     Keywords:  accessibility,       |             Triage Stage:  Ready for
  screen reader, landmarks           |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  1                    |                    UI/UX:  1
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"814e7bc22062eeae4be9f189e89027e28d5dd290" 814e7bc]:
 {{{
 #!CommitTicketReference repository=""
 revision="814e7bc22062eeae4be9f189e89027e28d5dd290"
 Fixed #34832 -- Made admin's header content render in <header> tag.

 Header tag was changed to <header> get the landmark banner for
 accessibility.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/34832#comment:10>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018a970c218c-82a3f574-0097-49ac-998e-dd3d30d1a03b-000000%40eu-central-1.amazonses.com.

Reply via email to