Meeting minutes
<jamesn> * [Deep Dive planning](https://
<jamesn> ### Quick Status Checks
<jamesn> * [Initial aria-textseparation (depends on generic PR being merged)](https://
<jamesn> * [Inconsistency between native and ARIA listboxes when implicit aria-selected is provided](https://
<jamesn> ### In-Depth Discussion
<jamesn> * [Clarify usage of aria-haspopup](https://
<jamesn> [Deep Dive planning](https://
<jamesn> ### Quick Status Checks
<jamesn> * [Initial aria-textseparation (depends on generic PR being merged)](https://
<jamesn> * [Inconsistency between native and ARIA listboxes when implicit aria-selected is provided](https://
<jamesn> ### In-Depth Discussion
<jamesn> * [Clarify usage of aria-haspopup](https://
1/27/22 ARIA Working Group Meeting
<spectranaut> New Issue Triage
New Issue Triage
<jamesn> https://
should tab role have ax tab button as subrole
James buttons inside tabs create a mapping issue
tab is a children presentation true element
tree grid aria orientation
scott: aria orientation supported for treegid, assuming it is a oversite, it is not allowed on tables or grids
Matt: solution for blocking inheritence?
Matt: remove tree as superclass, what is the effect?
matt: should be editorial
james, scott: low priority
New PR Triage
<spectranaut> New Issue Triage
<jamesn> https://
1687, 1686 are related to the charter, editorial
Deep Dive planning
core AAM Mapping
Scott will merge
handling author errors
Scott needs reviews
purpose to specify form and region roles do not be exposed if they don't have names
Topic HTML element mappings
cleanup removing interface declarations, changing elements to map to generic, holding off due to verbiage
defined in Core AAM for generic
figcaption name computation
Initial aria-textseparation (depends on generic PR being merged)
<jamesn> zakijm, take up item 3
Deep Dive planning
<jamesn> https://
<MarkMcCarthy> zazkim, take up item 4
Initial aria-textseparation (depends on generic PR being merged)
Clarify usage of aria-haspopup
https://
Scott: aria-haspopup, non true/false values lack AT support, haspopup changed buttons to menubuttons. We don't need to specify that we are popping up a dialog
wish we could go back to aria-haspopup to being binary
Matt: we let the action describe itself
the menu value was dealing with support issues of the past
as long as the popup describes itself
the only reason to have aria-haspopup
if the popup itself requiered a special action
aria haspopup feels legacy
doesn't solve any problems
Melanie: votes for simplicity
aria-expandedl, focus should remain
can't let the new content present itself
Bryan: it doesn't solve a problem
can only have one token value
but a button can generate a listbox and have an attached menu
<MarkMcCarthy> s/Bryan: it doesn't solve a problem
it was flawed, favors making it simpler
not sure why combobox needs haspopup
per Matt, deprecate only use for legacy API's
to really go for simplification
Bryan: favors simpler token values, but not eliminated on use with active element roles
user would likely not be aware of the popup menu
is aria-haspopup the right solution
would it be better then new properties like aria-actions
bryan, worries that if we change it it will break functionality
aria-haspop true/false only and only use for menus, supported by Bryan and Matt
aria-haspopup is only used for menus with only true/false values, backwards compatibility will be fixed, deprecated tokens
dialog could be interpreted is false
processing non valid tokens
Scott: it would need to be false
menu would be interpreted as true
use aria-haspopup for a menu button or don't use it