DPUB-ARIA Weekly Meeting

11 Aug 2016


See also: IRC log


Janina, Rich, Matt, Ivan, MichaelC, ShaneM


<Rich> I am connected on webex

<scribe> scribe: tzviya

rich: In mappings there is landmark role
... this is pulled into DPUB AAM
... There are additional updates to DPUB AAM from Core AAM. I need to add some additional updates. When i push them, i'll send them out.
... ARIA will meet with the TAG on Friday at TPAC
... what are DPUB
... 's needs for extensibility?

Tzviya: We want to make sure that we can extend our vocabulary easily without roadblocks. We don't want our vocabulary to exist in two places
... If there are accessiblity requirements for a term, then we may need to create mappings

RIch: I would like to add a note to DPUB-ARIA that indicates that if a role is not in tables, there should be no normative mapping, not a concern for AT

Ivan: We also need to define exit criteria for roles in DPUB-ARIA

Rich: We might need Michael for this, but it might just need to be added to the validator

Michael: Inclusion in validator is probably not sufficient exit critera
... I wonder if we should have default mapping instead of no mapping

Rich: If we have default mappings, then we need to test it

Michael: it has to have some meaning to AT users

ivan: I prefer Rich's approach. If there is no explicit mapping, then there is no meaning
... The intention of the term is to supply structural information.

Tzviya: An example is "learning-objective"
... The idea is to fall back to the mappings of the Element, not have no mappings at all

<ShaneM> if <div role="doc-learning-objective">lala</div> is in the text... then IS there a default mapping?

Rich: some APIs will default to the role that is provided

<Zakim> ShaneM, you wanted to ask about the mappings

<ShaneM> if <p role="doc-learning-objective">lala</p> is in the text... then IS there a default mapping?

michael: that is more of a useful function of the API, then anything we need to be concerned about

rich: it depends on the API

<ShaneM> <p role="button">my button</p>

tzviya: in summary, shane is saying that the presence of the role will overwrite the default definiton of the main element
... Rich is saying that it depends on the API

<ShaneM> but it will still be VALID. which was dpub / daisy's concern

Rich: If we don't map the roles, then the the APIs will disregard the values. It may show as an object attribute in some APIs. But, the default value of the HTML element will still be exposed to the AT user.
... I will double check with AT devs

Tzviya: The discussion with the TAG is that this is a great way to use ARIA
... and we (ARIA) need to define exit criteria.

<ShaneM> My new tagline is "Accessibility: It's not just for humans any more!" (TM)

Janina: There is precedent for that

<ShaneM> http://spec-ops.github.io/html-note/index.html

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2016/08/11 13:38:26 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/if there are no mappings/if a role is not in tables, there should be no normative mapping/
Found Scribe: tzviya
Inferring ScribeNick: tzviya

WARNING: No "Topic:" lines found.

Present: Janina Rich Matt Ivan MichaelC ShaneM
Agenda: https://lists.w3.org/Archives/Public/public-dpub-aria/2016Aug/0008.html
Got date from IRC log name: 11 Aug 2016
Guessing minutes URL: http://www.w3.org/2016/08/11-dpub-aria-minutes.html
People with action items: 

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report

[End of scribe.perl diagnostic output]