[Tagged PDF support for accessibility]

I totally agree. I don't know many designers who even know it's possible to create an accessible PDF, or what it actually means. But everyone gets it for web work. I can't see a single disadvantage of PDFs were created to be accessible by default.

[Tables inside text frames - mandatory]

1 hour ago, walt.farrell said:

They can be placed into text frames already. But they cannot be anchored to a specific point in the text.

To put a table into a text frame:

1. Create the text frame. Fill with text.
2. Create a table somewhere outside the text frame. Use the Move tool to put it over the text frame where you want it.
3. Adjust Text Wrap settings as appropriate.

A similar approach can be used for images, shapes, etc. Create them, move them on  top of a text frame at an appropriate position, adjust Text Wrap settings.

However, for all of these, if you add more text it will continue to flow around the placed object, and you cannot (at this time) keep the object positioned with any specific piece of text.

While text wrapping is useful, it's not a substitute for anchoring. I'm sure they have a plan for it, I just hope it's sooner rather than later. I'm dreaming for a pro-level tool that is better/more intuitive than InDesign particularly for modern output. Without anchoring ePub isn't possible, and accessible PDFs become harder to achieve.

[Basic things that I'm looking for]

Firstly – bravo for this. I do feel it's a little premature as there seem to be a chunk of vital things missing, and the absence of a road map leaves many of us guessing what will/won't be in the production ready app.

That said here's some things I wanted to see of the bat that, in my 2 hours messing about I felt confused about/lacking.

1. Find/Change. GREP is a must, but more basic functions like find/change needs to there from the beginning. 
2. Why is the leading so far from the type size? In my mind they are part of the same coin. The UI has 715px between the point size and the leading. I don't understand that logic.
3. Asymmetric draggy columns are wonderful, but I can't see how to edit the gutter. I expect it's in the pipeline.
4. Quick apply. it's a pro level feature that pro apps have: InDesign, Cinema 4D, After Effects) so useful especially for those on smaller monitors.
5. Bullets – aligning the following lines in bulleted lists seems only possible manually? Or did I miss something?
6. Overflowed text. I gave up trying to work out where I had overflowed text (export alert). I don' think I really had any but all my PDFs insisted I had some.
7. The exported PDF is the most basic PDF I've seen in years and I'm unsure if I trust it for print or screen. I need to do some more investigation, but in terms of Accessibility for screen it's appalling. Please tell me the team have a plan in place to make the best PDF's possible.

[Tables inside text frames - mandatory]

+1 here. Anchoring a table (or any element inside a text frame) is a must. 

In addition being able to specify table head rows (and columns) is important not only for long tables that flow over multiple pages/columns but also with respects for exposing an accessible PDF. Without specifying them any A11y checker will fail the PDF.

[interactive pdf with form fields]

Currently the whole PDF export is bare-bones. I'm crossing my fingers there is a team on this as that are not only making decent interactive PDFs as soon as possible but also go above and beyond for accessibility too. For me it's essential if I want to jump ship. It's just not right preventing such a huge number of people using a document (and it's a legal requirement in many countries too).

[Accessible PDF]

I'd be very interested in understanding how Publisher will address accessibility in their exported PDFs. Currently there is no way to tailor a document to export a PDF with any acknowledgement of A11y. I appreciate that it's early days. I just hope it hasn't been left too late. InDesign has been trying to address it, but it too was appalling in its early versions. I expected that a progressive new app might be thinking about this and build it in from the very beginning — after all we are building documents for screen so often, we can't just ignore the requirements of so many.