Django’s accessibility track record

Oct 18 4:00 PM EDT :calendar: to 4:45 pm

About This Talk

There are great accessibility guidelines out there. Great tools to evaluate individual websites too. Between the big picture and individual projects, we can look at what Django specifically does – and what changes at the level of the framework could improve large swaths of the Django web.

We will start by looking at the HTTP Archive’s dataset of 8M websites, 30’000 of which are built with Django. We can identify which issues are common compared to other frameworks, and review specific issues in more depth to understand where they might appear in Django.

We can then look into the implementation details to understand exactly how users of assistive technology would benefit or be harmed by Django’s design choices. And accordingly highlight the correct approach.

A practical example of this where we can go very deep is Django’s implementation of HTML forms. Django’s default markup previously left a lot to be desired, and it being “the default” led to a lot of websites shipping with accessibility issues. This has been improved from release to release, addressing basic issues and introducing more advanced patterns like ARIA attributes for errors.


    Thibaud Colas

    Thibaud is a developer interested in all things accessibility and sustainability. I’m a core contributor to the Wagtail open source CMS, and part of Django’s accessibility team.