RE: DPUB ARIA Questions

>> Accessible name and description should not participate in the DPUB AAM as you are not introducing attributes or native host language features that effect name computation. PS this is a copy and paste leftover form SVG

> TS: I don’t remember at this point. Matt, do you remember how we determined this? 

 

Sorry, this is all Greek to me. I haven't looked at the source of that document, but if you tell me what needs fixing I can look into it.

 

> I can see the case being made to make the following roles subclass “contentinfo”. I am interested in feedback:

> doc-acknowledgments

> doc-credits

> doc-abstract (currently subclasses section)

 

It's hard to say from the description. I guess the corollary for contentinfo as exemplified is the information on the titlepage verso. But maybe if you take a broader view that it's any material that describes the content instead of being the content, acknowledgements and credits would fit. I'm not sure how to place an abstract, as it's preliminary material that summarizes the content.

 

Matt

 

From: Siegman, Tzviya - Hoboken [mailto:tsiegman@wiley.com] 
Sent: July 14, 2016 9:43 AM
To: Rich Schwerdtfeger <richschwer@gmail.com>
Cc: W3C PF - DPUB Joint Task Force <public-dpub-aria@w3.org>; Matt Garrish <mgarrish@gmail.com>
Subject: RE: DPUB ARIA Questions

 

Hi Rich,

 

I have some follow up questions, inline below.

 

Thanks,

Tzviya

 

Tzviya Siegman

Information Standards Lead

Wiley

201-748-6884

tsiegman@wiley.com <mailto:tsiegman@wiley.com>  

 

From: Rich Schwerdtfeger [mailto:richschwer@gmail.com] 
Sent: Wednesday, July 13, 2016 6:43 PM
To: Siegman, Tzviya - Hoboken
Cc: W3C PF - DPUB Joint Task Force
Subject: DPUB ARIA Questions

 

We are trying to clean up DPUB ARIA and DPUB AAM

 

Just so that we are on the same page:

 

1.     roles that subclass role “none” are not mapped. However, I think these should subclass section and just not be mapped.

TS: The only role that subclasses “none” is role =”doc-pullquote”. The intent is for AT to skip this element. Is your recommendation still to subclass section? The explicit direction should be for AT to skip the element.

2.     Accessible name and description should not participate in the DPUB AAM as you are not introducing attributes or native host language features that effect name computation. PS this is a copy and paste leftover form SVG

TS: I don’t remember at this point. Matt, do you remember how we determined this? 

3. Should any of the DPUB ARIA landmarks subclass role “contentinfo” vs. “landmark”?

            TS: We intentionally excluded metadata elements from this vocabulary. However, I can see the case being made to make the following roles subclass “contentinfo”. I am interested in feedback:

doc-acknowledgments

doc-credits

doc-abstract (currently subclasses section)

 

Rich

 

 

 

Rich Schwerdtfeger