forked from w3c/wcag
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
4f91b8c
commit e0c2bb3
Showing
1 changed file
with
62 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,62 @@ | ||
| <?xml version="1.0" encoding="UTF-8"?> | ||
| <!DOCTYPE technique | ||
| SYSTEM "../../xmlspec.dtd"> | ||
| <technique id="F93"> | ||
| <short-name>Failure of Success Criterion 1.3.1 due to information in PDF headers and footers, marked as artifacts, not being programmatically determinable in another way</short-name> | ||
| <applicability> | ||
| <p>PDF</p> | ||
| </applicability> | ||
| <applies-to> | ||
| <success-criterion idref="content-structure-separation-programmatic" relationship="failure"/> | ||
| </applies-to> | ||
| <description> | ||
| <p>This failure occurs when information in a header or footer is not available to people who are blind using screen readers. If this information is marked as an artifact and not provided in another way to these users, then they may be disadvantaged by not having this information. Many authors mark up footers as artifacts to prevent the document from being overly "chatty" or interupting to flow of a sentence when the footer is read at the bottom of the page in the middle of the sentence. If authors do this, they must provide ALL the information in the footer in another way that can be read by screen readers, such as providing author information and date on the title page of the document and/or ensuring the PDF page numbers reflect the footer page numbers etc.</p> | ||
| </description> | ||
| <examples> | ||
| <eg-group> | ||
| <head>Page numbers in the footer not being confused with the PDF page number</head> | ||
| <description> | ||
| <p>In this example, the footer information is marked as an artifact and is not read by a screen reader, but the pages in Acrobat do not acurately reflect them [insert screen shot of Acrobat page number different than footer page number]</p> | ||
| </description> | ||
| </eg-group> | ||
| <eg-group> | ||
| <head>more examples</head> | ||
| <description> | ||
| <p>more text</p> | ||
| </description> | ||
| </eg-group> | ||
| </examples> | ||
| <resources> | ||
| <see-also> | ||
| <ulist> | ||
| <item> | ||
| <p> | ||
| <loc xmlns:xlink="http://www.w3.org/1999/xlink" href="http://www.w3.org/TR/WCAG20-TECHS/PDF17.html">Specifying consistent page numbering for PDF documents</loc> | ||
| </p> | ||
| </item> | ||
|
|
||
| </ulist> | ||
| </see-also> | ||
| </resources> | ||
| <related-techniques/> | ||
| <tests> | ||
| <procedure> | ||
| <olist> | ||
| <item> | ||
| <p>Check if the headers and/or footers is marked as an artifact.</p> | ||
| </item> | ||
| <item> | ||
| <p>Check on whether the information in the headers and/or footers is NOT available in text or in some other programatic way in the document. (i.e., on title page, in prose in the main body, PDF pages match header/footer page numbers etc.)</p> | ||
| </item> | ||
|
|
||
| </olist> | ||
| </procedure> | ||
| <expected-results> | ||
| <ulist> | ||
| <item> | ||
| <p>If checks 1-2 are true, then this failure condition applies and the content fails the Success Criterion.</p> | ||
| </item> | ||
| </ulist> | ||
| </expected-results> | ||
| </tests> | ||
| </technique> |
e0c2bb3There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
David, Maybe you should reference PDF 14 and PDF17 techniques.
I agree that it may not be the best user experience when a sentence is interrupted with footer text at the end of the page.
But is that not how it is for everyone? A sighted user turns the page.
An SR user will realize he has hit the end of the page and advance to the next page if he has selected 'single page' view.
On the other hand, if he has selected 'continuous' option, he may not realize the page has ended.
So I am not in favor of making footer text into an artefact. PDF17 explains the difference between actual page# and what is stated in the footer.
Maybe you may want to point to PDF14 and PDF17 or say how one can make footer text PD.
e0c2bb3There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Related techniques to PDF 14 and PDF17 will be added.
e0c2bb3There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
David to make clear that clear one would verify that the footers are artifacted in the document - based on @Awks comment