Skip to main content
Participant
December 22, 2024
Pregunta

Acrobat accessibility checker constantly fails for me??

  • December 22, 2024
  • 1 respuesta
  • 297 visualizaciones

I get this all the time - I run the accessiility full check and it brings up a few errors, eg my current document has 'other elements alternate text failed'. I click on that and the list expands to say 6 elements. I click on Element 1 but I have to wait a long time for the software to actually find and show the page. It eventually shows me the page but won't actually show the problem element. Nothing gets highlighted. This is absolutely useless! It can take me a long time trying to identify and correct problems as the software does not help at all. Does no-one else get this ????? For me it's the same with both home and work macs.

Este tema ha sido cerrado para respuestas.

1 respuesta

S_S
Community Manager
Community Manager
December 22, 2024

Hi @zebedee4321,

 

Hope you are doing well. Sorry for the trouble.

 

This error could occur due to certain objects in the document either being tagged as a picture in the parent document, or any image object that has not been highlighted as an image.

 

To better understand the issue and assist you accordingly, would you mind sharing the document with me? If it contains sensitive information, you can share the file with me over a private message. 

To do so, click on my profile name followed by the blue "Send Message" button on the next page.

 

Look forward to hearing from you.


-Souvik

Participant
December 22, 2024

Thanks for the reply. I can't share this as it's an as yet unpublished government document, but it's literally the same problem every time I do any work, as described above. Production with Adobe InDesign. I have found one workaround in that my mac at home is old and I can still run Adobe acrobat pro 9 which will do this function. I can't do this in the office at work though so it's more than inconvenient. It always seems like a major fail when software 'upgrades' don't work and yet predecessor version do. The problem is not how things are tagged (which Acrobat clearly recognises), it's that the software refuses to identify what the problem is.