Jump to content

JohannaH

Members
  • Content Count

    6
  • Joined

  • Last visited

Everything posted by JohannaH

  1. Thanks for starting this thread William! I really hope Serif will act on this and provide us with the right tools to make our digital products accessible. I love these apps and I want to use them for a very long time.
  2. First of all, it's not my satisfaction, @William Overington. I started in this job in June last year and I'm still learning a lot about accessible documents. It's a complicated subject, but very interesting as well. I'm pleased to hear you want to get this right. As an author you can certainly do things. Some of which doesn't depend on the tags that are needed to make the PDF available to screenreaders and other tools for people with disabilities. On this website at W3 you'll find techniques to make PDF's accessible. There are 23 pages about PDF, the link takes you to the first of them. https://www.w3.org/TR/WCAG20-TECHS/pdf_notes.html Accessibility is also about the use of color, contrast of color, meaningful text, the title of the document (which you will see in the tab of the PDF reader), the right language, the use of headings in the right order (h1, h2, h3), reading order, and so on. If done right it'll help all your readers and it'll give all of them a better experience.
  3. I've posted something in another thread (Tagged PDF support for accessibility in Feedback for Affinity Publisher) about this accessibility in PDF. Here is a copy of that text. I hope it helps you understand what this is about. "I totally agree with others on this subject. It's part of my job to check accessibility of PDFs. And most of them aren't accessible. But according to the law all content on a government (related) website in my country (part of the EU) and many other countries should be accessible. So that includes all PDFs on that website. Of course there is an exception for old documents. But new PDFs just have to be properly tagged so a screenreader is able to use it and read it to a blind person. And when that's the case, then it is usually also accessible to other tools used to help people to read or understand digital content. Within a bit more than a year the process of making all content on all websites in the EU will start and in June 2025 all company websites have to be accessible except the ones from very small companies. https://en.wikipedia.org/wiki/European_Accessibility_Act If Affinity doesn't solve this problem it will be impossible for designers to use this software as their products can not be published on websites anymore. We would be left with Adobe products just because they do have tags in PDFs, not because they are very good at it, they are not. I love all Affinity software, but I have to use other software to create accessible PDFs, like Adobe Acrobat, MS Word, Axes4 (Word Plugin and PDF QuickFix). I want to use Affinity!! Affinity team, please add tagging to creating PDFs! And please have a look at other things like a contrast checker, a checker of the the headings, and so on. Here you'll find some info: https://www.pdfa.org/wp-content/uploads/2019/06/TaggedPDFBestPracticeGuideSyntax.pdf https://www.pdfa.org/wp-content/uploads/2014/06/MatterhornProtocol_1-02.pdf https://www.axes4.com/resources.html https://www.access-for-all.ch/en/pdf-accessibility-checker.html https://www.access-for-all.ch/en/pdf-accessibility-checker/vip-pdf-reader.html"
  4. I totally agree with you @PaoloT. It would be great to use an app like Affinity Publisher to create good layouts for webpages with a lot of content. I'd like to combine the knowledge about magazine design, book design and so on with web design. The output doesn't have to be a full webpage. Just a part of it with only the 'text' part of html would be fine. (paragraphs, headings, articles, images with alt-text, proper lists, etc) If you could create just a <main> part of a webpage with content or even just an <article> in html that would be a huge improvement. It would allow content creators to do their job and then merge it with the work of the frontend developer who created the page template. And html is accessible if it's built according to WCAG criteria. And for the content part that's not exactly rocket science.
  5. I think there is some danger when it comes to the future of apps like Affinity Publisher. To survive as an app with which you can create PDFs or other documents that will be published online, that app needs to be capable to create accessible PDFs/documents. And that's not the case with Affinity Publisher (and many other software used to create PDFs). Many organisations are already required by law to only publish accessible content on their websites. And PDFs are web content, whether they are shown in the browser or just available using a link. Even if they are created only to be printed after downloading, they still need to be digitally accessible. In the coming years most company websites have to be made accessible for all people and not just the abled ones. Publisher apps like Affinity Publisher need to be capable of creating such accessible content or they'll become useless to any designer who's work ends up on a website.
  6. I totally agree with others on this subject. It's part of my job to check accessibility of PDFs. And most of them aren't accessible. But according to the law all content on a government (related) website in my country (part of the EU) and many other countries should be accessible. So that includes all PDFs on that website. Of course there is an exception for old documents. But new PDFs just have to be properly tagged so a screenreader is able to use it and read it to a blind person. And when that's the case, then it is usually also accessible to other tools used to help people to read or understand digital content. Within a bit more than a year the process of making all content on all websites in the EU will start and in June 2025 all company websites have to be accessible except the ones from very small companies. https://en.wikipedia.org/wiki/European_Accessibility_Act If Affinity doesn't solve this problem it will be impossible for designers to use this software as their products can not be published on websites anymore. We would be left with Adobe products just because they do have tags in PDFs, not because they are very good at it, they are not. I love all Affinity software, but I have to use other software to create accessible PDFs, like Adobe Acrobat, MS Word, Axes4 (Word Plugin and PDF QuickFix). I want to use Affinity!! Affinity team, please add tagging to creating PDFs! And please have a look at other things like a contrast checker, a checker of the the headings, and so on. Here you'll find some info: https://www.pdfa.org/wp-content/uploads/2019/06/TaggedPDFBestPracticeGuideSyntax.pdf https://www.pdfa.org/wp-content/uploads/2014/06/MatterhornProtocol_1-02.pdf https://www.axes4.com/resources.html https://www.access-for-all.ch/en/pdf-accessibility-checker.html https://www.access-for-all.ch/en/pdf-accessibility-checker/vip-pdf-reader.html
×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.