<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 ...