Meeting minutes
<Github> https://
<Github> https://
TPAC update
<Github> https://
Matthew: WHATWG - told us to file an issue to get a prefix. Simon who is in the WHATWG and W3C did a search and "adapt-" and only found very rare cases of it being used and felt that we should ask for it.
… , Good talks with Andrew Kirkpatrick get an MVP for coga style use-cases vs. more personalized ergonomic personalization. Some people this is a critical access issue.
… , CSS may have some crossover, with simplification with smaller view ports. Explore with Media queries to see if its appropriate.
<matatk> Demo page: http://
Matthew: , few things to explore with CSS.
Janina: IOS 16 are advertising simplification, focus filters for simplify your views.
Matthew: File issues and engage with us was the take-away from TPAC.
TAG update
Sharon: TAG did like the direction we are going the problems we are solving. On their end was some process issues. W3C are handling those issues. mistakes made which cause some churn, but these weren't pointed out when the issue was closed.
Janina: Draft CR as it is now is Dead in the water. Why that happened? - Process flaw which Judy will work with TAG on this. We were looking for open issues but was a close with concerns. They didn't see user need / community engagement etc.
… , TAG did like Symbols and architecturally ready. Everything else needed more work.
Sharon: This really affects how this affects CR.
<Roy> https://
Sharon: , this explains the whole meeting.
Becky: In that TAG meeting. We should be looking at ARIA. I keep hearing, I though ARIA was screenreader only. Can anyone clarify?
janina: They did have a general over this. They were confused what we do vs. ARIA does, two attributes with the same name.
Becky: ARIA is for SR only.
janina: that became the default over time. When Alice left, there are no accessibility person on the TAG. So they lost that knowledge unfortunately. We need to get a11y experts into the TAG.
Becky: wonders should we focus on symbols now?
… , substitutions, textual - they didn't seem to get that, TAG thought you can do this with other technologies.
Janina: Alice did a lot of good for a11y, and she does not know this area. Advertising is dead. we can't have that our example. I should have seen that earlier. They relied on her but she is now gone.
CR Next steps
Sharon: There are a lot of issues, but separation for CR with symbols by itself is our best option at this point. We need to engage more with other groups. CSS, ARIA. and issues around advertising.
… , is it a resolution?
Janina: we want to end today with 2 resolutions, 1. break out Symbols, and new explainers. I was stunned they thought we didn't engage the community.
… , since they said "This is well developed" lets get that into the pipeline. 2nd is to file "adapt-" with WHATWG.
Matthew: I felt action, destination, purpose are related to symbol, there are still some issues around them.
… , action, destination, purpose has ? around them. If we go head with just symbols. if we feel afterwards in a 1.1 update we can add those but naming the first spec will be important.
… , if we feel they are related.
<matatk> https://
Matthew: , we would have to also file an issue with HTML as well.
… , we may need to have a Call for Consensus. We need to ensure this is extremely clear. ie. why aren't we asking for symbol- vs. adapt-
Janina: we don't have to do this today as we will need to rename things, and how we have a path fwd.
Matthew: we need to file an HTML issue to get the "adapt-"
Janina: we may need to engage Michael and perhaps Philippe.
<janina> DRAFT RESOLUTION: WAI-Adapt will revise its Content Module draft to focus exclusively on AAC Symbols, as these were seen by TAG as most ready for standardization.
<janina> +1
+1
<mike_beganyi> +1
<Sharon> +1
<Roy> +1
<matatk> +1
<Becky> +1
RESOLUTION: WAI-Adapt will revise its Content Module draft to focus exclusively on AAC Symbols, as these were seen by TAG as most ready for standardization.
<janina> DRAFT RESOLUTION: Moving
<janina> AAC Symbols to CR first also requires we write a TAG explainer and a Public Explainer expressly for AAC symbols.
<janina> +1
<mike_beganyi> +1
<matatk> +1
<Becky> +1
+1
<Sharon> +1
<Roy> +1
RESOLUTION: Moving AAC symbols to CR first also implies we will write a TAG Explainer and a public Explainer expressly for AAC symbols.
<janina> DRAFT RESOLUTION: Move expeditiously to formally request the Adapt- prefix as a reserved prefix from WHAT-WG.
Matthew: when we file this we need to establish we have a pipeline of additional attributes to include in future specs.
<matatk> +1
+1
<janina> +1
<Becky> +1
<Sharon> +1
<mike_beganyi> +1
RESOLUTION: Move expeditiously to formally request "adapt-" as a reserved prefix from WHAT-WG.
<Roy> +1
<Github> https://
Janina: I will take the drafting of the two explainers. first cut author.
Matthew: It seems to me, we have a couple different threads, work on things like CR repackaging, registry at WG level, and have things like feedback / questions to address micro formats. etc. I can look into it over the next week. Exploring things in CSS etc. option to focus on other things so we don't loose momentum.
Janina: we did look at microformats
Matthew: we did but they asked specific questions so things may have changed since we last looked at it.
Sharon: it should be on our wiki.
Matthew: Yes exactly. looks like many parallel things. ARIA/ Microformats, social demographics etc. Recruitment for additional participation.