Meeting minutes
<pkra> present_+
New Issue Triage
accname #166
<Github> https://
spectranaut: can close
jamesn: closing
jcraig: might be dupe
jcraig: pr#69 covers it
#1782
<Github> https://
jamesn: duplicate
jamesn: someone that understands a11y apis do this
spectranaut: will do it
jamesn: any object can only have a single language
in most apis
jcraig: referenced element lang is an edge case
breaking up audio
jamesn: seems unresolvable
New PR Triage
StefanS: can both languages be used?
jamesn: confirm or deny
jcraig: it works where we made it work
1780 DA spectranaut assigned
#1778 has reviewers, scotto some were volunteered
core aam #135
<Github> https://
jamesc has it
@jamesc #1778
<Github> https://
<spectranaut> jcraig: ^
@jcraig #1778
<Github> https://
Deep Dive planning
next installment of popups
scotto: sure
scotto: questions from aarons doc in a discussions thread
<jamesn> https://
#1781 popups and a11y
<spectranaut> btw, from the previous topic, jcraig here is the other PR to review: https://
spectranaut: thanks
look at #1781
jamesn: last DD before TPAC
TPAC Topics
jamesn: current topics were already in flagged issues
now is the time to add new topics ...
APA 9/13 and 9/15
jcraig: PRs to finish before TPAC
DPUB ARIA,
back and forth in issue thread is unclear
jcraig: plans to finish next week, gihub comments
jamesn: not too late to register
there is a fee waiver
if your company is paying we prefer to not use it
to pay for the conference
yourself get the waiver instead
Where are we on Support aria-description
jamesn: where are we on accname #69?
<Github> https://
scotto: almost finished
scotto: next week will submit a PR to html-aam
jamesn: looking into 'Github' bot (not github-bot)
doing wrong things
MichaelC: will see
<MichaelC> Github, please part
MichaelC: not a bot I know of
could be a random persons bot
MichaelC: need operator status
MichaelC: they didn't like the past way will follow up
github bot and operator status
priveleges too low
Where are we on Initial aria-textseparation (depends on generic PR being merged)
jamesn: pinging Matt
Open PR Triage
<jamesn> https://
<pkra> or https://
jamesn: changing to standard ordering
#1780 needs reviews
<Github> https://
#1766
<Github> https://
jamesn: fixed xref html yesterday should be ready a soon as we get someone else to look at it
spectranaut: can talk to Alex but they are on vacation
jamesn: do custom elements make a difference to our spec?
jamesn: I believe it is not a problem
jamesn: #996 that Matt took on in march
<Github> https://
matt king, the dialog popover stuff has been my focus
until I feel better about those I'm not going to work on this
we can see whether anything changes between now and TPac
any reason to push hard to make it a 1.3 thing?
let it slide, small consequences?
jamesn: face to face discussion
scotto: we also have other
PRs
to get around this
generic, block level
inline
everything is generic
CSS rendering decides it
jamesn: is it being rendered by CSS?
jamesn: ovveride?
render inline to render a word
matt, recommended to change divs to spans
matt could have also used textseparation
CSS is the root of the problem
creepy voice on jamesns computer
lol
pkra: ask the children
lol
#1754
<Github> https://
ready to merge
pkra: will take care of it
#1762
<Github> https://
jamesn: fixed links
scotto: looks good
#1778
<Github> https://
talked about it
#1454
<Github> https://
jamesn: not ready
#1494
<Github> https://
scotto: james and I
are on it
#1733
<Github> https://
pkra: needs to update
#1738
<Github> https://
jamesn: on me still
suffix elements for idl
#1660
<Github> https://
jamesn: might be ready?
jamesn: ok
scotto, sarah and jamesn have reviewed
jamesn: any disagreements to merge?
<spectranaut> pkra, can you merge?
group says merge
#1695
<Github> https://
pkra: for micheal
#1734
<Github> https://
jamesn: reviewed by sarah and DA
chlane: reviewing #1734
<Github> https://
#1744
<Github> https://
#1740
<Github> https://
tediously long names
scotto: simplifying to list values? spectranaut this is a draft PR
#1162
<Github> https://
clarify intent of required owned elements
matt seems like a dupe
pkra: covered by sarah
#1033 Clarify required owned element
<Github> https://
the PR is #1454
<Github> https://
#1127
<Github> https://
clean up use of 'may'
jamesn: do we care?
reassing to rfc 2119
jamesn: only an rfc keyword if it is uppercase
matt respec was automatically capitalizing
strings like 'SHOULD'
jamesn: we do this in our stuff
jamesn: 'may' if its uppercase otherwise its not
matt, you must type in in uppercase in the source to be normative
spectranaut: who are the editors?
jcraig: don't care
I DON'T CARE
close in uppercase lol
spectranaut: he has a point
matt from an editorial standpoint, be careful
not using the word 'should' unless normative
matt must, may and should
is confusing
jamesn: why?
Matt_King: in the spec we should be careful
Matt_King: not for merging this PR
Matt_King: we should not make this problem more prevelant
spectranaut: what is it like to read with SR?
Matt_King: will sometimes look for uppercase
pkra: can we punt it back to fix merge conflict?
spectranaut: assign to me
jamesn: look for new things that have been added
jamesn: hard to merge
spectranaut: this process of mult branches needs to be resolved
spectranaut: hard to understand normative and not
#1048
<Github> https://
pkra: didn't make it into 1.2
jamesn: it's trivial
why haven't we merged?
5 words
#1019
<Github> https://
jamesn: should we close is this overcome by events?
scotto: I thinks so, sounds like we punted it not a bad idea
#1018
<Github> https://
scotto: same sort of thing
jamesn: jcraig suggested naming mechanism for articles
Matt_King: we struggled to figure how to make a predictable algo that would be useful
jcraig: we got a user report about this
jcraig: trying to be flexible in wording
jamesn: flexibility is .. a strong suggestion for the right thing to choose
jcraig: add myself to reviewers
jamesn: no label use first heading
scotto: just use first heading
jamesn: accessible name from heading
scotto: restart
not the PR to merge
jamesn: issue deserves more consideration
pkra: like original suggestion
put in a 'may'
let them do something
jcraig: maching learning is getting better then what we can spec
jamesn: isn't it better if the author knows
Matt_King: that path is complicated
jamesn: certain roles, no a11y name use first header
in resolving errors section
jamesn: TPAC Topic
Matt_King: lets do it again
<jamesn> https://