mirror of
https://github.com/django/django.git
synced 2025-06-05 11:39:13 +00:00
Add curb cut effect and accessibility team
This commit is contained in:
parent
0e955d76dc
commit
52660c107d
@ -2,8 +2,11 @@
|
|||||||
Accessibility
|
Accessibility
|
||||||
=============
|
=============
|
||||||
|
|
||||||
The Django project is committed to being accessible to everyone in all possible ways.
|
The Django project is committed to being accessible to everyone
|
||||||
We work to conform to established accessibility standards, and also to meet our own targets for supporting specific input devices and assistive technologies.
|
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:
|
.. _accessibility-standards:
|
||||||
|
|
||||||
@ -37,16 +40,24 @@ Accessibility support targets
|
|||||||
=============================
|
=============================
|
||||||
|
|
||||||
Beyond standards, we want to make sure Django actually works for people using
|
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
|
The best way to do this effectively is to take accessibility considerations
|
||||||
into account as part of designing features. If in doubt, consult
|
into account as part of designing features. If in doubt, consult
|
||||||
with users who rely on assistive technologies or with accessibility experts.
|
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:
|
||||||
|
|
||||||
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:
|
Always test user interface changes with:
|
||||||
|
|
||||||
* Keyboard-only navigation
|
* Keyboard-only navigation
|
||||||
@ -59,10 +70,6 @@ Where appropriate, also test with:
|
|||||||
* 400% browser zoom
|
* 400% browser zoom
|
||||||
* Forced-colors mode (for example Windows Contrast Themes)
|
* 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:
|
||||||
|
|
||||||
Assistive technologies
|
Assistive technologies
|
||||||
|
Loading…
x
Reference in New Issue
Block a user