<joanie> agenda: this
<joanie> agenda: be done
<Stefan> my headset .. no mic
<scribe> scribe: carmacleod
<joanie> https://github.com/w3c/aria/issues/1119
https://github.com/w3c/aria/issues/1119
joanie: triaged
<joanie> https://github.com/w3c/aria/issues/1120
<joanie> Add normative text to menuitem and treeitem about allowed child elements
<joanie> menuitem and treeitem need some normative text about what are the allowed child elements. Any elements which are not the allowed child elements should act like Children Presentational: true
jamesn: there's a bunch of related things here - would like to look at this in 1.3
<joanie> https://github.com/w3c/accname/issues/67
<joanie> Clarification of 2F for descendants of label with concrete role
joanie: can look at doing this for accname 1.2 (it's on a different release schedule)
bryan: the only caveat is that the numbering has changed, so this is not 2F anymore
james: fieldset/legend stuff shouldn't be in 1.2
joanie: upstream master is still 2F
<joanie> https://github.com/w3c/aria/issues/1118
<joanie> Clarify what it means to support "ARIA 1.0 combobox"
<joanie> Why should conformance checkers support the ARIA 1.0 pattern? If we want authors to use the 1.2 pattern, shouldn't conformance checkers flag an error when the 1.0 pattern is used?
<joanie> What does it mean for UAs and ATs to support the ARIA 1.0 pattern? If it is required for web compat to support the legacy markup pattern, the processing model to handle both the 1.2 pattern and the 1.0 pattern should be clearly specified in the current spec.
bryan: 1.0 pattern should still be supported
<jamesn> 1.3
mck: it just means that if you have a textbox owning something, the aria-activedescendant will still work
jamesn: conformance checkers should issue a warning for the 1.0 pattern, but they should issue an error for the 1.1 pattern
mck: need to make sure the
language is clear
... you can assign to me
<joanie> https://github.com/w3c/aria/wiki/Plans-regarding-role-parity#todo-1-3
<joanie> https://github.com/w3c/aria/projects/8
jamesn: the wiki is more organized than the project at this time
<joanie> aria-textattribute for role parity with generic (#960)
<joanie> aria-listtype for role parity with ul and ol (#961)
<joanie> aria-inputtype for role parity (#962)
<harris> I can take aria-listtype
joanie: I will look at those 3
(unless someone wants to adopt them)
... thanks, harris!
<Scott_O> do we need listtype?
mck: if it's an ordered list, it has numbers; if it's an unordered list, it has bullets - is that enough?
scott: if you use css, you can remove those
mck: this gets into the whole css for accessibility thing
joanie: we already discussed this, and decided to go ahead with it
<joanie> https://github.com/w3c/aria/wiki/Plans-regarding-role-parity#todo-1-3
joanie: we still have
aria-textattribute for generic, and aria-inputtype
... anyone interested in doing canvas?
... maybe we already have role parity for that one?
... maybe role graphics-document?
jamesn: if focusable, maybe role application?
scott: it's meant to be
represented as a bitmap graphic
... depending on how innards are exposed, could be many
things
mck: would default mapping be generic?
scott: well, it is meant to represent a graphic
mck: it's useful to have some
perception that there's something graphical there
... if it's an image, then AI can analyze it and tell me what's
in it
<joanie> https://github.com/w3c/aria/issues/927
joanie: please comment in issue ^
<joanie> https://github.com/w3c/aria/issues/928
joanie: how to map details
scott: shouldn't be mapped
mck: how do we map summary? need to talk about both of those together
<joanie> Summary: https://github.com/w3c/aria/issues/939
scott: toggle button with show/hide panel
mck: uses aria-expanded on
summary
... can you use a details without a summary?
others: no
scott: we can already do this with what we have
<harris> +1
mck: button with aria-expanded on
it
... that's ^ for the summary element. The details element is
just generic.
<joanie> https://github.com/w3c/aria/issues/929
joanie: ^ does anyone have an opinion on embed
peter: I can volunteer for iframe
scott: for iframe, maybe a role
called "scrollframe"?
... or "scrollable frame"
<Matt_King> scrollableframe better than scrollframe
<Scott_O> agreed. also never "said" scrollframe except in jest :)
car: sorry about that, Scott :)
https://github.com/w3c/aria/issues/879
joanie: one of the benefits of these roles is to give the screen reader a hint: "browse mode" or "focus mode"?
https://github.com/w3c/aria/issues/929
joanie: embed
... my platform has role "embedded"
jamesn: so we should use that
scott: it is being exposed as something right now, so don't want to go with generic
<jamesn> role="herebedragons"
joanie: tentative proposal for
embed and object to come up with a new role
"embeddedobject"
... lets screen readers know that it's something like "flash",
or something that they can't do anything with
<jamesn> role="DoNotUseEmbeddedobject"
scott: I'll take on the dragons
<joanie> https://github.com/w3c/aria/issues/938
joanie: yay! issue 929 and 938
<CurtBellew> I need to run. See you all next time.
jamesn: are there any big chunky things that people have as priorities for 1.3?
mck: I want to get aria-controls straightened out
<pkra> braille properties.
<pkra> :)
james: I'd love to get that done - totally agree for aria-controls
jamesn: matt and scott can own the aria-controls issue
<Scott_O> https://github.com/w3c/aria/issues/979
scott: propose "clarify role tooltip"
jon: interested in name from
caption and name from heading issues
... annotations
jamesn: would like to see progress on other things like feed, so could apply to tables
mck: like virtual cursor api that ms proposed - that would be fabulous - would that have been part of aria?
<joanie> https://github.com/w3c/aria/issues/812
mck: issue 812, related to
combobox, but about spinbutton
... composite is something where you manage focus of children,
spinbutton is not a composite
jon: I can help with 979 tooltip
mck: I still want to deprecate some of the live region roles (but that's a larger discussion)
<Stefan> sorry mic is broken
harris: would like aria spec to be made available in json format so tools can consume it
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/ i / in / Found embedded ScribeOptions: -final *** RESTARTING DUE TO EMBEDDED OPTIONS *** Default Present: Joanmarie_Diggs, Stefan_Schnabel, pkra, harris, jongund, carmacleod, CurtBellew, Bryan_Garaventa, Scott_OHara, Matt_King Present: Joanmarie_Diggs Stefan_Schnabel pkra harris jongund carmacleod CurtBellew Bryan_Garaventa Scott_OHara Matt_King Regrets: Mark_McCarthy Found Scribe: carmacleod Inferring ScribeNick: carmacleod Found Date: 21 Nov 2019 People with action items: 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]