<Jemma> Meeting Agenda: https://github.com/w3c/aria-practices/wiki/April-14%2C-2020-Meeting

<Jemma> https://github.com/w3c/aria-practices/wiki/April-14%2C-2020-Meeting

<scribe> scribe: carmacleod

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

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

Jon_Gunderson: Can someone fix the PR Preview?

jamesn: need to make sure respec doesn't have errors first
... I'll download master and see if I can get a good build, and I'll take a look at PR Preview

<Jemma> To do list: adding example for each state

<Jemma> Filling gap of ARAI Widget state

<Jemma> Reference to HTML states

<Jemma> Some editorial work for the clarification

<Jemma> Some editorial work for the consistency (add code example itself or just link each states to design pattern?)

<Jemma> Sub section for 7.3, 7.4, 7.5, 7.6 (ex: supported roles), is needed?

Widget States

<Jemma> ARIA 1008

<Jemma> ARIA 1777

<Jemma> ARIA 1052

<Jemma> ARIA 700

<Jemma> ARIA 1130:aria-disabled

<Jemma> ARIA 1026:aria-expanded:

<Jemma> ARIA 798:aria-selected on tree item

<Jemma> ARIA 542

<Jemma> ARIA 684

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

<siri> ./me unable to join via zoom

github: https://github.com/w3c/aria-practices/pull/1277

Jemma: aria-checked is in pretty good shape
... Which one should we focus on next, so that we can get through these?

<Jemma> https://pr-preview.s3.amazonaws.com/w3c/aria-practices/pull/1277.html#communicating_widget_states_aria-selected

mck: Need to help people understand the difference between selected, checked, and pressed.

<Jemma> https://github.com/w3c/aria/issues/798

mck: Not sure if this is organized in a way that makes that easy to explain

<Jemma> Clarify if aria-selected & aria-checked are required on roles 'treeitem' & ('menuitemcheckbox', 'menuitemradio') respectively #798

sarah_higley: Agree

mck: Is that in 7.1.2?

sarah_higley: Yes

mck: Is it specifically the paragraph where it's talking about orthogonal states? Is that the part that's unclear?

sarah_higley: Yes. I don't know what the use case would be. I think it's a bad idea to use both.

<Jemma> https://github.com/w3c/aria/issues/1052

<Jemma> This issue is more close to the current dicussion.

mck: If you have checked representing "include this in some action"

sarah_higley: we never have checked and selected - instead have extra actions

<siri> ./me trying meeting number but no use

<jamesn> nods enthusiastically to sarah_higley

<jamesn> we need to come up with an additional actions pattern

<BGaraventa> +q

sarah_higley: mixed value for checkbox is not supported on treeitems

Jon_Gunderson: there's a discrepancy, because it also says it's not supported on other roles

sarah_higley: checked is not as well supported as selected

<Jon_Gunderson> https://w3c.github.io/aria/#aria-checked

sarah_higley: selected is quite well supported

mck: ARIA should say that you should only use one or the other, but not both

Tabbed carousel

github: https://github.com/w3c/aria-practices/pull/1120

sarah_higley: Would be nice to compare the usability of links vs checkboxes for changing settings, from the point of view of someone reading the spec.

mck: Jon was leaning towards having separate example pages, Sarah was leaning towards checkboxes

Jon_Gunderson: not separate pages - separate links
... change the url to change the setting

sarah_higley: I think having fewer separate pages for the same type of example makes it easier for a new author to find what they are looking for

mck: if the roles, states, properties, keyboard tables have to significantly change then it should be separate pages

sarah_higley: maybe have all of the different examples statically on the page, like the layout grid examples?

mck: we have an open issue to separate the layout grid examples out into multiple pages

<Jon_Gunderson> https://raw.githack.com/w3c/aria-practices/update-carousel-guidance/aria-practices.html#carousel

carmacleod: as a sighted developer, I liked the checkboxes because I could see what the setting did in real-time

<MarkMccarthy> +1 to carmacleod

mck: can we use a checkbox for the setting that changes on reload?

<siri> + jon

Jon_Gunderson: need instructions that say "when you check this checkbox, need to reload the page to see the change"

mck: should we put the checkboxes in a table and have the longer description in another column?

sarah_higley: I don't have a strong opinion on table vs list for the checkboxes. I currently have aria-describedby on the checkboxes to point to the longer description

Select-only combobox example

sarah_higley: I can imagine that would be pretty long

https://github.com/w3c/aria-practices/issues/1026

menubar updates

github: https://github.com/w3c/aria-practices/pull/1356

mck: I made some editorial changes, so from that point of view this is good to go
... need the other reviews to make sure functional and visual are ok
... and regression tests
... definitely need visual review because there were changes to accomodate high contrast mode
... Operating System High Contrast Settings

keyCode Deprecation

github: https://github.com/w3c/aria-practices/issues/1350

mck: should we add this to our code guide?

Jemma: good idea

Extra questions

<Jemma> This is the project I mentioned regarding code guide https://github.com/w3c/aria-practices/issues/1180

sarah_higley: simon approved t.plan, but valerie won't have time - can this be merged?

<Jon_Gunderson> go to go to another meeting

<Jemma> I am also looking for volunteers to help with this project.

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)

Present: mck Jemma jongund carmacleod MarkMccarthy BGaraventa sarah_higley CurtBellew siri
Found Scribe: carmacleod
Inferring ScribeNick: carmacleod

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