Skip to content
← Acrobat for Windows and Mac

Feature request / Bug report

Acrobat for Windows and Mac: Accessibility

Categories

JUMP TO ANOTHER FORUM

(thinking…)

PDF forms using JAWS and NVDA Screen readers with latest Acrobat update

With the latest update of Acrobat (2024.002.20895) I have been experiencing issues reading, completing, and interacting with PDF forms using both JAWS and NVDA screen readers. The screen reader keeps leaving forms mode when I'm in fields. Instead of typing into the field, it recognizes my keystrokes as JAWS commands. For example, when I try to type "Henry" in a Name field, pressing "H" makes it jump to the next heading in the document instead of typing the character(s). I have confirmed that I am in forms mode (both visually and via the sound the screen reader makes when entering a field in forms mode). Sometimes, I have to tab past a field and then back to it before The screen reader announces it. One of our staff members who uses a screen reader mentioned this issue to me last week, and I’ve confirmed it with other screen reader users. When not using a screen reader, the forms work fine, but with JAWS or NVDA running, they act up. Documents without form fields are reading fine, but those with form fields are having issues. This was first noticed with the previous update and continues with the current one. The forms have been validated as accessible through manual testing and using the latest version of PAC 2024. We were able to use these same forms without issue before the last two Acrobat updates.

4 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

James Brown shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Ayush Jain commented  ·   ·  Report

    Hi James,

    Thank you for being so patient.

    In our latest update, we have fixed the issue related to the forms field.
    They should work with the screen reader enabled.

    Please update the application to the latest version 24.002.20933

    Thanks again for highlighting the issue.

    Regards,
    Ayush Jain

  • Carol Weber commented  ·   ·  Report

    In the Office of Vocational Rehabilitation in Kentucky, we use Acrobat forms for most of our interactions with our consumers. In order to apply for services, for example, a consumer and staff member work together to fill out an Acrobat form. Using either Acrobat Reader or Acrobat DC, on these forms when using either JAWS or NVDA, every time I move into a new form field, it exits forms mode so I can't input information into the field. Instead it interprets what I type as a screen reader command. For example, if I am entering the name "Thomas" into the name field, when I type "T", it tries to move to the next table in the form, or if there are no tables, it says "no next table." Additionally, if there is a table, the cursor jumps to that table and then I have lost my place in the form. This didn't happen prior to the last update. Both staff members and consumers have complained. Is there a timeline to fix this problem or will I need to recommend the agency move away from using Acrobat products?

  • James Brown commented  ·   ·  Report

    So how is a person using a screen reader supposed to interact with and enter information into a form? Are you saying this is expected behavior, or will this be addressed via an update? If so, what kind of timeline can we expect this to be completed?
    We are a government (state) agency and have many PDF forms that our staff use daily. Those staff using screen readers are currently unable to independently complete these forms, thus unable to effectively fulfill their essential job duties.
    As I mentioned in my original post, this was not an issue before the latest two updates. Before these updates, screen reader users were able to tab directly to a field and type their response. This is both for JAWS and NVDA Screen readers. Both of these tools have two distinct modes (reading mode and forms mode). Forms mode is supposed to allow you to type into the field, which is a form of editing.
    Are you going to fix this?

  • Ayush Jain commented  ·   ·  Report

    Hi James,

    Thank you for taking the time to write to us.

    We acknowledge your issue and would like to share the following details.

    When a screen reader is active, editing isn’t supported. So, if a user with an enabled screen reader tries to input text, the system exits edit mode. This consistent behaviour applies across all Acrobat edit types.

    Thank you again for your patience.

    Regards,
    Ayush Jain

  • Ryan Creech commented  ·   ·  Report

    Having exactly the same problem in this version. Destroys the user experience in PDF forms and requires a ton of extra steps and tech skills to read/complete the form. Trying to use the NVDA+Tab command in a PDF form field generally reads the tooltip but is just reading the file path. Thought it was an issue with my screen reader but can confirm same behavior in JAWS.