RE: Tomorrows A11Y DPUB Meeting

HI Charles,

We ruled out describedby for other reasons (Doesn't allow extended markup.) in the requirements document we originally submitted [1]

I am rather hesitant to add requirements at this stage. Is the ability to link out indeed a requirement or is this covered by the following:

1.    Access to description content:
1.   Description content should not viewable in browser chrome.
2.   The description content should, by default, be invisible on the page.
3.   Description content should be made available to user through AT.
4.   There should be an option to display description content on page on demand.
This is a non-specific requirement that does not specify where the description is held.

[1] http://www.w3.org/dpub/IG/wiki/Publisher_requirements_for_extended_descriptions


Tzviya Siegman
Digital Book Standards & Capabilities Lead
Wiley
201-748-6884
tsiegman@wiley.com<mailto:tsiegman@wiley.com>

From: Charles LaPierre [mailto:charlesl@benetech.org]
Sent: Monday, August 31, 2015 10:42 AM
To: Siegman, Tzviya - Hoboken
Cc: Deborah Kaplan; public-dpub-accessibility@w3.org
Subject: Re: Tomorrows A11Y DPUB Meeting

I would think its a requirement otherwise we could use aria.describedby to link internally.

_______________________________

Charles LaPierre
charlesl@benetech.org<mailto:charlesl@benetech.org>



On Aug 31, 2015, at 7:16 AM, Siegman, Tzviya - Hoboken <tsiegman@wiley.com<mailto:tsiegman@wiley.com>> wrote:

HI All,

I’m pulling this feedback together and I have a few questions.

Charles, is linking to an external document a requirement or a “nice to have”? We did not mention this anywhere in our requirements document [1]

[1]  http://www.w3.org/dpub/IG/wiki/Publisher_requirements_for_extended_descriptions


Thanks

Tzviya Siegman
Digital Book Standards & Capabilities Lead
Wiley
201-748-6884
tsiegman@wiley.com<mailto:tsiegman@wiley.com>

From: Deborah Kaplan [mailto:dkaplan@safaribooksonline.com]
Sent: Friday, August 28, 2015 12:03 PM
To: Charles LaPierre
Cc: Siegman, Tzviya - Hoboken; public-dpub-accessibility@w3.org<mailto:public-dpub-accessibility@w3.org>
Subject: Re: Tomorrows A11Y DPUB Meeting

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<mailto: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<mailto:charlesl@benetech.org>



On Aug 28, 2015, at 6:10 AM, Siegman, Tzviya - Hoboken <tsiegman@wiley.com<mailto: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<mailto:tsiegman@wiley.com>

From: Charles LaPierre [mailto:charlesl@benetech.org]
Sent: Thursday, August 27, 2015 5:25 PM
To: public-dpub-accessibility@w3.org<mailto: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<tel://642%20567%20899>
Dial in: +1-617-324-0000<tel://Dial%20in:%20+1-617-324-0000>
Direct access:

https://mit.webex.com/mit/j.php?MTID=me61494d75b248018777b1bbf0b87dd3b



_______________________________

Charles LaPierre
charlesl@benetech.org<mailto:charlesl@benetech.org>