Accessibility issue - AEM generating faulty tags/DOJ rule re Web Content | Community
Skip to main content
C
CØK
Level 4
July 23, 2024
Question

Accessibility issue - AEM generating faulty tags/DOJ rule re Web Content

  • July 23, 2024
  • 2 replies
  • 1987 views

We use desktop version 6.5.17.

I have attached three files to this post:

Test 1: File > Form Properties > Save Options > Generate Accessibility Information (Tags) for Acrobat checked

Test 2: File > Form Properties > Save Options > Generate Accessibility Information (Tags) for Acrobat unchecked

When opening Test 1 in Acrobat and applying Read Out Loud, the text before and including the link in bullet 2 is omitted - only "to understand your responsibilities" is read. Otherwise, the reader follows the tab order set in AEM.

When opening Test 2 in Acrobat, the Popup "Prepare document for screen reader" appears. The full text is read, however, the tab order set in AEM is ignored, and the reader proceeds in a top>bottom, left>right mode.

Test1 tags: Image displaying that the text "Before you fill out this form, read What Is Proof of Service? (form APP-109-INFO" is not tagged.

Why does AEM generate faulty tags? As you know, it is NOT possible to modify an XFA form in Acrobat.

I would also note that if not fixed, this is going to be an issue for state and local government customers given the DOJ's issuance of its final rule on accessibility of web content. For more, see https://www.ada.gov/resources/2024-03-08-web-rule/.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

C
CØKAuthor
Level 4
July 24, 2024

Any takers on this one? Adobe?

    C
    CØKAuthor
    Level 4
    July 31, 2024

    Hey Adobe - I do not have the required rights to open a ticket. To us, this is an enormous issue. Can someone please help get some traction on this?

     

    Do we think this issue may be related to links?

      R
      Adobe Employee
      rupalim1Adobe Employee
      Adobe Employee
      September 12, 2024

      Hello @cøk 

      We would need more data to analyse the cause of this issue.

      If you can share the template file and the config file (xci) used here to create the PDF, that would be helpful.

       

        G
        Adobe Employee
        gvdpatida1Adobe Employee
        Adobe Employee
        September 12, 2024

        Test1 -> As i can check ,You have generated this pdf using designer and list item is not tagged properly , that's why screen reader/Read aloud loud is only enunciating "to understand your responsibilities" , Please check . You can upgrade to SP21 designer and generate desired pdf to fix this issue.

         

        Test2 -> test2.pdf is not tagged, We need to tag this pdf in creation process , please try with SP21 designer .

         

        Let me know if more input required.

          C
          CØKAuthor
          Level 4
          September 12, 2024

          Also, please specify what "list item is not tagged properly" means - how are we supposed to tag it if not as a list item?

            C
            CØKAuthor
            Level 4
            April 2, 2025

            This is a known issue in 6.5.17.0 . You can upgrade to 6.5.21.0 designer to find fix to your tagging issue. I would recommend to go with x64 bit . 

            How to upgrade :- https://experienceleague.adobe.com/en/docs/experience-manager-65/content/forms/install-aem-forms/jee-installation/installing-configuring-designer


            As evidenced by the two attached files, this appears to not be correct. 

            We are on v6.5.21. 

            If you open v1 in Acrobat, you will find that one text field, item 1, Name, is not picked up in the tagging order at all. The reading order is completely off.

            In v2, all items are represented in correct order. 

            The ONLY difference between the two files is the link below the large text box.

             

            Can you please tell me if and when this behavior will be corrected? I do not have admin access and cannot log tickets. This is a problem while trying to comply with WCAG 2.1 AA as required by the US DOJ.

            Terms & ConditionsAccessibility statement

            Loading footer...