ISO 14289-1 (PDF/UA) (Sample Report) - Microsoft



ISO 14289-1 (PDF/UA) (Sample Report)Date: July 27, 2017Product: Microsoft Word 2016Contents TOC \o "1-3" \h \z \u Overview PAGEREF _Toc488943576 \h 11. Scope PAGEREF _Toc488943577 \h 12. Normative references PAGEREF _Toc488943578 \h 13. Terms and definitions PAGEREF _Toc488943579 \h 24. Notation PAGEREF _Toc488943580 \h 25. Version Identification PAGEREF _Toc488943581 \h 26. Conformance requirements PAGEREF _Toc488943582 \h 27. File format requirements PAGEREF _Toc488943583 \h 28. Conforming reader requirements PAGEREF _Toc488943584 \h 109. AT requirements PAGEREF _Toc488943585 \h 10Disclaimer PAGEREF _Toc488943586 \h 10OverviewThis document describes Microsoft Word 2016’s conformance to ISO 14289-1 (PDF/UA) specifications.1. ScopeNot Applicable2. Normative referencesNot Applicable3. Terms and definitionsNot Applicable4. NotationNot Applicable5. Version IdentificationWord provides support for PDF/UA as described in this document. In some instances, noted below, it is incumbent on the user to take steps to ensure that a PDF is in full compliance with PDF/UA. We expect the user will add the appropriate PDF/UA version and conformance identifiers as the last step in this process, indicating that the necessary work has been done to make the PDF entirely PDF/UA compliant. 6. Conformance requirementsCriteriaSupporting FeatureRemarks 6.1 GeneralSupportedWord exports PDF version 1.7.6.2 Conforming filesSupported with ExceptionsSee remarks in section REF _Ref474156658 \h 7 – File format requirements.6.3 Conforming readerNot Applicable6.4 Conforming assistive technologyNot Applicable7. File format requirementsCriteriaSupporting FeatureRemarks 7.1 GeneralSupported with ExceptionsAll real content shall be tagged as defined in ISO 32000-1:2008, 14.8. Artifacts (ISO 32000-1:2008, 14.8.2.2.2) shall not be tagged in the structure tree.Word does not offer the flexibility to explicitly mark individual items as artifacts, so it will instead artifact everything that maps to the criteria in ISO 32000-1:2008, 14.8.2.2.2.Content shall be marked in the structure tree with semantically appropriate tags in a logical reading order.NOTE 4 WCAG 2.0, Guideline 1.4 explains issues regarding contrast, colour and other formatting for accessibility.The user would need to ensure that their document is not subject to these issues. Standard tags defined in ISO 32000-1:2008, 14.8.4, shall not be remapped.Word does not remap the standard tags, although it does introduce other tags that get role-mapped to the standard tags. Documents begin with the Document root element.NOTE 5 Methods used for correcting such errors are dependent on the tools used for processing documents consisting of raster-based images.When Word rasterizes text, it does add ActualText; otherwise, this does not apply.Files claiming conformance with this International Standard shall have a Suspects value of false (ISO 32000-1:2008, Table 321).Word does not have the Suspects entry. This is an optional property.7.2 TextSupported with ExceptionsContent shall be tagged in logical reading order. The most semantically appropriate tag shall be used for each logical element in the document content.Word tags content in logical reading order as much as is feasible.Character codes shall map to Unicode as described in ISO 32000-1:2008, 14.8.2.4.2. Characters not included in the Unicode specification may use the Unicode private use area or declare another character encoding.Natural language shall be declared as discussed in ISO 32000-1:2008, 14.9.2 and/or as described in ISO 32000-1:2008, 7.9.2. Changes in natural language shall be declared. Changes in natural language inside text strings (e.g. inside alternate descriptions) shall be declared using a language identifier as described in ISO 32000-1:2008, 14.9.2.2.The language used for text is identified at the text string level. There is no supported document language property in Word.7.3 GraphicsSupported with ExceptionsGraphics objects, other than text objects, shall be tagged with a Figure tag as described in ISO 32000-1:2008, 14.8.4.5, Table 340. If any of the following exceptions are true, then the graphic shall be tagged as an artifact:— the graphic does not represent meaningful content, or— the graphic appears as a background to a link annotation, in which case, the alternative text on the link shall describe both the graphic and the link.Word tags graphics objects with the Figure tag. A caption accompanying a figure shall be tagged with a Caption tag.Word does not currently tag captions on figures with a Caption tag.Figure tags shall include an alternative representation or replacement text that represents the contents marked with the Figure tag as noted in ISO 32000-1:2008, 14.7.2, Table 323.NOTE 1 See also WCAG 2.0, Guideline 1.1.If text represented in a graphic is not text in a natural language that is meant to be read by a human reader, alternative text describing the nature or purpose of the graphic shall be provided.NOTE 2 Text that is a type sample or a sample of the writing system used by a language are examples of text that is not in a natural language.Word supports alt text on figures, though it is up to the user to add the alt text.Additional note regarding the BBox attribute:Word does not currently have the BBox attribute.A workaround is to manually retag illustrations as new Figures or as Artifacts.7.4 HeadingsSupportedSee subsections for details.7.4.1 GeneralSupportedA conforming document shall use heading tags for all headings as detailed in ISO 32000-1:2008, 14.8.4.3.2.Word supports heading tags (H1-H6) based on the heading style in Word. The T key in ISO 32000-1:2008, 14.7.2, Table 323 should be used to denote document sections.NOTE ‘Chapter 1’ or ‘Bibliography’ are examples of document section headingsWord does not add the T key.7.4.2 Numbered headingsSupportedFor documents that are not strongly structured, as described in ISO 32000-1:2008, 14.8.4.3.5, heading tags shall be used as follows.— If any heading tags are used, H1 shall be the first.— A document may use more than one instance of any specific tag level. For example, a tag level may be repeated if document content requires it.Word will export heading tags with the correct order, even if the user specifies a different heading order (e.g. if the document contains a Heading 2 then a Heading 1 style, the tagging will still be H1 then H2, as required by ISO 14289-1, 7.4.2).7.4.3 Additional headingsSupportedIf a PDF that contains the tags H1, H2, H3, H4, H5, and H6 (in any permissible sequence) requires more headings, tags numbered from H7 upward (without limit) may be defined and used.Word does not define any headings beyond the spec-required H1-H6. 7.4.4 Unnumbered headingsSupportedThe generic heading H (ISO 32000-1:2008, Tables 334 and 335) should be used in strongly structured documents (ISO 32000-1:2008, 14.8.4.3.5). Each node in the tag tree shall contain at most one child H tag.Word handles the creation of H1-H6 tags, so a generic H does not need to be created.7.5 TablesSupported with ExceptionsTables should include headers. Table headers shall be tagged according to ISO 32000-1:2008, Table 337and Table 349.NOTE 1 Tables can contain column headers, row headers or both.NOTE 2 As much information as possible about the structure of tables needs to be available when assistive technology is relied upon. Headers play a key role in providing structural information.It is up to the user to include headers in their tables. Word provides support for row headers and made a recent change such that column headers are defined based on the Header Row checkbox under the Table Styles ribbon chunk rather than the “repeat header rows” setting.Structure elements of type TH shall have a Scope attribute.Word does not include a Scope attribute on TH elements.Table tagging structures shall only be used to tag content presented within logical row and/or column relationships.This is dependent upon how the user has chosen to use tables in their document.7.6 ListsSupported with ExceptionsLists shall be tagged according to ISO 32000-1:2008, 14.8.4.3.3, Table 336 with the following additional provisions.List numbers are not in Lbl or List Label tags. — An explicit ListNumbering attribute shall be used for L tags in ordered lists as specified in ISO 32000-1:2008, 14.8.5.5, Table 347.This is supported by Word.Lists shall only be used when required when the content is intended to be read as a list.This is dependent upon how the user has chosen to use lists in their document.7.7 Mathematical expressionsSupported with ExceptionsAll mathematical expressions shall be enclosed within a Formula tag as detailed in ISO 32000-1:2008, 14.8.4.5 and shall have an Alt attribute.Word does not currently enclose math expressions within a Formula tag.The requirements regarding mapping of characters to Unicode shall apply to mathematical expressions as set forth in ISO 32000-1:2008, 9.10.2 and 14.8.2.4.This is supported by Word.7.8 Page headers and footersSupportedRunning headers and footers shall be identified as Pagination artifacts and shall be classified as either Header or Footer subtypes as per ISO 32000-1:2008, 14.8.2.2.2, Table 330.Headers or Footers are treated as artifacts and tagged as Pagination artifacts.7.9 Notes and referencesSupportedFootnotes, endnotes, note labels and references (cross-references or citations to locations within the document) shall be tagged per ISO 32000-1:2008, 14.8.4.4, Table 338.Word tags footnotes and endnotes; they are role-mapped to Note, which is the standard structure type as specified in ISO 32000-1:2008, 14.8.4.4, Table 338. 7.10 Optional contentNot Applicable7.11 Embedded filesNot Applicable7.12 Article threadsNot Applicable7.13 Digital signaturesSupportedThe appearance of a signature form field as documented in ISO 32000-1:2008, 12.7.4.5 shall meet all other requirements for page content of this specification.Word does not export form fields (including signature form fields).If a portion of the appearance of a signature is represented by a graphic, alternative text shall be provided for that graphic.If you insert a signature block in Word and export it, the resulting rasterized version of the signature does have alt text.7.14 Non-interactive formsNot Applicable7.15 XFANot Applicable7.16 SecuritySupported7.17 NavigationSupportedA document should include a document outline that matches the reading order and level of navigational targets (ISO 32000-1:2008, 12.3.3).Word supports making headings into bookmarks to make an outline, but the user must select this option. Word can also export its native bookmarks as bookmarks in the PDF if the user elects to do so.If present, the entries in the PageLabels number tree (ISO 32000-1:2008, 7.7.2, Table 28) should be semantically appropriate.Word includes a PageLabels number tree with semantically appropriate entries.7.18 AnnotationsSupported7.18.1 GeneralSupportedWord does not export anything with an ILSE type Annot except for links, which are a special case (see 7.18.5). Word specifies “Annotation” as the tag name for comments, but it is role mapped to type Sect instead.7.18.2 Annotation typesSupportedWord does not do TrapNet annotations, and only uses standard subtypes.7.18.3 Tab orderSupportedWord includes the Tabs key in the page dictionary and sets the value to S.7.18.4 FormsNot Applicable7.18.5 LinksSupported7.18.6 MediaNot Applicable7.18.6.1 GeneralNot Applicable7.18.6.2 Media clip dataNot Applicable7.18.7 File attachmentsNot Applicable7.18.8 PrinterMarkNot Applicable7.19 ActionsNot Applicable7.20 XObjectsSupportedReference XObjects, as noted in ISO 32000-1:2008, 8.10.4, shall not be used in conforming PDF/UA files.Word does not support reference XObjects.7.21 FontsSupported7.21.1 GeneralSupported7.21.2 Font typesSupported7.21.3 Composite fontsSupported7.21.3.1 GeneralSupported7.21 3.2 CIDFontsSupported7.21.3.3 CMapsSupported7.21.4 EmbeddingSupported7.21.4.1 GeneralSupported with ExceptionsIn order for all the fonts to be embedded, the user must select “PDF/A” when saving as PDF.7.21.4.2 Subset embeddingSupported7.21.5 Font metricsSupported7.21.6 Character encodingsSupported7.21.7 Unicode character mapsSupported7.21.8 Use of .notdef glyphSupported8. Conforming reader requirementsNot Applicable9. AT requirementsNot ApplicableDisclaimer? 2017 Microsoft Corporation. All rights reserved. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Microsoft cannot guarantee the accuracy of any information presented after the date of publication. Microsoft regularly updates its websites with new information about the accessibility of products as that information becomes available.Customization of the product voids this conformance statement from Microsoft. Please consult with Assistive Technology (AT) vendors for compatibility specifications of specific AT products. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download