Meeting minutes
<Github> https://
<Github> https://
<Github> https://
<Github> https://
<Github> https://
Reminder: TPAC is here, are you coming? Next meeting 26 Sept. 3 weeks off.
<CharlesL> I am also going
Lionel_Wolberger: TPAC serveral people are going, myself, Matthew, Janina, anyone else?
CharlesL: is going to TPAC
<janina> https://
janina: above is the master page with 2-3 Adapt related activities on the calendar; There is a proposed meeting on Tuesday (not fully confirmed). First Adapt meeting is with Anna K. on behalf of WHATWG. Need to request a reserved prefix for Adapt.
janina: there is a breakout on Wednesday; an early meeting on Thursday morning with Epub
<Matthew_Atkinson> Tuesday: https://
<Matthew_Atkinson> Thursday: https://
<Matthew_Atkinson> Also Thursday: https://
janina: meeting review: Wednesday breakout; Tuesday (proposed) with Anna K; Thursday early morning with EPUB
<Matthew_Atkinson> Proposed breakout: https://
Matthew_Atkinson: pointers above and meetings are correct on the wiki page
<CharlesL> ack
janina: 2 topics to discuss with ARIA on Friday morning
<Matthew_Atkinson> Friday: https://
janina: our use cases are looking for a smarter live region - mostly about timing, for example reminding of timeout more often during the last few minutes before timout occurs;
janina: ARIA has a request for hiding decorative images, they want to cooperate with Adapt on hiding decorative images;
janina: during CR we are looking for content to show support for our attributes and AT that can support; Many reasons for Adapt folks to attend this meeting.
TPAC Prep status (TAG, COGA, others?)
<Github> https://
janina: meeting with TAG is still not scheduled, I am escalating getting this scheduled
Lionel_Wolberger: I wrote to COGA with agenda for a meeting, was asked to propose a time
janina: it is still not clear that COGA folks are attending; believe we don't necessarily need an in person meeting
janina: COGA folks aren't registered;
janina: requested 5 attendees
MichaelC: there is a cost issue associated of having an in person meeting so if we don't have enough people we need to schedule as remote meeting
janina: check wiki of APA meetings, not sure where we would schedule COGA. Scheduling with TAG is most important as it is an action oriented meeting.
<janina> https://
janina: above is the entire list of breakouts
janina: times have not been assigned, yet
Janina: Thursday meeting at TPAC with CSS also
Matthew_Atkinson: CSS has suggested that we can use media queries to accomplish some of the Adapt change
Matthew_Atkinson: I have created a sample page - link available on list. Demonstrated live during the meeting. Demo is to show that can't get rid of all distractions equally using media-queries. You can get rid of most moving content using media-queries but Adapt allows more fine-grained controls. Can get rid of distraction of moving via css media queries. But, we can add more simplification
Matthew_Atkinson: can people think of things we can't control via distractions
JF: does prefers reduced motion refer to the entire page?
Matthew_Atkinson: yes, prefers reduced motion is page level but can narrow it down to the element level as well. HTML picture element has good support for prefers reduced motion
JF: curious how many content devs. are actually using HTML picture element; We have had concerns about serving mulitple images - if there a way to provide different alt text.
JF: steve faulkner was doing some research about content and element usage, maybe he could help?
Matthew_Atkinson: agree, we need a way to determine how often HTML picture element is used
Matthew_Atkinson: also wonder if web almanac would have data
janina: best interface to implementors are TAG, Anna K, and CSS
Matthew_Atkinson: elements moving within a 3rd party content iframe wouldn't work. Am looking for other examples where media queries will not work to stop moving distractions
<Lionel_Wolberger> Dispositive - such that it disposes (of some of our claims)
janina: I think we may find that media queries does a good job with distraction and there is overlap with Adapt; Need to discuss whether or not we still need adapt distraction - really want a discussion about this rather than a cut and dried decision based on demo;
janina: addition of prefers reduced motion was made by previous iteration of APA group; We need to consider where we will get better uptake / implementation
Lionel_Wolberger: another possible example: dialogs that shake/move if there are errors within it
Matthew_Atkinson: media-queries would handle that one (dialogs shaking)
<Lionel_Wolberger> FYI Shaking password text field, http://
Lionel_Wolberger: thanks Matthew for the exmaple
Conformance RFC 2119 PR
<Matthew_Atkinson> PR (now merged): https://
<JF> https://
Lionel_Wolberger: Adding conformance requirements and exit criteria to our spec; CfC ends tonight
<JF> actual source: https://
<Matthew_Atkinson> https://
Lionel_Wolberger: we have added section 3 for conformance (reads out loud) see link above.
Explainer regarding @rel vs. purpose/destination/action
Lionel_Wolberger: discussed the differences and will write an explainer. Will this be a stand alone or part of an existing explainer?
janina: believe we will add to existing explainer; this topic does come up often
<Lionel_Wolberger> The explainer is here, https://
CharlesL: there is only one may and one must in the entire document. This is the section on the bliss symbol set, that seems odd to me
janina: need to tell implementor community what they must do and what they might ignore
Matthew_Atkinson: we are looking for 2 independent implementations; but we need to understand that an implementor is not likely to implement the entire spec. But if do implement some, it must be fully scoped.
Exit criteria status
Lionel_Wolberger: are there open issues for exit criteria?