Meeting minutes
matatk: This is really just about learnign about the DAF work.
matatk: Rachael will give us the background on it and the rundown as it were.
Rachael: Thisis a prject from Accessible Communit. It grew out of our need for work to do search for organizations within the community that support the disabilities of people we work with.
Rachael: We needed something above and beyond the FAST. Also, I teach at UML and we needed something, too.
<shawn> s/ matatk Rachael will / matatk: Rachael will
Rachael: It also addressed concerns i was havinga thte time around the challanges of approaching the entire digital space, not just hte Web.
Rachael That's a very brief contextation of the whole thing.
Rachael: Michael Cooper is the project lead on it.
<Rachael> Michael Cooper, Bern Jordan (Professor with TRACE at university of Maryland and MIDA)
Rachael: We've had three rounds of contributions. Alasait Campbell, Joshue O'connor, Jean Spellman, Greg Vanderheiden etc.
<Rachael> accessiblecommunity.org/daf/framework
Rachael: This should be fully accessible.
Rachael: A11y guidance is developed after problems emerge.
Rachael: We codify what is already being created.
Rachael: Guidelines don't predict issues as new technology evolves.
Rachael: That is some of the background for why DAF came into being.
Rachael: A11y guidelines development is most focused on creators.
Rachael: This has pushed us to think about other solutions ot take. If we could push it lower in the stack, that would be more efficient.
Rachael: We want to focus on emerging technology.
Rachael: One need is to figure out what emerging technology needs before it develops.
Rachael: We've rewritten this from scratch based on what was out in the world thre times right now (see above).
Rachael: The highest level view. We have three boxes in a horizontal row. In the letmost box there are individual characteristics, the rightmost box object characteristicsx, and in the middle is the support needed.
Rachael: The framework is more accessible than the slides.
Rachael: See link, otherwise.
Rachael: The middle is the connective tissue, so to say. What do we do to support people?
Rachael: Under individual abilities/chracteristics: they can be senrosy, cognitive etc.; object characteristics are a pretty direct mapping to WCAG (sensory would map to Perceivable; physical to Operable; cognitive to Understandable.)
Rachael: Within the middle there are five diffeent ways to match: assistive technology, adjustmenbt, alternative, avoidance, or range (as a default).
Rachael: There are two types of object characteristics that have a one to many mapping: task compltion (Efficiency and Physical Location (glare, noise etc.)); and the other is safety (social constructs (financial impacts etc.) or technical (algoriths etc.)).
Rachael: This is how you map it out. Within these areas tehre are subsets of items to run through if you like.
Rachael: The next thing (subests): Sensory: Auditory, gustatory, olefactory, visual etc. Just because we don't have taste in thedigital space, this doesn't mean we can't or won't have it in the future. You do see things in this framework that aren't in the digital structure today.
Rachael: Within physical we have balance and stability, multidimensional body movement, physical attributes (like not having a standard facial configuration), reach, stamina, strength...
Rachael: Cognition: ability to understand implied content, contextual knowledge, executive functions, language skills, learning, memory, mental health, self regulation, sensory processing etc.
Rachael: Object characteristics: task completionand safety; cotent can be change of content, multidimensional content, location, notification, static content, strucutre and relatiosnhips, and time based ocntent; operable: binary, biometric, key based, motion, path and voice based; understandable: auditory, gustatory, implied, language based,
numbers and numerical inforamtion, olefacotry, tactile and visual content.
Rachael: After task completion and efficiency we have difficulty, inaccuracy, etc. Physical: glare, lighting, noise, physical operation, space, etc.
Rachael: Safety: safety, privacy, social media use, etc.
Rachael: Many difente flavours of algorithsm are mapped to.
Rachael: We have mapped into this framework WCAG 2.2 A, AA, AAA. ISO, UAAG, a really long lsit of standards; kisok a11y standards from ADA, 508...
<Rachael> https://
Rachael: There is an actual matrix. It's a multilevel framework that can be explored in different ways.
Rachael: We#re finalisign the mapping and the guidelines. We want to tie new research into these cels. We want to find out where the holes are.
Rachael: We want ot make sure we're adding dimensions we're missing.
Rachael: I've put a slide up now which is kind of a goal long term that we will have a user needs statement.
<Rachael> https://
Rachael: We have put this out as a public resource. we are working to get the funding for the rest of the work.
Rachael: That is our work for the coming months.
Rachael: As much or as little as you want to use it, it is afailable.
Rachael: AT the time we started this, it was not an option to take a larger view in teh W3C.
Rachael: "How can it help the W3C?" may be a good question.
shawn: Is there a role for FAST?
Rachael: We based this on seeral different models, FAST being one.
Rachael: I don't know in which ways there may be intersectiosn.
Rachael: It's intendede to be a iving document, however with a goal of being done at some point.
Rachael: The research supplements to it and the cell contents would evolve over time. It it sinteneded to be arather comprehensive top-down thing
Rachael: It is meant ot be a pretty logn term fixture.
matatk: Individual Ailities: I don't know if the listed abilities are multilevel/hierarchical or single-level. I believe the FAST's correlate to that were derived form teh wHO's non-public definitions. Are the DAF's a list or a tree?
Rachael: It's a shallow tree. Sensory: Auditory, gustatory, visual... but we're not going below that.
Rachael: More in the link.
<Rachael> https://