mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-03-31 11:37:06 +00:00
Code Issues 32 Releases Wiki Activity

Add curb cut effect and accessibility team

Browse Source
This commit is contained in:
Thibaud Colas 2023-11-16 22:56:55 +00:00
parent 0e955d76dc
commit 52660c107d
1 changed files with 14 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
docs/internals/contributing/writing-code/accessibility.txt
View File

@ -2,8 +2,11 @@
Accessibility
=============
The Django project is committed to being accessible to everyone in all possible ways.
We work to conform to established accessibility standards, and also to meet our own targets for supporting specific input devices and assistive technologies.
The Django project is committed to being accessible to everyone
in all possible ways.
We work to conform to established accessibility standards,
and also to meet our own targets for supporting specific input devices
and assistive technologies.
.. _accessibility-standards:
@ -37,16 +40,24 @@ Accessibility support targets
=============================
Beyond standards, we want to make sure Django actually works for people using
a wide range of input devices and assistive technologies.
a wide range of input devices and assistive technologies. This has benefits
to make sure Django works better `for everyone`_.
The best way to do this effectively is to take accessibility considerations
into account as part of designing features. If in doubt, consult
with users who rely on assistive technologies or with accessibility experts.
.. _for everyone: https://en.wikipedia.org/wiki/Curb_cut_effect
.. _accessibility-testing-baseline:
Accessibility testing baseline
------------------------------
Design the UI with accessibility in mind,
and the testing will only be needed as a final check. For more complex
interfaces, confer with other contributors to decide on testing targets.
Reach out to the `Accessibility team`_ for support and to coordinate testing
Always test user interface changes with:
* Keyboard-only navigation
@ -59,10 +70,6 @@ Where appropriate, also test with:
* 400% browser zoom
* Forced-colors mode (for example Windows Contrast Themes)
Design the UI with accessibility in mind,
and the testing will only be needed as a final check. For more complex
interfaces, confer with other contributors to decide on testing targets.
.. _assistive-technologies:
Assistive technologies