The Django project is committed to ensuring that websites built with Django are\nusable by everyone, including people with disabilities. Django’s built-in\ncomponents, such as the admin interface and default form rendering, should\nadhere to established accessibility standards and meet our own targets for\nsupporting specific input devices and assistive technologies.
\nWe work to conform with the Web Content Accessibility Guidelines (WCAG),\nversion 2.2, at the AA level. WCAG is the most established standard for web\naccessibility. AA-level guidelines are the most common legal compliance\ntarget worldwide.
\nWe also aim to follow other best practices, such as:
\nWCAG 2.2 AAA-level guidelines – stricter criteria that go beyond the AA\nlevel.
The upcoming WCAG 3.0 guidelines – a new, evolving standard that aims to\nunify and improve upon previous versions of WCAG.
Authoring Tool Accessibility Guidelines (ATAG) 2.0 – guidelines for\nsoftware and services that are used to produce web content.
To learn more about accessibility without diving straight into standards, we\nrecommend The A11Y Project, a community-driven effort to make digital\naccessibility easier.
\nBeyond standards, we want to make sure Django actually works for people using a\nwide range of input devices and assistive technologies. This has benefits to\nmake sure Django works better for everyone. The best way to do this\neffectively is to take accessibility considerations into account as part of\ndesigning features. If in doubt, consult with users who rely on assistive\ntechnologies or with accessibility experts. You can reach out to the\nAccessibility team via the Accessibility Django forum topic or via the\n#accessibility channel on the Django Discord server.
Design the UI with accessibility in mind, and the testing will only be needed\nas a final check. For more complex interfaces, confer with other contributors\nto decide on testing targets. Reach out to the Accessibility team for\nsupport and to coordinate testing.
\nAlways test user interface changes with:
\nKeyboard-only navigation. Common issues include:
\nAn interactive element can’t be reached using the Tab or arrow keys.
An interactive element « traps » input focus and prevents navigating away.
An interactive element doesn’t give a visible indication when it has input\nfocus.
The focus order is inconsistent with the logical order that’s communicated\nvisually.
The Accessibility Insights browser extension’s automated checks feature,\nor an equivalent tool with the Axe checker.
Where the UI changes could affect those modalities, also test with:
\nTouch-only navigation. Common issues include:
\nA touch target (interactive element) is too small.
Hover-based based interaction which does not translate to touch, such as a\nhover only tooltip.
400% browser zoom. Common issues include:
\nContent is cut off or disappears when zoomed.
Content that does not inherently require a two-dimensional layout causes\nscrolling in both directions (vertical and horizontal). Two-dimensional\nscrolling is acceptable for content like images, maps, videos, and data\ntables, which require both dimensions to be usable.
Forced-colors mode (for example Windows Contrast Themes). Note that this can\nbe tested via the "high_contrast" mode in the screenshot tests. Common issues include:
Over-reliance on color for meaning, which is lost in forced-colors mode.
Use of !important or inline styles may break forced-colors mode.
Where the UI changes could affect assistive technologies, here are popular free\noptions we recommend testing with.
\nFor Windows:
\nNVDA - recommended with Firefox ESR
Narrator - recommended with Microsoft Edge
Windows Magnifier
Windows Speech Recognition
For macOS:
\nVoiceOver - recommended with Safari
macOS Zoom
macOS Voice Control
For Linux:
\nOrca - recommended with Firefox ESR
For mobile or tablet:
\nVoiceOver on iOS, or TalkBack on Android
The following are popular licensed options. If you are a user of these, or can\nwork with a user holding a license, also test against:
\n\nThere are parts of Django that do not meet our accessibility targets. We\nactively work on fixing issues, both as part of ongoing maintenance and bigger\noverhauls. To learn about known issues, and get involved, see:
\n#accessibility sur le serveur Discord de Django.
Les tickets Accessibility sur le système de suivi des tickets.
Notre comité de projet améliorations de l’accessibilité de Django.