Translate Ideas and Comments
Choose language:
There was an error during translation

David Swisher

My feedback

  1. 18 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    David Swisher commented  · 

    I agree that this is an essential need. While InDesign is the natural solution for page layouts and Illustrator is often seen as just a tool for creating drawings that get placed within InDesign (and thus wouldn't need accessibility), the reality is that LOTS of illustrations ranging from infographics to maps to charts to explanatory graphics are best designed in Illustrator natively and NOT in InDesign.

    In both higher education and government, making all documents accessible is a mandate. It's also fundamental to UDL and a general expectation most places, whether or not it's a requirement.

    It requires quite a bit of post-production editing to tag PDFs with accessibility features that Illustrator ought to be able to handle natively. Further, for many projects (especially those mentioned above), it makes zero sense to build a page structure in InDesign just to enable accessibility when 95% or more of the illustration is done in Illustrator. Doing so is essentially a workaround to what really ought to be a core function.

    Likewise, yes, we can add tags in Acrobat to enable accessibility on the post-production side, but if ANYTHING changes in the original and needs to be updated, all of that post-production work in Acrobat has to be re-done on a newly-exported PDF. This makes it an inefficient workaround, not a legitimate solution.

    Illustrator needs this tagging for accessibility functionality natively.

    David Swisher supported this idea  · 

Feedback and Knowledge Base