#35863: Advice for new contributors documentation should be structured with
headings - Accessibility
-------------------------------------+-------------------------------------
Reporter: Sarah Sanger | Owner: Sarah
Type: | Sanger
Cleanup/optimization | Status: assigned
Component: Documentation | Version: 5.1
Severity: Normal | Resolution:
Keywords: Accessibility | Triage Stage: Accepted
Documentation Contributing |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Thibaud Colas):
* cc: Thibaud Colas (added)
* owner: (none) => Sarah Sanger
* stage: Unreviewed => Accepted
* ui_ux: 1 => 0
Comment:
Thank you for the report Sarah! The current pattern is a pretty clear
failure of [https://www.w3.org/WAI/WCAG22/Understanding/info-and-
relationships.html WCAG SC 1.3.1 Info and Relationships]:
> Information, structure, and relationships conveyed through presentation
can be programmatically determined or are available in text.
For reference, we also did a similar change in
[https://github.com/django/django/pull/17549 PR #17549]. Note for the page
you mention there seems to be two lists with this issue; under First steps
and Guidelines.
--
Ticket URL: <https://code.djangoproject.com/ticket/35863#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070192c0ddef89-4e29bb7a-1ac6-4c7e-ad10-a99376e23a10-000000%40eu-central-1.amazonses.com.
