Meeting minutes
<Lionel_Wolberger> /invite zakim
<Lionel_Wolberger> /invite rrsagent
New Zoom for APA meetings (Wed)
Lionel_Wolberger: New zoom link forAPA meetings update your calendar invites.
<Lionel_Wolberger> The updated APA zoom is on this page, https://
<Lionel_Wolberger> Lionel tells everyone, APA Zoom meeting zoom starts with 982 from now on
Lionel_Wolberger: CFC, 5 responces, 4 were A, and 1 was for B
of the A's 1 said they can't live with the other. 1 didn't answer.
1 vote for APT, but can live with the other.
clear vote for ADAPT
CharlesL1: Did we ask about upper or lower case?
<CharlesL1> Charles: upper/lower case
Janina: we didn't
Janina: We aim to reach consensus. We may need some further discussion, and have a little time to do that.
Janina: The WAICC call is this Wednesday, and facilitators are welcome, we could have sharon and Lionel_Wolberger join. Would like to have another chat with EO.
<CharlesL1> ack, me
Janina: I am concerned we're taking on _all_ of "adapting". We do need the expansion for our first slide for presentations. Whatever we adopt.
Lionel_Wolberger: John, voted for WAI-ADAPT, I can live better with WAI-Adapt.
<Lionel_Wolberger> John wrote, FWIW, I can live with WAI-ADAPT, could live better with WAI-Adapt (case sensitivity), and strongly oppose WAI-APT (what's a WAI Apartment?) (I recognize I've been MIA for a number of weeks now dealing with some personal issues, and was not part of the larger discussion here, but overall I remain fundamentally disappointed with Adapt as a new identifier. I would have preferred something that alluded closer[CUT]
<Lionel_Wolberger> than adaptability, but... that's just me. At the end of the day, we are customizing the UI/UX, but not really impacting the way users can or will interact with it, which to my mind is what adapt suggests - i.e. our work mostly falls under the WCAG Principle of "Perception" and not "Usable". For example, our attribute "destination", when used, makes it easier to comprehend or perceive where or what the destination is, [CUT]
<Lionel_Wolberger> are we modifying the destination or even for that matter the UI - it *might* change the UI, or instead the attribute and value may only be processed by AT.)
<janina> https://
CharlesL1: I understand John's concerned that things like 'destination' are not conveyed within ADAPT. I think they are considered, as e.g. icons can be placed in the page to represent those destinations.
… Therefore we _are_ adapting the UX in those cases.
<janina> +1 to Charles. It's all about adapting what the user experiences
<Lionel_Wolberger> +1 to Charles saying, even 'destination' has aspects of adaptation (depending on what the user agent does)
CharlesL1: We don't know what the UI is going to look like, and could well be making adaptations.
CharlesL1: We can debate upper/lower case, and the needs for the slide deck.
<Lionel_Wolberger> https://
CharlesL1: E.g. "DAISY ACE" is now "DAISY Ace" [it's an ePub accessibility checker]
CharlesL1: I'm fine with ADAPT or Adapt. Maybe for EO to guide us.
sharon: We were going to do the expansion so it looks better on the slides so uppercase would make more sense.
Janina, we also talked about AdaPT
Naming progress, status of EO effort
Matthew_Atkinson: This topic should have been at the top of this conversation. zakim issues with closing previous topic
Janina: Adaptable Personalizable Technologies
… , user experience is an adaptation.
… , we need wider buy in, not EO / APA / ultimately Judy needs to sign off on this ie. WAI
… , I can live with ADAPT, Personalization is claiming too much and this has has a lot of the same characteristics.
<Lionel_Wolberger> Camelcase: adAPT
Lionel_Wolberger: I don't like the up/down of camel case. adAPT would be my vote.
Janina: I don't think camel case will work but love playing with the options.
<Lionel_Wolberger> Expansion as camel case: ADAptable Personalizable Technologies
<Lionel_Wolberger> The ADA pops out to remind us of Ada Lovelace and the ADA
Janina: , remember the reason for expansion something like CSUN show what it does.
Lionel_Wolberger: ADA as (love Lace) or just US ADA :)
… , are we accepting this expansion?
Matthew_Atkinson: does EO aware of the ADAPT group? maybe a call with WAI call discussion.
Lionel_Wolberger: who will report back to EO? Janina?
janina: Yes
Lionel_Wolberger: the expansion does apply either way. ADAPT or APT
Janina: I will bring this to WAI and EO
Zakim: next item
Content Module Implementations Status (Follow-up on issue #144 and issue #203)
janina: There is an issue regarding our example with a recipe. I am inclined to bring this up tomorrow. Roy said one more week, that week is up. We noted we are marking up a recipe.
Matthew_Atkinson: a transfer from another repo, APA "Ham Sandwich".
janina: where does it say to respond below our abstract?
Matthew_Atkinson: published by APA, there is no text about responding. there is no github link. this came from James Craig. Latest editors draft does not.
… Regarding issue 144, I agree with Janina. I think they don't realize that the rendering is still in flux. I think until CR these issues can be addressed. This has to do with rendering which we shouldn't be held to at this point of time.
Janina: we feel this is an implementation issue which is a CR issue. we can easily demonstrate this was a known issue a long time ago.
Lionel_Wolberger: should we reply to them? We have talked to the community who needs symbols and that is needed not on the sentence level but for procedural.
Janina and note we brought this up in december.
Lionel_Wolberger: the rendering should be optional at this point, Dec. 8th they had access to the XML.