March 20, 2019 ARIA and Assistive Tech Community Group

20 Mar 2019


Matt-King, Michael-Fairchild, Yohta
Matt King


CSUN presentation

<mck> http://a11y.pro/csun2019/

<scribe> scribe: MF

mck: gave an overview of the CSUN presentation. Discussed each slide.
... slide 19 - our initial target browser set
... side 20 - for every observed behavior, is the level (quality) of support appropriate, missing, or incorrect?
... example: radio groups and the behavior around aria-checked. it would be a "must have" that the state be conveyed. If JAWS says "checked" for native radio buttons, then it should announce the state the same way for ARIA. "appropriate", "missing", or "incorrect" describes the quality of the information is conveyed. For example, if the state of a checkbox is conveyed by JAWS as "selected", the importance would be met, but the

quality would be incorrect (should be "checked"), but at least a state was conveyed.

mck: discussed how scoring of these factors might work. 100% would be if all of the minimal requirements were met. You might get a higher score if "should" or "may" assertions are met. Another approach might be to convey an independent score for each group of assertions (one score for "must", another another score for "should")
... we could give negative scores for assertions not being met, or incorrect support. We could also floor to zero.
... a single failing assertion could result in a zero score

<shimizuyohta> Matt: Concern is after spending time dividing scoring rule, finding screen algorithm doesn’t represent reality.

<shimizuyohta> Michael:Needs some specific example would be needed to test and validate the scoring algorithm

<shimizuyohta> Matt:[p.23] Two important precondition are Screen reader 1.mode 2.setting 99% are a response to keyboard command

matt: discuss next steps. Wrap up exploration.

Matt and Michael: focus on applying the methodology and scoring to a simple example like a checkbox so that we can create an informed data model

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2019/03/20 17:00:10 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: Matt-King Michael-Fairchild Yohta
No ScribeNick specified.  Guessing ScribeNick: michael_fairchild
Found Scribe: MF

WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)

[End of scribe.perl diagnostic output]