Django Accessibility for Everyone
summary
HTTP Archive and Lighthouse show six issues (color contrast, link text, labels, headings, alt text, document language) account for 96.1% of errors on top sites, and fixing them (proper headings, for=id labels, visible link text, concise alt, lang attribute) removes the vast majority of failures. A public rebuild for RNIB uses Django and Wagtail, adds Wagtail accessibility Checker in the CMS, and pairs early in-browser testing with low-vision and screen‑reader users; dark mode is added and usage is being monitored to decide defaults.
AI-written summary · about
chapters (12)
- 0:00Introduction to accessibility
- 1:16The impact of inaccessibility
- 2:24Understanding barriers
- 3:48Auditing common issues
- 5:12Prioritizing fixes
- 7:14Color and design standards
- 8:59Semantic HTML and headings
- 11:51Improving interactive elements
- 14:12Links and descriptive labeling
- 16:56Form labels and image alt text
- 20:01Real-world case study: RNIB
- 24:28Usability and final thoughts
related talks
42mDjango’s accessibility track record
23mAn Intro to Web Accessibility in Django
48mAccessibility awareness
23mWeb Accessibility In Django
41mBest Practices for Making a Wagtail Site as Accessible as Possible
02h 54mHow To Build More Accessible Websites with Wagtail
21mPrevent, Catch and Fix Accessibility Issues
25mReal Life Accessibility: Have you HEARD your site?