CAPTCHA draft - revision and research

<scribe> scribe: janina

OK, David!

jgw: Need to make decisions on next steps
... Lots of commonality in comments
... One more interesting comment relating to privacy

<jasonjgw> Janina plans to consult the APA Working Group regarding the reordering of sections in the document.

js: Asks the why of reordering

jgw: Intent was to make sure that related alternatives are grouped together
... Then moving out to authentication mechanisms which also distinguish from robots

sh: Also moves people from the familiar to the less familiar approaches

<jasonjgw> Janina proposes to take the reorganization to APA, allow time for them to read it, and confirm.

<jasonjgw> Janina: we've decided what to say about ReCAPTCHA.

sh: Seem to be many varied experiences with recaptcha

jgw: Also comment on privacy
... Problem is can involve other parties and disclose to other parties--an issue independent of a11y

sh: Privacy easily takes us into multiple other issues.

jgw: We need to be clear we're addressing a11y and only noting other concerns
... Our recommendations will be a11y, but we will need to note there are additional aspects that also need consideration

sh: That also raises the issue of security

js: Noting that security concern shifts to the user with authentication scemes, whereas old simple captcha placed security squarely only on the web site

<jasonjgw> https://github.com/w3c/apa/issues/7

<tripu> trackbot, status

<trackbot> #rqtf is associated with #apa.

<scott_h> reCAPTCHA example https://www.nteu.org.au/contacts

<jasonjgw> We agree to have a detailed discussion of the privacy comment at the next meeting.

<jasonjgw> im, next item

Identifying upcoming research topics.

jgw: Upcoming research topics as we review APA verticals topics of interest
... Domain specific content is one newer even than the APA wiki
... What the research questions on this are is not yet clear
... One are is author guidance
... Other issues?
... Issue of how specific treatment of domain content fits into the web

<jasonjgw> Janina suggests an example of a physics text that includes formulae in specific notation. We may need an accessibility API mapping for the specific notation involved.

<jasonjgw> An aocustics text is a good example, as it would also include SVG diagrams.

<jasonjgw> We need to delineate the beginning and end of each segment of specialized notation, and to identify in metadata what notations are used.

<jasonjgw> Example: the acoustics text could include mathematical and musical notation that need to be treated specially.

jgw: Recent math conf concerns expressed whether presentation mathml supports sufficient rendering
... We need metadata to distinguish subdomain of math is being used in a particular content instance

<jasonjgw> mple: vertical bar notation could represent absolute value (e.g., of a real number), cardinality of a set, the norm of a vector.

jgw: It was also noted one could analyze variables used and derive a good guess--needs work, though

<jasonjgw> Janina notes similar issues in music notation that are treated in NMX.

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
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/provided/supports/
Default Present: jasonjgw, janina, scott_h, sloandr, Judy
Present: jasonjgw janina scott_h sloandr Judy
Found Scribe: janina
Inferring ScribeNick: janina

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

Found Date: 01 Aug 2018
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.)