PDF Results

Axe Monitor can test PDFs for accessibility issues. These are automated accessibility checks. Manual checks are also required.

WCAG 2.0 Level A & AA Rules

Success Criterion	Issue Description	Impact
1.1.1	Images/Figures in PDF documents must have alternate text	Critical
1.3.1	Relevant table elements, properties, and associations must be utilized for data tables	Critical
1.3.1	Heading content must be tagged with a heading tag and level	Serious
1.3.1	Interactive form controls must have Labels/Tooltips associated	Critical
1.3.1	Appropriate and relevant list tags must be used to tag list content	Serious
1.3.1	Document must not contain untagged elements	Critical
2.1.1	Links must be tagged with Link tags with appropriate text object association	Critical
2.4.2	Document title must be provided	Serious
2.4.4	Links in PDF documents must have alternate replacement text	Moderate
3.1.1	Language definition in document Catalog	Serious
3.1.2	Language for passages or phrases must be specified where it does not match with the document language	Serious
3.3.2	Required fields must be identified both visually and programmatically	Serious
4.1.2	Form fields in PDF documents must include their name, role, state, and value information	Critical

WCAG 2.0 Best Practices

Success Criterion	Issue Description	Impact
2.4.5	Bookmarks should be utilized in long documents	Moderate

PDF/UA Standards

Success Criterion	Issue Description	Impact
1:7.1-11	For a document that has correct reading order, the Suspects key must not be set to True	Critical
1:7.1-8	Document must contain an XMP metadata stream	Serious
1:5	XMP metadata stream in the Catalog dictionary must include the PDF/UA identifier	Critical
1:7.1-8	XMP metadata stream must contain dc:title	Serious
1:7.1-9	ViewerPreferences dictionary of the Catalog dictionary must contain a DisplayDocTitle key	Serious
1:7.1-9	ViewerPreferences dictionary of the Catalog dictionary must contain a DisplayDocTitle key that has an appropriate value that is not false	Serious
1:7.2-3	Natural language for document metadata must be specified	Serious
1:7.4.2-1	First heading tag for the document must be <H1>	Serious
1:7.4-1	Heading levels must be used in the correct order and are not skipped	Serious
1:7.4.4-3	Document must not use both <H> and <H#> tags	Critical
1:7.1-1	Content marked as Artifact must not be present inside tagged content	Critical
1:7.1-1	Tagged content must not be present inside content marked as Artifact	Critical
1:7.1-2	Content must be either marked as Artifact or tagged as real content	Critical
1:7.2-1	Table-related structure element must conform to the syntax defined in ISO 32000-1, Table 337	Critical
1:7.2-1	List-related structure element must conform to Table 336 in ISO 32000-1	Serious
1:7.2-1	A TOC-related structure element must conform to Table 333 in ISO 32000-1	Critical
1:7.2-1	A Ruby-related structure element must conform to Table 338 in ISO 32000-1	Critical
1:7.2-1	A Warichu-related structure element must conform to Table 338 in ISO 32000-1	Critical
1:7.2-3	Natural language for text in page content must be specified	Critical
1:7.2-3	Natural language for text in Alt, ActualText and E attributes must be specified	Serious
1:7.2-3	Natural language in the Contents entry for annotations must be specified	Serious
7.3-3	<Figure> tag alternative or replacement text must be present	Critical
7.4.4-1	Nodes must not contain more than one <H> tag	Critical
7.7-1	<Formula> tag must contain an Alt attribute	Critical
1:7.7-2	Unicode mapping requirements must be met	Serious
1:7.18.1-4	An annotation other than Link, Widget, or Popup and does not have a Contents key must have an alternative description	Critical
1:7.18.1-4	A hidden form field that does not have a TU key must have an alternative description in the enclosing structure element	Critical
1:7.18.5-2	A link annotation must include an alternate description in its Contents entry	Critical
1:7.21.4.1-1	A font used by text in the document must be embedded in the document	Serious