Silver Conformance Subgroup

18 Feb 2020


jeanne, Makoto, sajkaj, AngelaAccessForAll
Joe_Cronin, Peter_Korn


<scribe> scribe: sajkaj

<jeanne> https://docs.google.com/document/d/1LfzTd_8WgTi0IUOOjUCRfRQ7e7__FRcnZow4w7zLlkY/edit#

<jeanne> We need to get the critical path of the organization’s scope. It doesn’t impact the score, but it gives an organization the pass/fails where it counts.

<jeanne> We need to get the critical path of the organization’s scope. It doesn’t impact the score, but it gives an organization the pass/fails where it counts. It isn’t tolerable to have a lower score on a critical path. For example, on the critical path, you would need 90% to pass and 85% on the rest of the site.

js: Notes unit of scoring varies
... Some are clearly page -- focus order, lang of page, time-out extension
... Some are instance based, alt on images

Makoto: Lasy out an example of a few items being in the wrong focus order out of dozens that are in correct order

js: Or keyboard trap? What should that be?
... We're coming down to more discussion on these.
... Suggesting perhaps all after the keyboard trap failure fail

<jeanne> Needs more discussion - maybe a percentage of focusable elements not impacted by the keyboard trap.

angela: Are we likely to have showstoppers for every disability type?

<jeanne> https://raw.githack.com/w3c/silver/ED-draft=comments-changes-js/guidelines/index.html#scoring-conformance

js: Not sure how much this has changed since our last meeting
... Added some headings and explanation for scoring conformance
... Notes Angela has contributed a plain language pass on the entire scoring and conformance section
... Discusses additional tweaks ...
... As she reviews notes needs clarification in structured sample ...

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: 2020/02/19 01:01:42 $

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)

Succeeded: s/kd/angela/
Succeeded: s/section/sample/
Present: jeanne Makoto sajkaj AngelaAccessForAll
Regrets: Joe_Cronin Peter_Korn
Found Scribe: sajkaj
Inferring ScribeNick: sajkaj

WARNING: No "Topic:" lines found.

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: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report

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]