Introducing the PDF/UA Processor LWG
The new PDF/UA Processor LWG will work to formalize common understandings on processing PDF/UA-conforming PDF files.
Improving accessibility support for PDF documents means improving the way PDF viewers, other PDF processors and assistive technology (AT) handle tagged PDF.
Although PDF/UA-1 provides conceptual requirements for processors, these have not been formally adopted as broadly as have PDF/UA’s file format requirements. PDF/UA-2, anticipated to be published in 2023, differs from PDF/UA-1 in that it focuses exclusively on file format requirements, with requirements for processors to be developed in a separate dedicated specification.
In support of this objective, the PDF Association has created the PDF/UA Processor LWG following a request from the working group responsible for development of PDF/UA, ISO's TC 171 SC 2 WG 9.
Chaired by PDF Association member CommonLook's Paul Rayius, the new Liaison Working Group will operate a schedule of meetings for the PDF and assistive technology industries to formalize common understandings on processing PDF/UA-conforming PDF files.
In particular, the PDF community seeks the involvement and input of developers who focus on assistive technology, including accessibility APIs, in addition to those who are already familiar with Tagged PDF, and PDF/UA. As a Liaison Working Group, independent developers and those employed by non-member organizations are nonetheless welcome to participate in scoping and creating this processor specification.
This new community will work closely with the PDF/UA TWG, PDF Reuse TWG, Deriving PDF to HTML TWG, LaTeX Project LWG and others to ensure that the entire ecosystem of those working on developing Tagged PDF technology are aware of and may contribute to these efforts.
PDF Association members can join this new LWG via the Member Area. Suitably qualified non-members wishing to participate at no cost should contact info@pdfa.org to request access.
NOTE: Developers who contribute to or are experienced with popular accessibility APIs, including but not limited to the following, are especially welcome!