PDFUA-234: Decorative content not marked as artifact

[zakkinsey]

Jira issue originally created by user @BPeboeck:

This describes a failure condition in which decorative content is not marked as an artifact.

[zakkinsey]

Comment created by @PaulRayius:

Working on metadata, I included, from WCAG, 4.1.1.  I think it's a stretch but because of the part about requiring "complete start and end tags" - and the item in question, in this example, is neither tagged nor marked as an artifact.  I took that to, somewhat, align with "not having complete start and end tags." 

[zakkinsey]

Comment created by @unknown-jira-user-2:

I suggest including WCAG 1.1.1 and have added it since the metadata is still subject to review. Among other things, WCAG 1.1.1 says: {quote} Decoration, Formatting, Invisible If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by assistive technology. {quote}

Since 32k-1, 14.8.2.2.2 says, "An artifact shall be explicitly distinguished from real content by enclosing it in a marked-content sequence with the tag Artifact...", then content that is neither in the structure tree nor marked as an artifact has not been correctly "implemented in a way that it can be ignored by assistive technology."

[zakkinsey]

Comment created by @PaulRayius:

I agree with William's comment, above. 

[zakkinsey]

Comment created by @MarkusErle:

We decided in the group reviewing not to refer to 4.1.1. It seems too stretched to us.

[zakkinsey]

Comment created by @unknown-jira-user-7:

7.21.4.2 requires that if CIDSet is present, it lists all the glyphs. Replacing with a version that does.

[zakkinsey]

Comment created by @PaulRayius:

I found the testing results, as compared to the Description, confusing until I dug deeper.  People looking at this as the "surface" level would see that the blue background has been untagged and may immediately assume it's been "artifacted" because of that.  The issue, however, is really that the untagged Path is not in an Artifact container.  I think the Description might serve our audience better if we indicate that - the "real" issue is that the Path is not in an Artifact container. 

[zakkinsey]

Comment created by @unknown-jira-user-7:

The failure we see is "untagged content" - ie. there's content that is not real content and not an artifact. So same issue identified by Paul in the comment immediately above.