Meeting minutes
<MichaelC> https://
New Issue Triage
<Jemma> scribe:
<MichaelC> https://
chris: I want to reinforce the note
michael: this will be assigned to APG group issue
<MichaelC> moved to https://
<MichaelC> https://
mck: APG moved this to ARIA this Tuesday
New PR Triage
<spectranaut> https://
<MichaelC> https://
<MichaelC> https://
it is word change so we can merge it.
<MichaelC> https://
valerie: it does not need to be discussed now.
<MichaelC> https://
Update related concepts for landmarks
scott: adding missing related concept to the PR - adding link to banner, complementary and main.
jcraig: it matters in which version is merged into.
peter: I can merge the PR
<MichaelC> https://
Fix: add aria-level as supported on treeitem
scott: dropped supported property was removed back
<sarah_higley> context: https://
Joannie: I think I implemented the change.
scott: adds aria-level to the supported states and property cell of the characteristics table since its no longer being inherited due to the change to listitem
joannie: level was dropped for xx as part of 1.2
<pkra> https://
mck: level support was not dropped becuase APG cannot think of actual use case.
<pkra> removed aria-level from treeitem
<MichaelC> https://
abstract roles remove 'name from' #1667
New PR Triage
scott: last pr about figcaption. looking for the reivew/suggestion to update the issue
<scotto> https://
scott: explains the problem - "Per what's being discussed there, if an entire video transcript were placed within a figcaption, the flattened text string of the transcript would become the accessible name for the parent figure"
mck: we saw the same problem in APG
… any discussion about details?
Chris: do we need both name calculation?
Scott: this would make figure associated with figcaption additional details - they can use title, aria description, aria detail
mck: so will current mapping always take figure caption and ... name?
scott: caption is connected to labelled by IAA2(MS?)
… I need to check with UIA folks
scott: I still need to check a few things and to do.
TODO:
need to check on updates to UIA mapping, if any.
do we want figcaption to map to caption?
regardless of above, caption will need to be updated in regards to its referencing figure and figcaption relationships
aria-details definition should be updated to reference this change
mck: I thought caption was the one we pulled out.
scott: if there is any implementer who want to chime in, it would be good.
I will add jcraig as the reviewer
Deep Dive planning
jaemsn: sarah will talk about ..
Deep dive: Secondary actions on items in composite widget roles
<carmacleod> https://
jamesn: if there is any suggestion for deep dive, msg Jamesn
Next week https://www.w3.org/events/meetings/1f06f919-513f-4341-aa47-2027ee0925c5
Consider collapsing Base Concept category into Related Concepts
<jamesn> https://
car: I am wondering whether having both Base Concept and Related Concepts is really all that useful? Perhaps it would be sufficient to just keep Related Concepts? If there's an existing Base Concept, it could simply be the first item in the list of Related Concepts? Thoughts?
comment from Jaws-test is
"I think the separation into base and related concepts is not wrong, it should just be done and described correctly:
base concept: similar element in another specification like e.g. HTML, SVG etc..
related concept: related role in the ARIA specification (like listitem and option, link and button)."
car: I'm still not sure about restricting Related Concepts to only aria, but it always makes sense to include alternative aria roles.
scott: "basically" related concept
: jamesn: we removed a lot of xhtml
… and remove those unless it is really useful
chris: it is really hard to teach ARIA . those concepts are valuable but I see the advantage of removing those.
… if we have a chance to simplify the concept, I am up for it.
jamesn: APG is more intended for authors.
scott: I am happy to combine basic and realted concepts but
… I would up for simplification
… simplifying the concepts.
if needed we can make a reference to html.
car and scott can work on this issue.
jamesn: important thing is keeping the consistency throughout the spec
Inconsistency between native and ARIA listboxes when implicit aria-selected is provided
<jamesn> https://
carolyn will be ready for this next week
Figure out what to do with the DPUB mappings overlap with the ARIA Core spec, in the context of newer implementation differences
<jamesn> https://
jamesn: Need more people to comment about what they think is useful here
jcraig: I will add a comment. Reminder to the group that if you have opinions, please share.
[Role Parity] What do we do about embed?
<jamesn> https://
<chlane__> herebedragons lol
scotto: I don't think there should be a role for these
jcraig: For implementation consistency, might be useful to have a role that authors don't use, but are returned by the developer tools in contexts like inspectors, WebDriver, and other interoperability tests
jcraig: For instance, video has some features that can't be surfaced because there's no specific role
<jamesn> https://
<pkra> agenda!important
scotto: should we consolidate these?
jamesn: I think there are enough people that want a role for audio and video that we shouldn't mix these with embed and object
chris_lane: Is canvas similar?
<jamesn> https://
jamesn: There is an issue for canvas.
Clarify usage of aria-haspopup
<jamesn> https://
jamesn: we need to talk some more before a proposal. there's not enough time today, so we'll put it early on the next agenda.
<Laurence> https://