- From: <chagnon@pubcom.com>
- Date: Fri, 11 Jan 2019 17:02:02 -0500
- To: "'Andrew Kirkpatrick'" <akirkpat@adobe.com>, "'Bonnie Felt'" <Bfelt@mmgyglobal.com>, "'WAI-IG'" <w3c-wai-ig@w3.org>
- Message-ID: <003901d4a9f9$48d2c370$da784a50$@pubcom.com>
Most likely it’s an Adobe® Tagged PDF exported from an InDesign layout, so it does not use a markup language; instead it uses the tag set defined in PDF/UA-1. Bonnie, the PDF/UA-1 accessibility standard is similar to WCAG’s, but is developed specifically 1) to take advantage of features that are only in PDFs, and 2) to coordinate with the goals of WCAG. PDF/UA actually makes a more accessible PDF than you can get if you try to shoehorn WCAG onto a PDF because PDFs are not based on HTML technologies. Contact me off list if you’d like more information. — — — Bevi Chagnon, founder | <mailto:Bevi.Chagnon@PubCom.com> Bevi.Chagnon@PubCom.com | 301-580-1944 cell/text US delegate to the ISO for PDF and PDF/UA universal access standards Adobe Community Professional - ACP — — — PubCom: Technologists for Accessible Design + Publishing print | digital | web | documents | pdfs | epubs consulting • training • development • design • sec. 508 services ms office • adobe acrobat • indesign • xml + automated workflows — — — How We Work: <https://www.pubcom.com/downloads/about-PubCom_2018_v4_508.pdf> see slidedeck Classes: Upcoming classes at <http://www.PubCom.com/classes> www.PubCom.com/classes — — — <https://mailchi.mp/ff5bd323ea45/newsletter-accessibility-fonts-design-upcoming-classes-2901237> Latest blog-newsletter – Accessibility Tips From: Andrew Kirkpatrick <akirkpat@adobe.com> Sent: Friday, January 11, 2019 9:09 AM To: Bonnie Felt <Bfelt@mmgyglobal.com>; WAI-IG <w3c-wai-ig@w3.org> Subject: Re: WCAG 2.1 compliance for brochure pdfs Forwarding to WAI-IG list for discussion. As a quick note to help with the discussion, I can tell you that the first question you will be asked is whether the online brochure is implemented using markup languages that support the style properties. If not, then 1.4.12 won’t apply. Thanks, AWK Andrew Kirkpatrick Head of Accessibility Adobe akirkpat@adobe.com <mailto:akirkpat@adobe.com> http://twitter.com/awkawk From: Bonnie Felt <Bfelt@mmgyglobal.com <mailto:Bfelt@mmgyglobal.com> > Date: Friday, January 11, 2019 at 9:03 AM To: "public-agwg-comments@w3.org <mailto:public-agwg-comments@w3.org> " <public-agwg-comments@w3.org <mailto:public-agwg-comments@w3.org> > Subject: WCAG 2.1 compliance for brochure pdfs Resent-From: <public-agwg-comments@w3.org <mailto:public-agwg-comments@w3.org> > Resent-Date: Friday, January 11, 2019 at 9:03 AM Hello, We create printed brochures for a cruise line and they desire to be WCAG 2.1 compliant for their downloadable brochures posted on their website. The online brochures are the same as the printed with adjustments made for color contrast. The client is particularly concerned about the Success Criterion 1.4.12: text spacing. We design the brochures for print first. Then we adjust color contrast and send them to a company to be remediated to make them accessible. The layouts and text do not change in this process. Then they are posted to the clients website. The brochures are also emailed upon request. My question: Is it necessary for the text in these brochures to follow the guidelines found in Success Criterion 1.4.12? Thank you, -- BONNIE FELT Graphic Designer <http://www.mmgyglobal.com/> MMGY Global <tel:424%20309%200810> 424-309-0810 direct <tel:310%20649%207714> (310) 649-7714 main <http://facebook.com/mmgyglobal> facebook.com/mmgyglobal <http://twitter..com/mmgyglobal> twitter.com/mmgyglobal THINK again. Do you really need to print this entire email? The information in this e-mail is confidential and is intended only for the use of the above named recipient. In certain cases it is also legally privileged. If you are not the intended recipient, any dissemination, distribution or copying of this email is strictly prohibited. If you have received this e-mail in error, please advise immediately by return e-mail.
Received on Friday, 11 January 2019 22:05:01 UTC