<Jemma> https://github.com/w3c/aria-practices/wiki/December-3%2C-2019-Meeting

<scribe> Scribe: carmacleod

2 more meetings in Dec

aria-level

<Jemma> https://pr-preview.s3.amazonaws.com/w3c/aria-practices/pull/1109.html#aria-level

aria-level guidance

<zcorpan> GitHub: https://github.com/w3c/aria-practices/pull/1109

mck: pr is getting close to ready

<zcorpan> ARIA issue about this https://github.com/w3c/aria/issues/1050

mck: should we allow aria-level > 6?

simon: some screen reader (s) don't support levels > 6

jamesn: does it just say "heading" without level?

simon: not sure

<zcorpan> https://github.com/FreedomScientific/VFO-standards-support/issues/301

simon: perhaps we should advise authors not to use > 6

<zcorpan> https://github.com/w3c/aria-practices/pull/1109#issuecomment-550029120

mck: I would be fine with a note saying it's not defined what screen readers will do

<MarkMccarthy> +1 to Matt's suggestion of a note

simon: according to html, it is possible to have section with h1 to arbitrary depths

aria-live

mck: rough draft

<MarkMccarthy> https://github.com/w3c/aria-practices/blob/zcorpan/live-regions/live-regions.md

<jamesn> https://www.w3.org/TR/core-aam-1.2/#mapping_events_visibility

jamesn: this is the closest I could find to defined events
... it doesn't say what AT need to do, it just assumes that they can use this to tell if a live region has changed
... shows what events are fired

mck: is there any browser api directly tied to aria-live?

jamesn: no
... the Apple column is more specific and ties the event to live regions

mck: I wonder if we have a gap in testability here, i.e. (outside of Apple) the browser doesn't have a specific responsibility
... so onus is on AT to listen for events and interpret

<Jemma> https://rawgit.com/w3c/aria-practices/master/aria-practices-DeletedSectionsArchive.html#docmgt

mck: so it's not clear which ways of interpreting events are valid

jemma: here is old content ^

mck: simon, is there enough info here to draft a proposal?

simon: live regions are not well defined, and implementations tend to be different, so not reliable

mck: if there is a specific kind of dom change event that is buggy with most screen readers, we need to guide people towards things that will work
... if there are certain techniques that we know will work across screen readers, then we need to emphasize that
... we need to tackle this in 1.3
... I think we should give more responsibility to browsers. we may need to specify new api.

States

<zcorpan> GitHub: https://github.com/w3c/aria-practices/pull/1277

<zcorpan> https://github.com/w3c/aria-practices/blob/c356a98dc1f4c4e851ec93d7572c46333de12184/widget-states.md

mck: if there are any states that are not touched on here, please comment in pr

range related properties

mck: did we resolve the questions about undetermined value? (i.e. min and max undefined)

simon: spinbutton is an example that allows undefined min and max

mck: progressbar too
... we don't have an apg example of something that doesn't have a defined range

<Jemma> for aria widget status, are you starting from here, https://www.w3.org/TR/wai-aria-1.1/#attrs_widgets?

<zcorpan> https://pr-preview.s3.amazonaws.com/w3c/aria-practices/pull/1279.html#range_related_properties

<zcorpan> GitHub: https://github.com/w3c/aria-practices/pull/1279

<Jemma> Communicating Value for Range Widgets

<Jemma> aria-valuetext Defines a description of the value of the element.

simon: I added an example of an undetermined progressbar

jon: need more on when to use aria-valuetext
... how should you think about valuemin and valuemax if you have valuetext
... i.e. if we have low, medium, high, do I put in 1 for min and 3 for max?

simon: aria spec says you can _also_ use valuetext as well as min and max, so unless spec changes, we need to have min and max
... if it's required for the role

jon: if it's a price range, screen readers only say the text

mck: if I want to know the range, I type home and end key to find min and max

<Jemma> +q

<Jemma> https://pr-preview.s3.amazonaws.com/w3c/aria-practices/pull/1279.html#range_related_properties_using_aria-valuemin_and_aria-valuemax

mck: some will communicate percentage and some will communicate actual values (I think spinbuttons say value, and sliders say percentage)

<Jemma> https://rawcdn.githack.com/w3c/aria-practices/1f7d940ca9872ff2f240c65ce4520338fbdbd3c6/examples/meter/meter.html

simon: for progressbar, min and max default to 0 and 100; for meter, authors are required to provide min and max

Combobox

<zcorpan> GitHub: https://github.com/w3c/aria-practices/pull/1276

<Jemma> carmacleod: there is some info about fall back value for aria value min and max

carmacleod: Here is Fallback values table in ARIA spec: http://w3c.github.io/aria/#authorErrorDefaultValuesTable

jon: combobox Esc key behavior: Esc closes popup; 2nd escape clears textbox

mck: for autocomplete=both, enter and esc are essentially the same: value is chosen
... for autocomplete=list, enter and esc are different; typing "al" then down arrow, then esc, leaves "al" in combobox

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/Matt's suggestion/Matt's suggestion of a note/
Default Present: Matt_King, zcorpan, Jemma, MarkMccarthy, carmacleod, jamesn, jongund
Present: Matt_King zcorpan Jemma MarkMccarthy carmacleod jamesn jongund
Regrets: Bryan Garaventa Bryan_Garaventa CurtBellew
Found Scribe: carmacleod
Inferring ScribeNick: carmacleod
Agenda: https://github.com/w3c/aria-practices/wiki/December-3%2C-2019-Meeting

WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

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.)