#35855: Add a disclaimer about PDF accessibility issues in docs
-------------------------------------+-------------------------------------
     Reporter:  Thibaud Colas        |                    Owner:  (none)
         Type:                       |                   Status:  new
  Cleanup/optimization               |
    Component:  Documentation        |                  Version:  dev
     Severity:  Normal               |               Resolution:
     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 Thibaud Colas):

 I didn’t know about that page in the ReportLab docs! I’m baffled to read
 their tagged PDF support is [https://docs.reportlab.com/pdf-
 accessibility/#availability only available for paid users], not sure what
 to make of that information. There’s no way a PDF with any kind of
 formatting in it would be considered good enough for an organization that
 has to follow accessibility standards.

 @Natalia PDFs have accessibility issues like any other content, but
 they’re even more prevalent because a lot of software out there requires
 extra steps to produce accessible PDFs. The page shared by Sarah is a good
 overview of things that are often missing and can be resolved (in
 particular tagging). Additionally I would recommend reading:

 - [https://en.wikipedia.org/wiki/PDF/UA PDF/UA], the standard for PDF
 files’ accessibility. The first requirement "Complete tagging" is what’s
 only available in the paid version of ReportLab (…).
 - [https://gds.blog.gov.uk/2018/07/16/why-gov-uk-content-should-be-
 published-in-html-and-not-pdf/ Why GOV.UK content should be published in
 HTML and not PDF]. This is a good authoritative overview of fundamental
 accessibility issues with the format (such as lack of responsive resizing
 and reflow, lack of text resizing, and color theming).

 @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.
-- 
Ticket URL: <https://code.djangoproject.com/ticket/35855#comment:4>
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/01070192b6540289-376d02bf-f21e-4f23-bdc6-652387aeefe8-000000%40eu-central-1.amazonses.com.

Reply via email to