Update: revised Working Group Note on CAPTCHA

Hi, Jasonpresent+

<jasonjgw> I'm still here. The mute button seems to have disappeared from the UI.

<jasonjgw> Janina: latest draft not quite published yet.

<jasonjgw> Janina has been coordinating with Michael regarding publication logistics.

https://www.w3.org/TR/turingtest/

<jasonjgw> Janina: when publication occurs, the draft will appear at the same URI as the previous draft and will be announced on the Task Force list and elsewhere.

<jasonjgw> Janina notes that the published draft is significantly different from the July 2018 draft. Wide review is called for.

<jasonjgw> Janina clarifies that the next phase will depend on the nature of comments received.

<jasonjgw> Scott discussed the draft at a conference this week; questions were raised about privacy issues associated with third-party CAPTCHA services.

<jasonjgw> Janina acknwoeldges the work done to address such issues in the recent revision.

<jasonjgw> Janina: it demonstrates the importance of amintaining up to date guidance.

Version being published is here:

https://w3c.github.io/apa/captcha/

https://w3c.github.io/apa/captcha/

Update and discussion: accessibility of domain-specific content

https://www.w3.org/community/

<jasonjgw> Janina: the community group is now established. This will be the locus of the wider W3C conversation.

<jasonjgw> Janina notes the different ways in which knoweldge is represented in content written in different domains.

<jasonjgw> Janina has written a first draft of a document that explains proposed minimum requirements for incorporating content from one or more knowledge domains itno a document.

<jasonjgw> Janina: an acoustics texts may include both mathematical notation and music notation .

<jasonjgw> Graphics are also likely to be included.

<jasonjgw> Janina: the user agent needs to be able to identify the content from each knoweldge domain within the the document and to determine what it is, so that diverse assistive technologies and other tools can be used to process it.

<Chris_OBrien> +1

<jasonjgw> Responding to Scott: Janina raises the question of wehther there needs to be a registry of identifiers for specific types of custom domain-specific markup that might be used. Janina cautions taht this may not be desirable or necessary, but wishes to investigate the relevant ocnsiderations that operate here.

<jasonjgw> Janina offers to have another draft by the next meeting.

Update and discussion: virtual/augmented reality accessibility and 360-degree video

<scribe> scribe: janina

jgw: We have some existing documentation on ar and vr ...
... suggest starting from the main rqtf wiki and follow links
... Additional W3C activity in this area appears to be coalescing
... new wg
... Entertainment and Media IG held telecon re 360 video
... e.g. how should captions/subtitles fall in user's field of view? follow their gaze? stay fixed?
... expecting apa interest, as well as timed-text wg

<Chris_OBrien> I have to drop off for another meeting

jgw: that summarizes context

jb: yes

sh: Is it expect captions remain where user is looking?

jgw: According to meeting there are varying prefeences
... One proposed approach noted use case of an indicator (arrow?) pointing to the active speaker who may be out of the view field

mc: That was one proposal involving captions in fixed field
... another proposal was to have captions moving with user's view field
... Believe they mean to allow the user to configure

sh: Clever!
... Is there a todo for us in this?

jgw: At the moment we should be aware of current work status
... There's still more direction we need from where work will go

mc: We can come up with use cases and reqs they might not think of
... e.g. captions appearing angled as though writing on a nonrectelinear plane
... we need to define who/what gets to overwrite

jb: Notes an open w3c position who should be someone who can help with this, too

<jasonjgw> Janina notes potential to use VR to make display of notation (e.g., equations) more usable in the context of enlargement/users who have low vision.

jgw: notes also issues of readability in an vr context were discussed at the mtg

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)

Default Present: jasonjgw, scott_h, Chris_OBrien, MichaelC
Present: jasonjgw scott_h Chris_OBrien MichaelC
Found Scribe: janina
Inferring ScribeNick: janina
Found Date: 13 Feb 2019
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.)