Static PDF rendered using outputservice.generatePDFOutput has 'form' tags for text fields

Hi ​@SmrithiGo 

For static PDFs generated by OutputService.generatePDFOutput from XDP this is expected behavior and you cannot selectively stop it:

• When you enable tagged PDF, Output Service produces a non‑interactive (flat) but tagged PDF; fields are represented with <Form> structure elements to meet PDF accessibility conventions, but the PDF is still read‑only for the user.
• See how Output generates non‑interactive PDFs: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/forms/use-document-services/overview-aem-document-services 
• See generatePDFOutput/output options: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/forms/developer-reference/programming-aem-forms-jee/performing-service-operations-using-apis/creating-document-output-streams

Screen readers (like NVDA) interpret those <Form> tags as read‑only form controls, and the exact wording they speak (for example "edit unavailable read only") is controlled by the screen reader, not by AEM or Output Service.

So your only real options are:

• Disable tagging for that output
  • Turn off tagged PDF in your options/XCI (for example, set the PDF to be not tagged via XCI config/present/pdf/tagged or equivalent Output options), so no <Form> structure tags are generated at all.
  • Example for tagged setting in Submission PDFs: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/forms/adaptive-forms-authoring/authoring-adaptive-forms-core-components/create-an-adaptive-form-on-forms-cs/html-markup-tags-support-in-document-of-record
  • Trade‑off: the document is no longer a tagged/accessible PDF.
• Post‑process in Acrobat/other tools
  • Keep Output Service as‑is, then manually adjust the tag structure in Acrobat (for example, change or remove <Form> elements) knowing this is outside what Output Service itself can control.

There is no Output Service setting that both keeps a tagged static PDF and prevents NVDA from announcing those read‑only fields; that announcement is on the NVDA side.