I've seen more threads about this subject, but haven't found a satisfying answer yet...
I'm trying to create an accessible pdf-file from an InDesign file (a flyer with a lot of small text blocks; no threading). I followed all the steps in this (excellent!) description: https://helpx.adobe.com/indesign/using/creating-accessible-pdfs.html, (among other things) setting the (desired) order in the Articles panel. I thought that would determine the reading order in my pdf. After exporting, the reading order as shown in Acrobat's accessibility tool is just totally random (and not at all the order I put in the Articles panel). (I can't post any screenshots cause my client's information is confidential)
I read some posts where people said 'Acrobat doesn't show the right order, but in practice it does have the right order' but how can I check this? I tried the VoiceOver function on my Mac, but I guess I need more training to be able to use that properly (besides: it shouldn't be necessary - though it is a great user's test).
Can somebody please enlighten me and help me solve my problem?
Copy link to clipboard
You should thread the text bloxks in the right order. If not, InDesign follows the order when these text rame were created.
I wonder why you use different text frames? In my experience most, near to all, layouts can be done in a single text frame. This will guarantee the right reading order.
Thank you, @Willi Adelberger for your reply.
I didn't use threads because there's no need for it; text blocks are standing on their own and I don't want text to flow into another block. It's more of an infographic/schematic visualisation, so I need to be able to position all the blocks very precisely.
But I guess threading might be a workaround...
Still hoping somebody can help me find a better method (like the one Adobe provides - but then with a better result)...
Copy link to clipboard
Are you referring to "tab" order or "reading" order? Your title and text refer to different things.
In human terms, it's the reading order: how the information should be read.
In Adobe terms I guess it's the tab order: the order in which a screen reader should be guided through the document in a logical way (either by tab or buttons/inputs).
No--two different things. Reading Order is what you want. Did you check your Acrobat Pro Accessibility tools for the reading order?
Did you select Use for Tagging Order in Tagged PDF?
Depends upon which screen reader or assistive technology you're using. It's NOT the TAB key on your keyboard, but rather any key or action that is programmed to advance the content.
"TAB order" is an out-of-date term, a holdover from decades ago when the actual TAB key was used by screen reader users to move through the content. But the name hasn't changed to keep up with our newer technologies and protocols.
If your A T is PDF/UA-1 compliant, then it should respect the TAB key and move through the content. But so many technologies don't use the TAB order, or ignore it entirely.
Most of our screen reader testers remind us that they DON'T TAB through a document. They use other mechanisms for navigation.
Thanks, I've read all the other posts on this subject, so I knew this. I don't mind which input people use; I just want to deliver a document that is 'accessible' for people that need it. I followed Adobe's guidelines (as mentioned in my post) and that didn't seem to work; so I'm looking for 1. What I did wrong or 2. another practical solution...
Here is a good read that might help (from Bevi, naturally...):
Jump to the correct answer.
Thanks, @Creamer Training for the reference.
@YvonS, I not sure what you're finding wrong with your PDF. You seem to have done all the right tasks, but something isn't working for one or more reading orders.
So let's review, first. Apologies for this long, detailed reply, but the answer is not short and quick.
There are 4 reading orders in a PDF.
More details are at this blog: https://www.pubcom.com/blog/2020_08-18_ReadingOrder/reading-orders.shtml
Different assistive technologies (AT) tap into one or more of these reading orders.
Our accessibility firm recommends this plan of action:
Question: which reading order is having problems?
And did any of this correct the problem?
Tag RO and Tab RO are all set in my document, but it gets messy when I try to fix the architectural RO… This order is totally messed up in the first place; probably follows too much of the order in the Layers panel? And that just doesn't make sense to me at all - why would they use the stacking order of my visual elements to dictate a reading order…? I tried to fix this, but here arises the next problem: when I do, my tekst disappears - looks like it ends up behind one of the white/blue blocks (as shown in screenshot: left: original order in the order panel; left: what happens when I try to correct it…)
Bonus question (it was in my initial post): how can I check my document's accessibility myself? Acrobat's check is not very trustworthy, I guess. And it tells me to check the reading order myself - which is exactly the problem 😐 (see above).
I read about PAC 2021 - which is only available for Windows 😞 (I'm a Mac user)
Use Acrobat/Preflight/PDF standards/ run the one under PDF/UA, that checks more items; there is also a fix up there.
May I advice you to follow a training course? As it is complicated indeed. If you are Dutch: I'm doing a two days online training beginning September 27th in the Netherlands, drop me a PM if you are interested 😉
Frans is great. Take advantage of his coures if you can.
There is no software checker that can thoroughly check your PDFs.
It's something you'll always need to check on your own, as well as using a checker.
It's Apple that prevents accessibility tools on the Mac, not Adobe or Microsoft. So it will be a while before we get something acceptable for Mac designers.
In the meantime, either run Parallels software on your Mac and installed Windows under it, or buy an inexpensive Windows laptop or computer and outfit it with checker and screen reader testing software.
Don't drag that order in Acrobat, it is like dragging text below frames in InDesign (top/bottom)!
The Article panel ONLY sets the Tag order; the Layer panel sets the Reading/Z/Logical (whatever you want to name it) order, and that one is from bottom to top! So go back, open the Layers panel and there place them in the order you want: bottom ('1') and then stack up. So a bit 'reversed' in what you see in the tags-tree (Article panel).
It appears in your sample that each blue block with text has 2 elements: a text frame holding the text, and a blue box behind the text.
When you rearrange the elements to correct the RO, then the text is falling behind the blue box. There are 2 solutions in InDesign:
Always strive to simplify your layout in terms of the number of frames on the page. The more frames you have, the greater likelihood of accessibility problems.
No client before me has asked for accessibility, so I'm new on the subject and definitely learning a lot!
I had my reasons for designing it this way and will definitely take it into account for my next projects.
Though I still don't understand why Adobe makes it so hard for us and uses the Layer panel to dictate a reading order (wouldn't it be great if they would just use the Articles panel for all orders? And why it's so difficult to test your designs. I plea for making accessibility accessible for everyone 😉 . It shouldn't be just for the pros/specialists in the field.
Thanks to all contributors!
I like simplicity, but unfortunately, that doesn't work in more complex lay-outs, like the one below (I had to blur the contents for confidentiality reasons). Textblocks and colorblocks have to be disconnected, because reading order and layering (visual) order are not the same 😞 .
It's just an example, but this is what information designers encounter in daily life... Do you see a way to make this simpler?
Thanks for the detailed screen shot, @YvonS. It explains what you're trying to create.
Examining this from an accessibility viewpoint, you have a table of information that should be arranged in a spreadsheet matrix of columns and rows — there's the WAT column, and the HOE column that is further broken down into 2 sub-columns.
It really shouldn't be individual text blocks that you then have to wrangle into a correct Tag reading order and Architectural reading order.
A table structure is required because the user must be able to read down the first column and choose either Documents, E-mails, SMS, or WhatsApp, and then read across the row to find the screenshots or video instructions. This is exactly the correct functionality that a table structure gives end users. Plus, your reading orders are set perfectly!
I quickly created this sample that mimics your design (both the InDesign and PDF files are attached).
The key is that I created a table that sets the correct accessible structure for the content. And then I created Paragraph Styles to format the heck out of it. I heavily used the new Paragraph Shading and Borders settings in paragraph styles to create your design of the blue "hotdog" boxes.
By using Paragraph Styles to do the visual formatting, most of the text boxes are eliminated and your reading orders are left in tact. I did nothing to the PDF, other than to do the usual minor corrections to table span settings, which took all of 1 minute.
... Do you see a way to make this simpler?By @YvonS
As Mies van der Rohe said, "Less is more."
And as Bevi Chagnon says, "Not only is 'less' more, 'less' is more accessible." <grin> (I have a degree in architecture and studied the philosophy of Mies and the Bauhaus movemement. Their theories have greatly affected my graphic design career ever since.)