Target size (first half - 30 min)

+AWK

<Mike_Pluke> What is the Webex meeting ID?

<Kathy> https://github.com/w3c/wcag21/issues/60

<alastairc> https://github.com/w3c/wcag21/issues/60#issuecomment-286490153

Kathy: big issue right now seems to be inline links

"For targets within content which are considered essential, at least one of the following is true "

https://github.com/w3c/wcag21/issues/60#issuecomment-286229209

<alastairc> Main concern: pointer isn't an attribute of the content, but the user's setup / user-agent. That means it is 44px for any public facing site.

JF: could we exclude text-based links if they are a problem?

<kirkwood> +1 to JF

Kathy: many users may have problems with using zoom function to get the links larger

<Detlev> missing the password for Webex...

<alastairc> Question: Don't the mobile devices have heuristics when people tap screens to help you hit small targets? Not sure how much that helps when people have mobility impairments?

<Detlev> I read that but can't recall that from the main call...

<Detlev> thanks Alastair!

Also the high contrast also includes images of text, and high contrast doesn't deal with that

<KimD> Present_

<Zakim> JF, you wanted to ask How do evaluators know what the end user is using in terms of "pointer" input? (I have a pen with a rubberized tip which I use on my cell phone, so does the

<Detlev> scribe?

<JF> "The size of the target in relation to the visible display at the default viewport size is at least: - 44px by 44px for pointer inputs with coarse pointing accuracy (such as a touchscreen) - 22px by 22px for pointer inputs with fine pointing accuracy (such as a mouse, trackpad or stylus)"

<patrick_h_lauke_> JF https://drafts.csswg.org/mediaqueries-4/#mf-interaction to start

<patrick_h_lauke_> rubberised stylus will act to the tablet/phone as a finger

<Kathy> The size of the target in relation to the visible display at the default viewport size is at least 44px by 44px for pointer inputs where px is a CSS pixel when the page is using the device ideal viewport.

<patrick_h_lauke_> unless it's a dedicated stylus

<patrick_h_lauke_> if we say that one dimension can be half of the other...but at the same time we say that users have difficulty accurately hitting a target that is not X wide, wide do we then think they can hit a target that is half of X in the other direction?

<patrick_h_lauke_> agree

<laura> 44 px = 2.750em right?

<patrick_h_lauke_> laura yes

personalization

Lisa: 2 reasons investing in this area

with Cognitive, there are many "best" versions

Personalization: https://github.com/w3c/wcag21/issues/6

<alastairc> yep, need the 'how': How does a site implement this now (or v soon).

JF asks about "contextual information" definition. Only achievable with ARIA?

Lisa: Can be implemented with RDF-a today
... COGA work in ARIA will make this simpler

JF: but that ARIA work is still in draft

Lisa: Question - when does a technology need to be ready to allow us to include it?

<JF> <title> Step 2 of a 5 step process</title> isw indeed machine-readable

<Mike_Pluke> +1

<mhakkinen> +1 to first point of gowerm

<Zakim> JF, you wanted to ask about "Contextual information and author settable properties of regions, critical features and important information are programmatically determinable so that

<gowerm> COGA is not the only thing that can benefit from personalization, but at the moment, it is the only thing in the spec

<alastairc> Lisa, would be good to update the link to "Semantics for adaptive interfaces" on the issue 6 page, currently 404.

<JF> 2 independent implementations

<gowerm> WAYNE: how do you not think this is more effort?

<gowerm> Plain language: Allow the user to use plain language and provide clear and simple language in all content so that all of the following are true

<gowerm> "...If the text is not literal, then the tester must confirm that personalization and an easy user setting enables it to be replaced, such that all meaning is retained. "

<jamesn> ARIA doesn't have drag and drop

<Wayne> With well defined programming language additions, the author does not have to provide a mechanism. The AT can do that.

<JF> +1 to JamesN re: ARIA does not have D&D

<gowerm> No, the author has to rewrite the entire content for simplification

<laura> bye

<Wayne> Mike let's talk of line

trackbot, end meeting

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)

Default Present: AWK, Kathy, Rachael, marcjohlic, alastairc, JF, Mike_Pluke, MichaelC, jasonjgw, Laura, kirkwood, Glenda, Jim, steverep, Pietro, Detlev, JamesNurthen, Kim, MikeGower, KimD
Present: AWK Kathy Rachael marcjohlic alastairc JF Mike_Pluke MichaelC jasonjgw Laura kirkwood Glenda Jim steverep Pietro Detlev JamesNurthen Kim MikeGower KimD
No ScribeNick specified.  Guessing ScribeNick: AWK
Inferring Scribes: AWK

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

Found Date: 16 Mar 2017
Guessing minutes URL: http://www.w3.org/2017/03/16-ag-minutes.html
People with action items: