What exactly is it that does not work? Wat does 'not correctly' mean for you?
Thanks for your fast answer.
For me, a non working accesible PDF table is:
1. If I hit command+4 in a Macintosh, I'll get a reflow view. But the tables exported from InDesign are losing the cell/table borders and the background colors, so it's really difficult recognize that data as a table.
2. If I select the table in the structure panel and delete only the table structure, then using the touch up reading order tool, I define it as a table, when hitting command+4 it shows the table background, but not the table border nor cell border. At least it's recognizing it as a table, and I'm only losing the borders.
So, what I need is the correct workflow for exporting hundreds of tables in an InDesign document to an accesible PDF, and then, that the tables show the background and the borders as defined in InDesign when using the reflow view.
In InDesign I'm using paragraph styles, cell styles and table styles
As far as I can tell you are rather describing limitations in functionality (reflow) provided in a specific commercial product (Adobe Readeer/Adobe Acrobat). For my taste this does not count as an accessibility issue.
Those familiar with Reflow in Adobe Reader/Acrobat know that its functionality has been limited already since it was first included in the product many years ago. My guess is that Adobe intended to provide something that makes reading regular text easier for certain users (e.g. those wishing to increase the text size without being forced to having to scroll horizontally). I also guess it was never intended for complex document substructures, like tables.
I suggest you find out what is offered in other, more modern implementations of customizable reflow from taged PDF, including support for such complex substructures, like the free VIP Reader ( http://www.access-for-all.ch/en/pdf-lab/500-vip-pdf-reader-e.html ) or the free pdfGoHTML plug-in ( Free Adobe Acrobat plug-in converting tagged PDF files into HTML [callas software] ) for Adobe Acrobat. [Disclosure: pdfGoHTML has been developed by my company, callas software]
"Accessible PDF" = PDF that is ISO 14289-1, PDF/UA-1 compliant.
You want "reflow friendly" PDF which, basically, is not the same thing as and "accessible" (tagged - PDFU/UA-1) PDF.
To get there from here you'll need to revisit the authoring file / application and lay the ground work there.
Consider output of a PDF that is not 'tagged'. You not needing an "accessible" PDF.
A helpful resource: