<scribe> scribe: carmacleod
<jamesn> https://lists.w3.org/Archives/Public/public-aria/2019Nov/0001.html
WebApps is no longer working on HTML AAM - askng if ARIA WG can take up working on this
<Scott_O> web apps :)
<MarkMccarthy> MarkMccarthy: Message James was referencing: https://lists.w3.org/Archives/Public/public-aria/2019Nov/0001.html
jamesn: so the idea is that we would have all of the AAM's
joanie: I will be able to help
Scott out with HTML AAM
... Michael says we don't need a call for consent to adopt the
spec, just to publish it
jamesn: sounds like we don't have any objection to doing this
joanie: we do not own HTML, so we don't get to say how authors should use aria in html, but we can suggest
michael: html working group
coordinates with whatwg
... html working group publishes whatwg snapshots once a
year
jamesn: current plan date is
first week of May in Europe (not fixed date yet)
... Vancouver Canada TPAC October 2020 is 2nd F2F
... TPAC is Oct 26-30, 2020
<jamesn> May 5-7 Dublin (date and location tentative)
<aaronlev> I can't wait to go to Dublin
<jamesn> https://github.com/w3c/aria/wiki/1.3-Planning
jamesn: 4 big topics: Outstanding
Role Parity issues
... Attribute Parity
<joanie> https://github.com/w3c/aria/issues/961
james: New Naming things, DL/DD/DT, Native??
jamesn: ARIA Annotations stuff that Aaron has been working on - big feature
aleventhal: new roles, plus aria-description
<aaronlev> also maybe, change aria-details to IDREFS (from IDREF)
james: new braille stuff
jamesn: any other big things for 1.3?
joanie: for ol vs ul, consider
attribute to distinguish
... other attributes to distinguish roles
mck: need some refinement to the language of aria-haspopup, refinement to language of aria-controls
jamesn: agree, we need to triage
issues to make sure we work on the high prio ones
... would be good to have everybody go through issues and speak
up if there's something you want to work on for 1.3
<joanie> https://github.com/w3c/aria/wiki/Plans-regarding-attribute-parity
joanie: there are lots of
attributes that are not mapped in html, and don't need to
be
... scott, can you look through list at above link
joanie: we can't make "aria audio and video" as accessible as native
<Zakim> jamesn, you wanted to say I think we need aria-valuetext on input
jamesn: need some sort of value attribute
mck: aria doesn't have any of the semantics of text interface
aleventhal: can work around with offscreen contenteditable
mck: there are more kinds of input than text fields that could use a "value"
<BGaraventa> I would like to see a way of adding a value prop to combobox
<aaronlev> synthetic text fields should wait until ARIA 1.14
mck: we don't need to deep dive on this right now, joanie added item to wiki
joanie: everyone should take the
time to read over these
... image height/width exposed by user agents as per html AAM
spec
... nice to own aria in html and htmlAAM specs because we can
ensure that AT get what they need
scott: there's also css aam
mck: we are now also responsible for html aam testing
joanie: jon and I have quirky but
useful automated testing tools for that
... reading through Plans regarding attribute parity wiki
page...
... go pick out the thing you care about, pull it out into a
github issue, and start thinking about it
jamesn: Annotations
<jamesn> https://github.com/aleventhal/aria-annotations
jamesn: aleventhal has simplified the proposal (link above)
aleventhal: 4 or 5 new roles -
revision, suggestion, comment, commentsection, and mark
... simple annotations like "description": add
aria-description
... wasn't added to aria originally because we thought
description should always be visible, but that hasn't turned
out to be true
... description is the simplest form of aria-details
jamesn: how does a sighted person get the info
aleventhal: for "someone is editing nearby", a caret with the person's name shows up
<MarkMccarthy> MarkMccarthy: There is an image showing how an editor on Google docs shows up here - https://gsuite.google.com/products/docs/
<aaronlev> +1
<aaronlev> Stefan: aria-description shouldn't be used when there is a better semanntic
jamesn: we have restricted aria-label[ledby] on some roles, and we were thinking of restricting aria-describedby on some things as well
<Scott_O> +1 for discussing limiting aria-describedby in 1.3
aleventhal: there's no reason to restrict aria-description on anything that's visible, as far as I can see
mck: can be hard to hear when details are read
carmacleod: I like the idea of an earcon, and then users can request the info on demand
aleventhal: let's put this on the
discussion list
... I have it in Chrome Canary behind a flag, so you can
experiment with it
stefan: what is the order if multiple descriptions on an element?
aleventhal: follow the pattern of label in accname, i.e. aria-describedby first, then aria-description, then html like title...
jamesn: for next week, triage,
read 1.3 plans, bring out your priorities
... also take anything off the list for 1.3 that we aren't
going to have time for
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Succeeded: s/WebAxe/WebApps/ Succeeded: s/aria-description/Stefan: aria-description/ Default Present: Joanmarie_Diggs, jongund, Scott_OHara, carmacleod, harris, MarkMccarthy, CurtBellew, Stefan, Matt_King, Bryan_Garaventa Present: Joanmarie_Diggs jongund Scott_OHara carmacleod harris MarkMccarthy CurtBellew Stefan Matt_King Bryan_Garaventa aaronlev MichaelC Found Scribe: carmacleod Inferring ScribeNick: carmacleod Found Date: 14 Nov 2019 People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]