Meeting minutes
CfC for Content Module 1.0 CR Status, Issues raised by the W3C Director upon their review [1] Exit criteria (Lionel & Matt), [2] TAG Response Resolution (Sharon research) [3] BCI (Janina communication)
sharon: Lionel and Matthew have not met, yet on exit criteria
<Sharon> https://
sharon: url above tries to summarize the open issues. It looks like we may have closed #170 prematurely
sharon: reads notes from above link that relate to meetings with TAG
<Sharon> https://
sharon: issue #170 was closed by John; there were discussions on distractions and overlap with media query; TAG had concerns about media query features that already include user preferences. This is in relation to issue 146
sharon: TAG's issue 476 raised concerns; We raised ADAPT issue #170 to address these and 170 got closed without complete resolution
sharon: TAG closed #476 but we still need to address sensory issues; our 170 was about that distraction values needed to be updated
sharon: our issue 170 links to content module 1; We said that we added values but new values are not showing up in our draft.
sharon: Do we still need to compare MQ5 with what we have and meet with that team
Janina: We must address this before we can move forward; APA and CSS always meet at TPAC so we can address there; We don't intend or think that we are clashing with CSS
sharon: On May 28, 2021 - nothing had been added due to reduced motion; we are giving metadata control at the element level vs CSS which provides it at the page level - this is key.
Janina: we need to clarify and verify there is no overlap. To reiterate, CSS only gives override at the page level; ADAPT is facilitating more granular change at the element level which is clear
Janina: will work with Matthew to schedule time with TAG at TPAC
charles: in #170 we see the samples are done but we don't know where those are; Seems we need to create an example with two audio type distractions that we want to handle differently in different sections of the page
Lionel_Wolberger: agree that working code always works best, curious why picking audio vs visual
CharlesL: I believe 170 referred to audio or tactile
Lionel_Wolberger: I was thinking of a timer and a carousel (for visual)
sharon: I think we went towards audio because media queries focuses on visual; we wanted to show this is more than just visual so suggested audio
becky: remembering that discussion but not sure it was related to 170
<Zakim> janina, you wanted to say it could be either, and both would be best
Lionel_Wolberger: I have seen pages with timers and carousels and other distractions on the page, where it would be useful to keep the timer and not the others
janina: basically agree that we need examples; timers are covered by aria-live for screen readers; but a smarter countdown (that limits the number of interruptions until the time is near end) would be useful
sharon: media query does have a session timeout option - the amount of time but not an ability to change the setting
janina: WCAG 2 is problematic on the timeout issue - it requires 20 hours of open session which is not realistic to maintain security/privacy
janina: I recommended solution to allow user to save data and come back to it
sharon: looking at issues 170 and TAG 476 it seems we need to reopen 170 and revisited
janina: yes, reopen 170 and find distinction from Media queries via examples and we do need to connect with TAG at TPAC
Lionel_Wolberger: distracting advertisements are an issue
sharon: be we had a long discussion about that because advertisements provide revenue
Janina: they can be distracting but they can also be informational; allow people to look on their own time
sharon: in 170 we talk about audio and tactile and wanted to add values for those and remove the visual values and let CSS handle
janina: but John is correct that CSS only handles page level, we need to handle element level
sharon: examples include mp3; animated gif; countdown widget, stock ticker
CharlesL: in looking at tag 476, TAG encouraged us to open an issue with CSS to discuss overlap between MQ5 and ADAPT
janina: Media queries is a spec. produced by CSS; features in MQ5 were discussed at TPAC in Lisbon
Janina: should discuss with CSS that MQ5 features are page level; they have other features that are element level, why not some of the distraction ones? Should clarify that
Lionel_Wolberger: short window to develop examples for TPAC to show element level distraction issues
<Sharon> https://
janina: stock ticker seems like least controversial example
Sharon: link above gets you to section of document for example
sharon: BCI issue
Janina's action on BCI
Charles: back to examples; you are on a trading web site with a countdown timer and a stock ticker running at the same time (the countdown for how long you have to complete the transaction)
Lionel_Wolberger: on a stock page with a stock ticker running and you are purchasing a seat at a webinar
BCI
janina: we need Russell from BCI to have something formally documented between W3 and Bliss to use their index; Director wants a normative reference; We don't want PDF, excel is better, CSV is better; Need Russell's help to write the spec
janina: action for ADAPT is that we need to begin on a registry spec
Lionel_Wolberger: I have agreed to work on that
Janina: we just need to define the spec; we don't have to address hosting
janina: is a normative spec
janina: we get to define the format; there is a registry in the W3C process so there must be/have been a group that wanted it;
CharlesL: CSV format is a good suggestion for being able to easily map
janina: also avoids vendor lock in to Excel
Lionel_Wolberger: I would like to have a registry draft spec for TPAC
janina: we should at least have the requirements laid out; then writing the spec won't be hard
janina: suggest working in git
Janina: we need to take this registry through the W3 process and then we can reference it in Adapt 1.0
Janina: we can go to 1.0 without the registry fully complete, but we will likely get more uptake if we also have the registry completed. It shouldn't be too problematic
janina: history of how registry came about should be documented in W3C process community group
Lionel_Wolberger: would be helpful if there was a spec that resembles this; are we just defining a database scheme?
janina: yes, a database schema;
janina: we are defining a standard for Bliss symbolics
Lionel_Wolberger: an example would certainly help in defining a new registry;
group agrees, great forensics by Sharon!