W3C

– DRAFT –
(MEETING TITLE)

21 October 2021

Attendees

Present
avneeshsingh, becky, jasonjgw, Jaunita_George, Jemma, Joshue108, Matthew_Atkinson, MichaelC, shadi, stevelee, SteveNoble, Todd
Regrets
-
Chair
-
Scribe
becky

Meeting minutes

Joshue108: Welcome and introduction

Joshue108: using IRC and chat in zoom for questions and discussions. Will start with an introductory presentation followed by open discussion

Joshue108: introductions

Joshue108: FAST = Framework for Accessible Specification of Technologies - advise tech spec creators how to ensure technology meets needs of users with disabilities;

<Jaunita_George> Can you post the checklist link here?

Joshue108: FAST components - checklist to aid review of technologies for what is relavent or not to people with disabilities and how well it addresses those needs

Joshue108: goals: provides guidance to tech developers via a list of user needs

Joshue108: used for: gap analysis, identify where functional needs and outcomes overlap; matrix to address user needs for emerging tech; creation of new a11y requirements and techniques for WCAG 3

Joshue108: working on FAST in functional needs sub-group

Joshue108: have been updating comprehensive list of user needs

Joshue108: URI to list available within presentation deck

Joshue108: discussion around what is a user need; user needs statement format; intersectional needs

Joshue108: intersection of user needs between groups is the sweet spot - important to identify those intersections

Joshue108: feedback from silver task force noted areas that were missing: mental state, stress, etc.

Joshue108: reviews FAST definitions: discusses functional need; intersectional need; user need statement

Joshue108: current user need statement draft is: "A statement that describes what a user needs, on a high level, in context with a principle."

Joshue108: reviews matrix methodology

Joshue108: user outcome definition: User functions combined with user needs leads to user outcomes that reduce barriers

Joshue108: reviews an example of user need: perceivable

Joshue108: and user function: hearing & auditory. Discusses the outcomes

Joshue108: showed example of user needs and functions within rows and columns of excel sheet

Joshue108: reviews questions: how to define context?

Joshue108: how to deal with high level sets of intersectional outcomes that are identified?

Joshue108: how to define a methodology for referency parent/child relationships

Joshue108: how to define methodology for gap analysis?

<Jemma> can Josh reexplain the "parent/child" relationship?

<Jemma> I could not hear due to noise

Joshue108: request for involvement

<Jemma> yes, Josh's answer was helpful.

MichaelC: we want to put all of this content into a database to get inter relations and intersections;

Joshue108: looking to get feedback on FAST and where people see opportunities for use;

<Zakim> Jemma, you wanted to ask about data structure - matrices vs parent and child relationship - and how this will be used in practice.

jemma: believe parent/child relationship is important but also hear that there are parallel structions. how to solve conflict between hierarchical and matrix based relationships

Joshue108: ultimately these things are abstractions - we need to hear how these are reflected in various technologies

Jake: most important outcomes is to keep the formula clear, clean, simple. Is difficult when have multiple functional needs that vary by time of day, year, circumstances

jake: looking for more abstract layer of user needs and functional needs - ends up a stacking of user outcomes that vary by situation. We define high level

Joshue108: stacking up varying user needs at high level

<Zakim> tzviya, you wanted to ask how this is being used

tzviya: how is this set of documents being used; checklist looks daunting for a spec. author; what is experience of the checklist being used? Do people know this exisits?

MichaelC: FAST checklist are foundational materials that have existed; we are using this as a basis for ongoing work. We do plan to update the checklist as we go further.

Joshue108: some groups use the existing checklist now

shadi: believes there is a UI redesign of the checklist underway to make it easier to use?

Joshue108: we did develop a prototype app to make it easier to user; there is a need for tooling

<Jemma> I think the relationship between user needs to funtional needs is one to many.

<Jemma> relationship

Joshue108: FAST has many potential uses: gap analysis, need for additional WCAG techniques or success criteria

Minutes manually created (not a transcript), formatted by scribe.perl version 136 (Thu May 27 13:50:24 2021 UTC).

Diagnostics

Maybe present: Jake, tzviya