#35855: Add a disclaimer about PDF accessibility issues in docs
-------------------------------------+-------------------------------------
Reporter: Thibaud Colas | Owner: (none)
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: dev
Severity: Normal | Resolution: wontfix
Keywords: accessibility, | Triage Stage:
djangonaut space, pdf | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Claude Paroz):
Replying to [comment:4 Thibaud Colas]:
> @Claude we want Django sites to be accessible.That means the framework,
including docs, certainly should encourage good practices for
accessibility. As is the case for security, performance, etc. A warning
seems commensurate with the size of the footgun.
To be clear, I'm all for accessibility as far as Django itself is
concerned. But for me, the choice of a PDF output is not something we
should interfere with. We have to put limits in what we document, and for
me, this is out of scope (but legitimate by itself, of course).
And yes, I also find ReportLab limitations saddening, but this is related
to the business model of the company behind it. It's not a community-
driven project.
--
Ticket URL: <https://code.djangoproject.com/ticket/35855#comment:6>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/01070192b953c160-931435e7-2864-47a2-bb7a-621421cff3a1-000000%40eu-central-1.amazonses.com.
