Meeting minutes
Jake: in general, in the last few calls it's clear that a structure and relationship is not clear. Should we do experiments? Mapping between outcomes, guidelines, user needs
… in various groups. We need to have that conformance model and structure in place
… decisions made to start a group on structure of guidelines, another for conformance, another for processes
… have shared some work from the attempt to produce master list of functional needs
correction, the master user needs list
<JakeAbma> https://
<JakeAbma> https://
Detlev: Have questions about the granularity of overall structure within WCAG 3. Last comments on the mapping document were 2 years ago
Kim: need to figure out the granularity-related questions
Detlev: what are the potential benefits of reorganizing the material we've had for years. An exercise around core functional needs and outcomes eg. activation and focusing
… crucial things which is difficult to tackle because of the complexity depending on the mode
… regarding this cluster of concerns, what are the outcomes/
… is the outcome the element can be activated - with screen reader, with tab, with speech
… higher level outcome that breaks down the mode, technique
… lacking basic understanding of the overall scheme before doing a 1:1 transfer from 2.1
Kim: Looking for emails re: granularity
… and open to doing work in a different way
Detlev: other group has aspects that can be tested in atomic ways
… when the more complex and important ones that can't be tested as well yet aren't
Jake: this sounds like a change from the second conformance testing group
… they are working on the more technical parts of ACT
Jake: I have been working on other aspects, which might help address some of these concerns. Will be presented in the larger group
KIm: We need the resources
… can you out in a pointer to the presentation, Jake?
Spreadsheet with user needs was useful for people
Kim: You are in another level
… we should also look what's new in the OSs
Jake: presentation is not online right now
Kim: can you email?
Jake: yes
<kim_patch> Jake is going to give us a brief version of his thoughts on user needs
<kim_patch> Jake: challenge that we are trying to solve is to put people up front in both the fast group and silver. Create guidelines or methods or proof points – give them a name from within the human beings – the people
<kim_patch> functional needs, I call them user functions. Those 54 also created in functional needs group
<kim_patch> Detlev: Can you hone in on the outcome
<kim_patch> Jake: 14 main categories and 54 subcategories
<kim_patch> Jake: on the other side we been working on what is a user need – performance, error prevention, all have different ways of defining a user need
<kim_patch> Jake: we have been focusing on what is the master user list. Those two together, the Function list and the user list create the requirements
<kim_patch> Jake: I'm blind or I have a motor requirement And I want to operate – what are my needs
<kim_patch> Jake: are we on track for a master user needs list?
<kim_patch> Detlev: I don't see this is the main problem whether we have more or less or split the user needs differently – I don't see how the outcomes are related
<kim_patch> Jake: I've been trying to search for a very simple formula everyone can understand
<kim_patch> Jake: Added personalization
<kim_patch> And discoverability, Distractions
<kim_patch> What are the requirements – that is the user outcome
<kim_patch> Jake: I just placed the user functions at the top of the spreadsheet and the user needs master list in the first column of the spreadsheet
<kim_patch> Jake: in every cell where they intersect I add the requirements for that intersection
<kim_patch> Jake: so if you are blind and using a screen reader you need text-to-speech or maybe braille, must be depth independent – just the basic stuff what is the requirement for that intersection for user to perceive content
<kim_patch> Jake: this is just one very simple formula is a function, user need, all the requirements – I started working them out in the spreadsheet
<kim_patch> Jake: this formula of having a functional need having a user need and Where they intersect is very clear
<kim_patch> Jake: I tried to put error prevention in this document. Only the bold ones are pretty mature. Error prevention is all about instructions. Synonym to prevent errors. I've been going through the error prevention work and I came back with six out comes
<kim_patch> Jake: the guidelines are basically just an outcome but error prevention with synonyms, that's the endgame of my story – we were looking for a framework structure to place those functional needs on and to come up with outcomes. The master user need list – they are like guidelines. Users can orient themselves in immersive environments, can operate navigation, can perceive changes the content, can perceive content. Those are like guidelines [CUT]
<kim_patch> Jake: our structure is we can use the renewed core principles – perceivable operable personalization understanding with user needs
<kim_patch> Jake: so we don't talk about methods, not descriptions, not how to's, just this list.
<kim_patch> Jake: I worked on can users perceive content today
<kim_patch> Detlev: I'm still struggling where Touch input, speech input comes into this
<kim_patch> Jake: we are at the layer were we don't need to talk about methods –
Action: Jake to write an email explaining briefly a proposed useful task for MATF that has to do with line 15
<trackbot> Created ACTION-98 - Write an email explaining briefly a proposed useful task for matf that has to do with line 15 [on Jake Abma - due 2021-09-16].