[Accessible PDF (tagged PDF) and (accessible) EPUB with Publisher?]

As long as lists are not tagged/coded as such, or TOC, or no support for Heading H tag nor for correct tagging of hyperlinks the exported PDF does not comply with WCAG nor 508 (let alone PDF/UA).

Therefore you must do all that sort of tagging in Acrobat on a PDF exported from Publisher.

And no one needing WCAG/508 compliant accessible PDF’s is going to touch A Publisher therefore.

Step up your game Affinity or Canva or… whoever these days….

[Still no Tagged PDF...]

I get it, you’re a typical young fan boy, not ready for discussion. I’m out.

[Still no Tagged PDF...]

Quote

 

 again a „Still no …“ post with a „first priority“ feature claim. I love it! 

What an enormous encouragement for the Affinity team …

 

Well, If you like to see the software change a change out there in  professional use, tagged PDF is a necessity ...  Simple as that. InDesign has it. QuarkXPress has it.

[Still no Tagged PDF...]

Mentioned before, but as long as there is no support for tagged Accessible PDF, this version can not be used in a professional enviremont that creates PDF that is also put on line for Government and Government related publications in The Netherlands, Germany, France, UK, USA to name a few...

Did you miss it is required now? And in the USA you can even be fined when it is not accessible online?

First priority!

[Scanner support!]

The thing still missing for me is Twain scanner support (or VueScan) to have a port directly to my scansoftware to Affinity Photo (and Designer)!

[Plug ins folder added, Tools gone]

TOne thing however, the adding of a plug-in folder means loosing the visibility of all tools and many options can not be selected; the plug-ins however do not show up. Removing the path to any plug-in folder and restarting gets the tools back again. Mac 10.10.2, Dutch, iMac 27" late 2013, 32 GB RAM.