I see what you are saying about the page reflow for details which explains
the concern over pagination.
Regarding a context switch, if you go to another URL presumably you are
going to jump to a new tab or you are going to launch a new window. Escape
does not close those. I don't think the back button is guaranteed to go
right back to the same location where you left off in the document. I also
don't like the user having to hit the back button to go back an entire
page.
Rich
Rich Schwerdtfeger
From: Daniel Weck <daniel.weck@gmail.com>
To: "White, Jason J" <jjwhite@ets.org>
Cc: Ivan Herman <ivan@w3.org>, Janina Sajka <janina@rednote.net>,
Richard Schwerdtfeger/Austin/IBM@IBMUS, Avneesh Singh
<avneesh.sg@gmail.com>, Charles LaPierre
<charlesl@benetech.org>, Juan Corona <juanc@evidentpoint.com>,
George Kerscher <kerscher@montana.com>, "DPUB mailing list
(public-digipub-ig@w3.org)" <public-digipub-ig@w3.org>, "PF
(public-pfwg@w3.org)" <public-pfwg@w3.org>, Ric Wright
<rkwright@geofx.com>, "Siegman, Tzviya - Hoboken"
<tsiegman@wiley.com>, Zheng Xu <zxu@kobo.com>
Date: 11/10/2015 12:36 PM
Subject: Re: Proposal: remove aria-describedat from the ARIA 1.1
specification
On Tue, Nov 10, 2015 at 6:10 PM, White, Jason J <jjwhite@ets.org> wrote:
> I also support Rich in encouraging implementation of details/summary.
And for the record: I do too ... as much as figure/figcaption, or any
other markup container that is capable of carrying adequate semantics
via @role, etc. and compatible with usage of a Media Query to
determine its hidden/displayed state.
Where I disagree is in the use of iframes to embed long descriptions
(ancillary files) directly within the primary reading flow.
Rationale detailed here:
https://lists.w3.org/Archives/Public/public-digipub-ig/2015Nov/0033.html
https://lists.w3.org/Archives/Public/public-digipub-ig/2015Nov/0055.html
Regards,
Daniel
