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

To the best of my knowledge, disclosure of significant information that happens to be in CSS properties via accessibility APIs is still an open question between the APA Working Group and CSS. My understanding  ay be out of date, though.

It should be noted that I’m somewhat inclined toward an ARIA-based solution for the reasons that Aaron gives.

From: Aaron Leventhal <aleventhal@google.com>
Date: Tuesday, August 20, 2019 at 16:48
To: "White, Jason J" <jjwhite@ets.org>
Cc: George Kerscher <kerscher@montana.com>, "public-publ-wg@w3.org" <public-publ-wg@w3.org>, Joanmarie Diggs <jdiggs@igalia.com>
Subject: Re: Running headers/footers / new version of DPUB-ARIA?

Jason, that's certainly something for us to look into.
That said, we're very likely going to be using AOM, in which case CSS won't help us.

On Tue, Aug 20, 2019 at 4:42 PM White, Jason J <jjwhite@ets.org<mailto:jjwhite@ets.org>> wrote:
In the context of an editor/word processor, though, which gave rise to the question, one does need to be able to access header and footer information for reading or modification.

It’s interesting that CSS Paged Media provides for headers and footers, but (even if present in the CSS), I assume this is unlikely to be disclosed to assistive technologies. The examples in the CSS Paged Media module suggest the header/footer text would appear in the CSS properties after interpretation by the UA. I don’t know what the browser implementation status is of these properties, and, in any case, not every word processor-like application can be expected to use them.

Thus, I think making provision for it in the ARIA digital publishing module is a reasonable request.

From: George Kerscher <kerscher@montana.com<mailto:kerscher@montana.com>>
Date: Tuesday, August 20, 2019 at 16:35
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 16:35

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%7Cd373469c763242fb039708d725afbad6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637019309018391555&sdata=M%2FEx2%2BBkmEnUs%2BZPrSQAANEl8C8BhDpeg9lxIBQHzhk%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%7Cd373469c763242fb039708d725afbad6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637019309018401550&sdata=p8uCdaioxItmHM6OktjX9ruqZ7k0AkaRCFkI2XAH8%2Bg%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.

________________________________

________________________________

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.

________________________________