- From: Joshue O Connor <joconnor@w3.org>
- Date: Tue, 15 Feb 2022 15:02:41 +0000
- To: public-a11y-functional-needs@w3.org
Hi all, No rrsagent in channel, so here are the minutes below: Note - there will be no meeting this Thurs. Next meeting on Tues 22nd. Thanks Josh Meeting: Functional Needs scribe: Joshue108 JOC: Had a look at the Personalization suite and I added some draft essential needs to the matrix https://www.w3.org/WAI/personalization/ JOC: Where were we at from last week? JA: We did 70% of error stuff last week.. JA: Gives update to Michael.. I walked thru the sheet last week to explain some of the thinking of the Error sub group and their related outputs. The creation of a structured list of outcomes We look at where errors occur and when outcomes are needed. Ways and methods of applying outcomes etc Josh and I reviewed the outcomes last week - and today we want to look at the comments in Red JA: I've added notification provided stuff etc - and again to give overview and add to the working sheet. — @Joshue108 thanks Jake <@Joshue108> Joshue O'Connor MC: Is absorbing.. JA: Continues on.. Reviews error recovery and correction items.. Has some questions.. The outcomes in the list - I want to see if I can group them.. <riffs on grouping options> Some relate to notification It is hard to see if the outcome if part of the user need - user can recover from errors, or present error (as a part of percievable) Which is correct? Isn't providing overview of errors a part of understandable. q+ to discuss intersections between user functions and outcomes JA: Similar to where contrast is needed - labels and inputs etc These are not a part of users get instructions for interactions et s/et/etc q? JOC: discuss intersections between user functions and outcomes How should that be defined in this document or a DB? JOC: So I want to hear from Michael.. MC: Regarding this - there are two levels, outcomes that are a part of percievable that feed a meta outcome that is understandable So the parent can be percieveable with the extra or meta being defined as overlapping or related; MC: We may have more meta outcomes. JOC: That could be what Jake is worried about.. JA: I'd like to not mix them - but present error is purely presentation - either visually or via prog determination.. JOC: Yeah. JA: I've taken all the items and placed them in one cell. We can explore the items in column B - if we find the spot for the first 5 outcomes as percievable - but tag them as recover from errors.. Then they can be labelled etc JA: Other items are related - description or error is separate from presentation. Should they be in different spots? MC: The goal of minimizing duplication is paramount. So its best that they are correct - we can tag There may be meta outcomes.. So methods support outcomes - you can have outcomes supporting outcomes also. Is that correct? We have solutions to this. JOC: So Jake e'thing is in one bucket? JA: Yes - I'd like to redistrbute.. JA: I propose they are grouped and then tagged/referenced JA: Lets discuss CAPTCHA, speech alternatives etc I've discussed this with Sarah Horton etc They have not been looked at previously.. JOC: Is the CAPTCHA one, going to OTBE in terms of server side fixes to CAPTCHA security? Will this still be relevant by the time we are ready to publish this stuff? JA: If it is still in use then we need an outcome. CAPTCHA is interesting, even from a personalization angle.. https://www.w3.org/TR/turingtest/ <Discussion on CAPTCHA> JA: Some things may be abstracted.. MC: We shouldn't tie outselves to the technology So lets keep it at a user needs level. JOC: So a review of user needs relating to CAPTCHA would be good - these can be more generic — @Joshue108 sounds good <@Joshue108> Joshue O'Connor JA: I've like to place these in an another place JA: They can be tagged for the moment by way of explanation. <Riffs on where to put the CAPTCHA related stuff> — @Joshue108 sounds good <@Joshue108> Joshue O'Connor JOC: +1 to cutting up the CAPTCHA outcomes mc: regarding gathering user needs, generic is best here a la wcag 3 that may not be understandable... intersections can be reworded do try to consolidate but they may no be used in that format in public guidelines etc ja: tagging will show where they are.. no meeting this thurs, next meeting on Tues 22nd Thanks Josh -- Emerging Web Technology Specialist /A11y (WAI/W3C)
Received on Tuesday, 15 February 2022 15:02:46 UTC