- From: Deborah Kaplan <dkaplan@safaribooksonline.com>
- Date: Fri, 28 Aug 2015 12:02:31 -0400
- To: Charles LaPierre <charlesl@benetech.org>
- Cc: Tzviya - Hoboken Siegman <tsiegman@wiley.com>, "public-dpub-accessibility@w3.org" <public-dpub-accessibility@w3.org>
- Message-ID: <CANSiVPYNjVctSv6XB8pLha4S2SumZgHrG2girn73mUXgkiG_4Q@mail.gmail.com>
Comments on the table: longdesc:mitigation:: Could be extended to cover more elements beyond <img> (eg. "All block-level elements.") aria-describedby:cons:: No standard way to hide visually but expose on demand or to AT. (Can hide but expose to screen-readers, can expose, or can right custom JS tools.) hidden iFrame; figure with iframe:cons:: iFrames can require implementer effort to make accessible. All three figure + details options:cons:: Doesn't inherently clarify that this figcaption is the accessibility description as oopposed to a general captopn. All three figure + details options; hidden iframe:cons:: "special support" and "depend on script-support long term" are unclear: all three of these should just say, "will require scripting to hide visually but expose on demand or to AT." All three figure + details options:mitigation:: Add a role attribute which AT, extensions, or user agent settings could recognize to expose as appropriate. All three figure + details options:mitigation:: Add the "Add role attribute to clarify overloading" to all of them. All three figure + details options:mitigation:: Add a role attribute which AT, extensions, or user agent settings could recognize to expose as appropriate. SVG wrapping bitmap:cons:: Using SVG as a wrapper for non-graphics overloads a graphical format as a descriptor container. On Fri, Aug 28, 2015 at 9:31 AM, Charles LaPierre <charlesl@benetech.org> wrote: > I read this over and think its very good. Here are my comments. > > > I would add a con to ARIA-describedby is that it can not link to documents > outside the primary document. And as a Workaround add you can get around > this issue by placing hidden iFrames with links outside the document but > this is a hack to say the least :) > > The one thing I would add to "figure with details and embedded iFrame" > as a con would be “This seems too complex for easy use” come on 4 levels > deep of this containing that which contains … > > For SVG, I just don’t get this, if I have a table why am I adding an SVG > so I can add alternate descriptions. > > I thought there was talk about media query? I don’t see that. > > Thats about it for me. > _______________________________ > > Charles LaPierre > charlesl@benetech.org > > > > > On Aug 28, 2015, at 6:10 AM, Siegman, Tzviya - Hoboken <tsiegman@wiley.com> > wrote: > > Reminder: If we have any feedback for PF on the extended descriptions > analysis grid [1], we should put it together within the next few days. > > [1] http://www.w3.org/2015/08/extended-description-analysis > > *Tzviya Siegman* > Digital Book Standards & Capabilities Lead > Wiley > 201-748-6884 > tsiegman@wiley.com > > *From:* Charles LaPierre [mailto:charlesl@benetech.org > <charlesl@benetech.org>] > *Sent:* Thursday, August 27, 2015 5:25 PM > *To:* public-dpub-accessibility@w3.org > *Subject:* Tomorrows A11Y DPUB Meeting > > Agenda Friday August 28st > > 1. Update on PF/ARIA describedAt meeting this week (George / Tzviya ??) > 2. Update from Diagram meeting (Charles / George alternatives to > ARIA.describedAt) > 3. Update from BISG meeting (Charles - MathMl recommendation) > 4. A11Y Note status / blockers / progress > 5. TPAC possible meetings / who is attending > 6. Honorable Mentions : Diagram Award > > When: Friday at 8AM PDT / 11AM EDT > > Join WebEx meeting > Meeting number: 642 567 899 <//642%20567%20899> > *Dial in: +1-617-324-0000 <//Dial%20in:%20+1-617-324-0000>* > Direct access: > > *https://mit.webex.com/mit/j.php?MTID=me61494d75b248018777b1bbf0b87dd3b > <https://mit.webex.com/mit/j.php?MTID=me61494d75b248018777b1bbf0b87dd3b>* > > > _______________________________ > > Charles LaPierre > charlesl@benetech.org > > >
Received on Friday, 28 August 2015 16:03:04 UTC