See also: IRC log
<Jason_Duan> Hello everyone
<Jason_Duan> can anyone head me?
<Jason_Duan> I am from IBM
<Jason_Duan> no luck with computer audio. dialing in
<MichaelC> agenda order 1, 4
<scribe> scribe: Janina
mc: Any objections to a CfC on ARIA-Dpub?
[No objections]
<MichaelC> DPub ARIA CR CfC
mc: Hope to publish week following
mc: ARIA in HTML Review requested:
http://lists.w3.org/Archives/Public/public-aria/2016Nov/0024.html
<MichaelC> APA tracking of ARIA in HTML
janina: Notes Michiel is reviewing for APA Action-2104 and cross referencing APG
mc: Proposing the APA review will suffice for this WG as well
janina: Proposing to have him report to both WGs and get the wider audience
mc: Question for now is does anyone want to also review?
mk: No, but I have raised issues on that doc
mc: Anyone we think should review it?
[crickets]
jd: Also raised an issue not yet addressed
mk: Have raised some that have been addessed
[People looking at open issues]
janina: Noting this was once a
joint ownership, via the HTML-A11y TF
... Therefore, we owe a good review
mc: We'll re-address this in a couple weeks
mc: Anything additional this week?
jd: Still working, but nothing major to report
mc: No Testing mtg this week?
jd: Correct
<MichaelC> https://www.w3.org/TR/html51/textlevel-semantics.html#textlevel-semantics
mc: Text level semantics
... <a > we need nothing
jn: Do we have a mapping for an
anchor? Is that important?
... Just asking
mc: Think not, nothing exposed to
api
... so, do we worry about rel?
... Notes there's a lot there ... Do we need these, or save for
2.0
... Suggest we'd need to go one by one
... I suggest they're useful but not widely used, so could be
2.0
mk: We use it to view a style sheet in the apg
mc: But not on an <a >
tag
... Propose this is 2.0
[crickets]
mk: Mapping things not used by AT doesn't make sense, so we want them only if think they would be useful to AT
jn: If it were widespread and
supported, it would be very useful
... But neither is true now
<MichaelC> GH-ISSUE 480 https://github.com/w3c/aria/issues/480
jn: Notes this overlaps Dpub
mc: What about target
attrib?
... We know it's supported
... Tells what window ...
... WCAG SCs refer to this
... Do we need mapping to tell AT where to go?
mk: Today we add invisible text ---
mc: Some AT will tell you about text ---
mk: We did change HasPopup
mc: Does HasPopup meet the use case?
mk: No, need value like "Window"
mc: I think we need to consider this
mk: Agree
mc: So Issue-481
<MichaelC> GH-ISSUE 481 https://github.com/w3c/aria/issues/481
mc: Continuing with others of <a >
jd: href covered on Linux ...
mc: Suggests we need it
jd: Agree
<MichaelC> GH-ISSUE 482 https://github.com/w3c/aria/issues/482
mc: Next download attrib --
believe this is ua ...
... Do we want to indicate that rather than open?
mk: Would propose to cover with target
mc: So add to target issue
... So updated 481
... Next hreflang ...
... Believe not supported by tools
... Lang not known until link opened without this, so could be
a basis for choice, but haven't seen this used
<MichaelC> GH-ISSUE 483 https://github.com/w3c/aria/issues/483
janina: Suggest to ask Dpub and assessment people like ETS
mc: Attrib=type a mime
... Allows selection of prefered mime
... But also not used
<MichaelC> GH-ISSUE 484 https://github.com/w3c/aria/issues/484
mc: Reviewing which are 1.2 and 2.0
mk: Let's keep for now and see what the discussion is
mc: Next <em>
<MichaelC> https://www.w3.org/TR/html51/textlevel-semantics.html#the-em-element
<MichaelC> https://www.w3.org/TR/html51/textlevel-semantics.html#the-strong-element
mc: Suggest also <strong>
<MichaelC> https://www.w3.org/TR/html51/textlevel-semantics.html#the-b-element
mk: Are <b> and <i> still there?
<MichaelC> https://www.w3.org/TR/html51/textlevel-semantics.html#the-i-element
<MichaelC> https://www.w3.org/TR/html51/textlevel-semantics.html#the-u-element
jd: Currently exposed through
text attributes
... We can't really say "emphasis" by simply mapping to
<i>
mk: Pondering using properties
jd: Or an attrib in ARIA
... Proposing ARIA support
janina: Suggesting the history is that these were intended as simple replacements for b and i
mk: We should keep these pieces
together for future discussion
... Think there would coordination on these questions with the
new CSS A11y TF
jd: And ins and del
mk: We have some kind of mapping for ins
mc: Also code? samp? etc
... Want to look for where we need correspondances -- not
necessarily the semantics
... Also cite?
... Also q ?
[agreement]
mc: q is inline quotation
... Almost never see it ...
... Notes some of these attribs are style, and some are
semantic, but different people would class each differently
<MichaelC> GH-ISSUE 485 https://github.com/w3c/aria/issues/485
mk: Willing eventually, but suggest ideal is CSS and perhaps Dpub
mc: Want to look at who to assign these in remaining minutes ....
mc: Next will be December 1 -- no meeting U.S. Thanksgiving Day!
This is scribe.perl Revision: 1.148 of Date: 2016/10/11 12:55:14 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/Micheil/Michiel/ Succeeded: s/rhel/rel/ Found Scribe: Janina Inferring ScribeNick: janina Default Present: Joanmarie_Diggs, Janina, MichaelC, Jason_Duan, Matt_King, James_Nurthen Present: Joanmarie_Diggs Janina MichaelC Jason_Duan Matt_King James_Nurthen Regrets: Joseph_Scheuhammer Agenda: https://lists.w3.org/Archives/Public/public-aria/2016Nov/0041.html WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 17 Nov 2016 Guessing minutes URL: http://www.w3.org/2016/11/17-aria-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]