Brainstorm & document open questions on conformance

Content migration from WCAG to Silver

https://docs.google.com/document/d/1aCRXrtmnSSTso-6S_IO9GQ3AKTB4FYt9k92eT_1PWX4/edit#heading=h.yb575k8cuplm

<Lauriat> Where we left off in WCAG: https://www.w3.org/TR/WCAG21/#seizures-and-physical-reactions

WCAG to Silver Migration Outline

<Cyborg> didn't know meeting was happening today, just found out. if there's a link, can you please repost? thanks.

<KimD> We're working on https://docs.google.com/document/d/1aCRXrtmnSSTso-6S_IO9GQ3AKTB4FYt9k92eT_1PWX4/edit#heading=h.yb575k8cuplm

<Cyborg> what # are we on now?

WCAG 2.3.3

<KimD> @Cyborg, at the end of the google doc

<Cyborg> Re: vestibular concerns - how does VR fit with this SC?

<Lauriat> https://www.w3.org/WAI/WCAG21/Understanding/animation-from-interactions.html

VR would be a Method related to this Guideline

<Cyborg> i think important to flag it.

<Cyborg> i've seen "accessibility tours" done only through 360 view, and it is nauseating and disorienting, both for vestibular disorders as well as cognitive disabilities

<Cyborg> and no alternative provided to inform people about accessibility - ugh

<Cyborg> providing information that is equivalent, without having to use the motion version

Shawn: protecting users from motion that is the result of their own activity needs to be prevented or canceled. We could merge with Pause Stop Hide

<Cyborg> plus warnings about vestibular risks before you click on it

Shawn: it is an example of a Method applying to multiple user needs
... both motion and distraction/interruption

Jeanne: The wiki page where we are storing new ideas for Content <- https://www.w3.org/WAI/GL/task-forces/silver/wiki/Disabilities_for_Inclusion

https://www.w3.org/WAI/GL/task-forces/silver/wiki/Potential_Guidelines_in_Silver

s|Jeanne: The wiki page where we are storing new ideas for Content <- https://www.w3.org/WAI/GL/task-forces/silver/wiki/Potential_Guidelines_in_Silver

WCAG Guideline 2.4

Bypass blocks should also include expand or show hide or simplify the screen or context. Should also include single page

<Lauriat> Rewording with the qualifier removed: "If the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability."

<Lauriat> The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.

<Chuck> +1 to that

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)

WARNING: Bad s||| command: s|Jeanne: The wiki page where we are storing new ideas for Content <- https://www.w3.org/WAI/GL/task-forces/silver/wiki/Potential_Guidelines_in_Silver
Present: KimD dboudreau CharlesHall Lauriat JF Cyborg AngelaAccessForAll
No ScribeNick specified.  Guessing ScribeNick: jeanne
Inferring Scribes: jeanne

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 19 Apr 2019
People with action items: 

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