mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2024-12-23 01:25:58 +00:00
Code Issues 25 Releases Wiki Activity

Add guidelines for accessibility in documentation

Browse Source
This commit is contained in:
Thibaud Colas 2023-10-05 07:21:21 +01:00
parent af737c05d2
commit 1844e5b74b
1 changed files with 39 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

39
docs/internals/contributing/writing-documentation.txt
View File

@ -197,6 +197,10 @@ point to the latest or stable version of the documentation, e.g. ``/en/stable/``
Writing style Writing style
============= =============
Prefer plain language where possible. Avoid jargon and technical terms unless
they are necessary. Keep sentences short and to the point. Use the active voice
where possible.
When using pronouns in reference to a hypothetical person, such as "a user with When using pronouns in reference to a hypothetical person, such as "a user with
a session cookie", gender-neutral pronouns (they/their/them) should be used. a session cookie", gender-neutral pronouns (they/their/them) should be used.
Instead of: Instead of:
@ -609,6 +613,41 @@ you'd like to help translate the documentation into another language.
.. _django-admin-manpage: .. _django-admin-manpage:
Accessibility in documentation
==============================
See :doc:`/internals/contributing/writing-code/accessibility` for our project guidelines. For documentation
specifically, guide readers to use accessible patterns.
* Include enough code so examples are accessible by default. For example:
* :class:`django.forms.ImageField` usage should
acknowledge the need for alt text.
* :class:`django.forms.URLField` to create an HTML link should
provision for link text.
* ``<html>`` elements must have a ``lang`` attribute.
* ``<img>`` elements must have an ``alt`` attribute, set with an appropriate
description or left empty for decorative images.
* When there are multiple ways to achieve a result, make sure the accessible
option is the most prominent. For example:
* Forms should showcase use of :meth:`.Form.as_div` over alternatives.
* :class:`django.core.paginator.Paginator` examples should
demonstrate pagination links before “Load more” patterns.
* Document common accessibility considerations. For example:
* When creating or storing documents such as :doc:`/howto/outputting-pdf`,
mention the need for accessible alternatives.
* For operations with timeouts, mention `relevant accessibility guidelines <https://www.w3.org/WAI/WCAG22/Understanding/timeouts.html>`_.
* Use appropriate semantic HTML elements and attributes. For example:
* Use headings instead of bold text.
* Add landmark elements where needed.
* Only use ARIA attributes if there are no alternatives.
``django-admin`` man page ``django-admin`` man page
========================= =========================