RE: Running headers/footers / new version of DPUB-ARIA?

Hi,
 
Anybody else hate this idea?
 
It seems to get us stuck with fixed page sizes instead of reflow. How would this work with reflowed pages? Would this show up in the middle of the display?
 
I need to understand how this would work; I need to be convinced, and I do have an open mind.
 
Best
George
 
 
 
From: Aaron Leventhal <aleventhal@google.com> 
Sent: Wednesday, August 21, 2019 6:55 AM
To: White, Jason J <jjwhite@ets.org>
Cc: Leonard Rosenthol <lrosenth@adobe.com>; George Kerscher <kerscher@montana.com>; public-publ-wg@w3.org; Joanmarie Diggs <jdiggs@igalia.com>
Subject: Re: Running headers/footers / new version of DPUB-ARIA?
 
Sounds good. 
- How about doc-pageheader and doc-pagefooter?
- Possible definition: repeated section of text that appears at the top/bottom of pages in a document, potentially containing a title, page number or other information
- Should the page number get its own role, e.g. doc-pagenum? Should it exist within the doc-pageheader/doc-page-footer?
- Should the new roles inherit from contentinfo?
 
On Wed, Aug 21, 2019 at 8:05 AM White, Jason J <jjwhite@ets.org <mailto:jjwhite@ets.org> > wrote:
If there’s already a mapping to accessibility APIs via PDF readers, then we could use it here too.
 
Screen readers could offer a command to query this information, if desired, just as there is for window titles.
 
From: Leonard Rosenthol <lrosenth@adobe.com <mailto:lrosenth@adobe.com> >
Date: Tuesday, August 20, 2019 at 21:45
To: George Kerscher <kerscher@montana.com <mailto:kerscher@montana.com> >, 'Aaron Leventhal' <aleventhal@google.com <mailto:aleventhal@google.com> >, "public-publ-wg@w3.org <mailto:public-publ-wg@w3.org> " <public-publ-wg@w3.org <mailto:public-publ-wg@w3.org> >
Cc: 'Joanmarie Diggs' <jdiggs@igalia.com <mailto:jdiggs@igalia.com> >
Subject: Re: Running headers/footers / new version of DPUB-ARIA?
Resent-From: <public-publ-wg@w3.org <mailto:public-publ-wg@w3.org> >
Resent-Date: Tuesday, August 20, 2019 at 21:45
 
FWIW: Headers & Footers can be properly identified in PDFs and exposed accordingly to AT (so that they aren’t read multiple times).  In fact, PDF/UA (the PDF standard for Universal Accessibility) calls out their usage.
 
Leonard
 
From: "kerscher@montana.com <mailto:kerscher@montana.com> " <kerscher@montana.com <mailto:kerscher@montana.com> >
Date: Tuesday, August 20, 2019 at 4:35 PM
To: 'Aaron Leventhal' <aleventhal@google.com <mailto:aleventhal@google.com> >, "public-publ-wg@w3.org <mailto:public-publ-wg@w3.org> " <public-publ-wg@w3.org <mailto:public-publ-wg@w3.org> >
Cc: 'Joanmarie Diggs' <jdiggs@igalia.com <mailto:jdiggs@igalia.com> >
Subject: RE: Running headers/footers / new version of DPUB-ARIA?
Resent-From: <public-publ-wg@w3.org <mailto:public-publ-wg@w3.org> >
Resent-Date: Tuesday, August 20, 2019 at 4:35 PM
 
Hello,
 
This is just my opinion. Running headers and footers are very intrusive while reading. I encounter these many times in PDF documents. The same information is constantly repeated. Fortunately, I do not encounter this while reading EPUB. I can understand that it might be useful for the Reading System to provide “where am I?” information as one is reading, but including this over-and-over again in the content would be horrible.
I am reading using Assistive Technology (AT) and the TTS reads to me. I imagine this would also be painful if a person was using the read aloud function in Reading Systems.
 
I could see the same problem in an audio book. Nobody would want to hear those running heads and footers in the audio book.
 
My $.02
 
Best
George
 
Best
George
 
 
From: Aaron Leventhal <aleventhal@google.com <mailto:aleventhal@google.com> > 
Sent: Tuesday, August 20, 2019 11:37 AM
To: public-publ-wg@w3.org <mailto:public-publ-wg@w3.org> 
Cc: Joanmarie Diggs <jdiggs@igalia.com <mailto:jdiggs@igalia.com> >
Subject: Running headers/footers / new version of DPUB-ARIA?
 
Hi all,
 
I'm wondering about the plans for doing DPUB-ARIA 2.0 as described under the deliverables:
https://www.w3.org/2017/04/publ-wg-charter/#deliverables <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2017%2F04%2Fpubl-wg-charter%2F%23deliverables&data=02%7C01%7Cjjwhite%40ets.org%7C7e4c7b9724114d918a4408d725d93e36%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637019487312874610&sdata=9H73bI8vtn9JbDPnqYieMNjeAJYIbIGMpjbab1CdqyA%3D&reserved=0> 
 
Thanks for what DPUB-ARIA provides so far. Google Docs is going to be using it  to expose semantics for online word processing. We're collaborating with AT vendors and other developers of online word processors as well.
 
One gap is running headers and footers: https://github.com/w3c/dpub-aria/issues/10 <https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fdpub-aria%2Fissues%2F10&data=02%7C01%7Cjjwhite%40ets.org%7C7e4c7b9724114d918a4408d725d93e36%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637019487312884609&sdata=6xRJGvSpHdV0dzzUI%2BBIM8L6dPMj%2FqtpFsFrsPdOV3Y%3D&reserved=0>  -- hence the reason for my email and status check :)
 
Thanks for any info,
Aaron
 
 
  _____  

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.
 
Thank you for your compliance.
  _____