#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
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):

 * resolution:   => wontfix
 * status:  new => closed

Comment:

 > I’m baffled to read their tagged PDF support is ​only available for paid
 users, not sure what to make of that information. Without tags, 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.

 I agree this is concerning, perhaps we should recommend
 [https://doc.courtbouillon.org/weasyprint/stable/ WeasyPrint]. This looks
 like you format it in html and you opt to convert it to a pdf (with tags)

 It looks like this How-to guide was added in 2005 - do we think this guide
 needed at all? It uses a [https://docs.djangoproject.com/en/5.1/ref
 /request-response/#fileresponse-objects FileResponse] maybe these docs are
 already enough?
 Perhaps this how-to, which relies on an external package (possibly
 commercialized in the past 20 years), doesn't belong in the docs.

 These are the options I see:
 1. Remove this How-to
 2. Move away from ReportLab
 3. Add a warning to the docs
 4. Do nothing

 To decide a route forward, can you start a discussion on the
 [https://forum.djangoproject.com/c/internals/5 forum] and get more input
 from other folks? If there's a consensus for any of the options 1-3 please
 come back here, link the discussion and reopen the ticket
-- 
Ticket URL: <https://code.djangoproject.com/ticket/35855#comment:5>
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/01070192b8713103-dd163ece-6c75-440d-b503-081d009fddb6-000000%40eu-central-1.amazonses.com.

Reply via email to