- From: David MacDonald <david100@sympatico.ca>
- Date: Wed, 10 Jun 2015 21:25:34 -0400
- To: Jonathan Avila <jon.avila@ssbbartgroup.com>
- CC: WCAG <w3c-wai-gl@w3.org>
- Message-ID: <BLU436-SMTP25795E7AA5C7F6AEF425A8CFEBC0@phx.gbl>
Jonathan comment: >For example, some footers contain links – links can never be artifacts. David Response: I put a link in a MS Word footer, and exported it. It appears to be marked as an artifact, even though it can receive tab focus. I have a screen shot at the bottom of the discussion article here: http://davidmacd.com/blog/pdf-headers-footers.html Perhaps information can be added in meta data or added to the tag tree in acrobat when the original is not available. This would allow us to cordinate with 7.8 of PDF/UA Cheers, David MacDonald *Can**Adapt* *Solutions Inc.* Tel: 613.235.4902 LinkedIn <http://www.linkedin.com/in/davidmacdonald100> www.Can-Adapt.com * Adapting the web to all users* * Including those with disabilities* If you are not the intended recipient, please review our privacy policy <http://www.davidmacd.com/disclaimer.html> On Wed, Jun 10, 2015 at 12:02 PM, Jonathan Avila <jon.avila@ssbbartgroup.com > wrote: > David, I agree the page label feature is the appropriate place for > non-ordinal or non-contiguous page numbers – so PDF 17 is the way to go for > that. The issue is that stating headings and footers should be artifacts > is not so simple. For example, some footers contain links – links can > never be artifacts. So you are forced to tag them or remove the link. > Many people who are remediating PDFs also don’t have access to change the > document so we run into situations where those remediating may not be able > to change the section names of the document. > > > > Jonathan > > > > -- > Jonathan Avila > Chief Accessibility Officer > SSB BART Group > jon.avila@ssbbartgroup.com > > Phone 703.637.8957 > Follow us: Facebook <http://www.facebook.com/#!/ssbbartgroup> | Twitter > <http://twitter.com/#!/SSBBARTGroup> | LinkedIn > <http://www.linkedin.com/company/355266?trk=tyah> | Blog > <http://www.ssbbartgroup.com/blog> | Newsletter <http://eepurl.com/O5DP> > > > > *From:* David MacDonald [mailto:david100@sympatico.ca] > *Sent:* Tuesday, June 09, 2015 4:13 PM > *To:* WCAG > *Subject:* Re: Should PDF documents have headers and footers on every > page? > > > > I have compared what PDF/UA with WCAG say about headers and footers and > have written up a small report and recommendations on how I think we should > proceed with Headers and Footers in PDF documents. > > http://davidmacd.com/blog/pdf-headers-footers.html > > I think PDF14 requires an update quickly. I could take an action item to > propose the rewrite. > > > > > Cheers, > > David MacDonald > > > > *CanAdapt* *Solutions Inc.* > > Tel: 613.235.4902 > > LinkedIn <http://www.linkedin.com/in/davidmacdonald100> > > www.Can-Adapt.com > > > > * Adapting the web to all users* > > * Including those with disabilities* > > > > If you are not the intended recipient, please review our privacy policy > <http://www.davidmacd.com/disclaimer.html> > > > > On Mon, May 18, 2015 at 9:54 PM, Jonathan Avila < > jon.avila@ssbbartgroup.com> wrote: > > David, there are some good but very specific reasons to not artifact > header and footer information. Otherwise running headers and footer should > be made pagination artifacts and the Page Labels feature should be used to > add Page numbering including section information to identify pages and > sections to assistive technology. The page label feature is pretty > powerful and allows flexibility for different number schemes such as Roman > numbers and custom label prefixes. > > > > Some instances of header and footer information that might be useful > include classification information on classified documents, copyright > information, form numbers, or other content that is not located elsewhere > in the document. In general I recommend marking that content as > non-artifact content on the first and last page so it does not break up the > reading order of content. > > > > Best Regards, > > > > Jonathan > > > > -- > Jonathan Avila > Chief Accessibility Officer > SSB BART Group > jon.avila@ssbbartgroup.com > > > > 703-637-8957 (o) > Follow us: Facebook <http://www.facebook.com/#%21/ssbbartgroup> | Twitter > <http://twitter.com/#%21/SSBBARTGroup> | LinkedIn > <http://www.linkedin.com/company/355266?trk=tyah> | Blog > <http://www.ssbbartgroup.com/blog> | Newsletter <http://eepurl.com/O5DP> > > > > *From:* David MacDonald [mailto:david100@sympatico.ca] > *Sent:* Monday, May 18, 2015 2:50 PM > *To:* WCAG > *Subject:* Should PDF documents have headers and footers on every page? > > > > > > We have a technique for Creating PDF headers and footers, usually inserted > using the source program such as MS Word Headers and Footers. See PDF14. > > http://www.w3.org/TR/WCAG20-TECHS/PDF14.html > This causes the screen reader to announce these Headers and footers at the > top and bottom of every page. Sometimes the interrupt reading halfway > through a sentence that continues on the following page. I can imagine this > is quite annoying for screen reader users tp have to listen through a > header and a footer between every page. > > Visually we just skip over it... Usually most of the information found in > the header and footer is available on the home page of the document or some > other prominent place. > > What is useful is page numbers. However, if the author syncs the page > numbering of the PDF with the document large numbers using PDF17, it makes > me wonder if we should advise the author to mark headers and footers as > artifacts instead... > > An organization that teaches PDF, which is fairly well known, and has done > work for Adobe teaches to turn these headers and footers into artifacts so > they will be ignored by a screen reader. > > I propose we place a note on PDF14 saying something like this: > > "If the page numbering has been synchronized as in PDF17 and other header > and footer information is available in a prominent place in the document > such as a heading or home page, then headers and footers are not necessary > and can be marked up as artifacts..." > > Cheers, > > David MacDonald > > > > *CanAdapt* *Solutions Inc.* > > Tel: 613.235.4902 > > LinkedIn <http://www.linkedin.com/in/davidmacdonald100> > > www.Can-Adapt.com > > > > * Adapting the web to all users* > > * Including those with disabilities* > > > > If you are not the intended recipient, please review our privacy policy > <http://www.davidmacd.com/disclaimer.html> > > >
Received on Thursday, 11 June 2015 01:26:13 UTC