RE: Target Size SC

+1 to Michael

About:
“Text Links - The target is a text link with a size that is at least 22 pixels in width or height unless it is in a block of text;”

I still have no clue what the exact rationale and well-founded reason is for the size of 22 CSS pixels and the combination with a block of text.

I guess the 22 is chosen  just because we have the Material Design 48x48 dp and Human Interface Guidelines 44x44 pt as a basis, adapted the 44 CSS pixels for this SC but it didn’t work for lists of links so we took half of it, 44x22 CSS pixels.
And now we also want to apply this size to text links IF they are not part of more than one sentence of text.

I struggle with this because:


-          One sentence can be bigger / contain more words than two sentences, so why the differentiation

-          One sentence can still cover multiple lines, especially when re-sizing for mobile / phone, so why the differentiation

-          22 pixels is the default link height for font-size 17px and thus will always comply, even when the link is 1 character / 22x3 CSS pixels

-          All font-sizes lower than 17 CSS pixels have different compliance rules for small words:

o   Some 2 / 3 / 4 letter words may or may not comply, depending on character width

o    Depending on CSS padding they may or may not comply, also in relation to the amount of characters

o   For content authors working with a CMS this is very hard to adjust / know besides measuring with a measure tool for every small link

o   For sites with different font sizes it may be so that some sizes may and others may not be used to link certain 3 / 4 character words but this is even different for other ones

Just some remarks why I wonder about the rationale although I do fully support big enough target sizes for all UICs.

Regards,
Jake Abma

Accessibility Lead ING
Product owner at Team A11Y

ING Nederland / CIO / Omnichannel / Experience
ACT B.02.166, Bijlmerdreef 24
Postbus 1800, 1000 BV Amsterdam
0031 (0)6 - 25 27 52 46
jake.abma@ing.nl<mailto:jake.abma@ing.nl>





From: Michael Gower [mailto:michael.gower@ca.ibm.com]
Sent: woensdag 22 november 2017 18:42
To: Kathy Wahlbin <kathy@interactiveaccessibility.com>
Cc: Andrew Kirkpatrick <akirkpat@adobe.com>; Joshue O Connor <joshue.oconnor@cfit.ie>; w3c-wai-gl@w3.org
Subject: Re: Target Size SC

Sending out my response to the broader group.

I wonder if we already have an "out" for the text link conundrum using:
User Agent Control - The appearance of the target is determined by the user agent and is not modified by the author.

So, here's the scenario. If we just treat links as user agent controls, just like an <input>, then I think maybe we gain all we need through the 'not modified by author' language.

Any time I've ever seen a link used as some kind of replacement for a control, the author has ALWAYS modified the appearance. They don't want it to look like a straight old underlined text link with a focus rectangle around it because that doesn't jibe with the UI. So they make it 1) look like a button or 2) look like a menu item or even 3) look less like a link and more like a text control (a la iOS).

Yes, there is the possibility that someone will just leave it as a thoroughly stock html link, but in my experience anything that is designed to be a control will be affected -- the Designers just won't let it exist in stock form. Conversely links that just fall inside text documents will be less likely to be affected (but still could be).

We'd end up with:
Level AA The size of the target for pointer inputs is at least 44 by 22 CSS pixels except when:

  *   Essential - A presentation of target is essential to the information being conveyed;
  *   Equivalent - The target is available through an equivalent link or control on the same page that is at least 44 by 22 CSS pixels;
Text Links - The target is a text link with a size that is at least 22 pixels in width or height unless it is in a block of text<https://www.w3.org/TR/WCAG20/#blockstextdef%7C>;
  *   User Agent Control - The appearance of the target is determined by the user agent and is not modified by the author.

We add in wording to the Understanding document that makes it clear that any alteration of user interface controls through suppression of appearance, such as removal of underlining from links, or styling user agent controls with CSS immediately makes the SC applicable. We may need some language on links saying that changing only link text color for visited and unvisited links is an exception. That addresses the block of text situation, in the case where link color is modified but nothing else.

This is much the same tactic we took for User Interface Component Contrast (and which was revised into Graphics Contrast:
The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s): (Level AA)

User Interface Components
Visual information used to indicate states and boundaries of active user interface components, except where the appearance of the component is determined by the user agent and not modified by the author.

Thoughts?

Michael Gower
IBM Accessibility
Research

1803 Douglas Street, Victoria, BC  V8T 5C3
gowerm@ca.ibm.com<mailto:gowerm@ca.ibm.com>
voice: (250) 220-1146 * cel: (250) 661-0098 *  fax: (250) 220-8034



From:        Kathy Wahlbin <kathyw@ia11y.com<mailto:kathyw@ia11y.com>>
To:        Michael Gower <michael.gower@ca.ibm.com<mailto:michael.gower@ca.ibm.com>>, "Repsher, Stephen J" <stephen.j.repsher@boeing.com<mailto:stephen.j.repsher@boeing.com>>
Date:        2017-11-21 09:09 AM
Subject:        RE: Target size

________________________________



Hi Mike –

Can you take a look at the language I added to the WIKI?  Any suggestions on how to change this to address the concerns?

See the section “Alternative Wording”

https://www.w3.org/WAI/GL/wiki/WCAG_2.1/targets#SC_revision_discussed_on_11.2F21_call_.28Kathy.27s_suggestion.29



Kathy
CEO & Founder
Interactive Accessibility

T (978) 443-0798  F(978) 560-1251 C (978) 760-0682
E kathyw@ia11y.com<mailto:kathyw@ia11y.com>
www.InteractiveAccessibility.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.interactiveaccessibility.com_&d=CwMGaQ&c=jxhwBfk-KSV6FFIot0PGng&r=UK__SX18Mp9Fb6tIJfzgjkhM1qTux9WksegD3zR-Bss&m=Kyx2xjSikKdohzK4YYjpf6lkpNeSYzbcW2-3BWkmRfM&s=QvEa6SOOfiPYi3edgtQBne9UjZFUHulJz3xqkGwAu7o&e=>

NOTICE: This communication may contain privileged or other confidential information. If you are not the intended recipient, please reply to the sender indicating that fact and delete the copy you received. Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful.

From: Michael Gower [mailto:michael.gower@ca.ibm.com]
Sent: Tuesday, November 21, 2017 12:01 PM
To: Repsher, Stephen J <stephen.j.repsher@boeing.com<mailto:stephen.j.repsher@boeing.com>>; Kathy Wahlbin <kathyw@ia11y.com<mailto:kathyw@ia11y.com>>
Subject: Target size

I'd be happy to participate in trying to crack this nut again.
My two bits is that I'm hearing two different objectives:
1) make Control target sizes a minimum size (just like in mobile guidance)
2) make all links a minimum target size

I think we can achieve #1 in the language with blocks of text as defined, and make #2 best practices and advisory techniques.

I suggest we discuss objectives at this level of abstraction to agree on scenarios, and then try to tweak language to meet those different scenario objectives.


Michael Gower
IBM Accessibility
Research

1803 Douglas Street, Victoria, BC  V8T 5C3
gowerm@ca.ibm.com<mailto:gowerm@ca.ibm.com>
voice: (250) 220-1146 * cel: (250) 661-0098 *  fax: (250) 220-8034


Michael Gower
IBM Accessibility
Research

1803 Douglas Street, Victoria, BC  V8T 5C3
gowerm@ca.ibm.com<mailto:gowerm@ca.ibm.com>
voice: (250) 220-1146 * cel: (250) 661-0098 *  fax: (250) 220-8034



From:        Kathy Wahlbin <kathy@interactiveaccessibility.com<mailto:kathy@interactiveaccessibility.com>>
To:        Andrew Kirkpatrick <akirkpat@adobe.com<mailto:akirkpat@adobe.com>>, Joshue O Connor <joshue.oconnor@cfit.ie<mailto:joshue.oconnor@cfit.ie>>, "w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>" <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Date:        2017-11-21 09:10 AM
Subject:        Target Size SC
________________________________



Based on the feedback on today’s call, I took a stab at modifying the target size success criteria language for AA and AAA.  See the section “Alternative Wording” on the WIKI

https://www.w3.org/WAI/GL/wiki/WCAG_2.1/targets#SC_revision_discussed_on_11.2F21_call_.28Kathy.27s_suggestion.29<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_WAI_GL_wiki_WCAG-5F2.1_targets-23SC-5Frevision-5Fdiscussed-5Fon-5F11.2F21-5Fcall-5F.28Kathy.27s-5Fsuggestion.29&d=DwMFAg&c=jf_iaSHvJObTbx-siA1ZOg&r=_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc&m=YEpXscziFaqGTQElW-Y1zNt8HD9Q_YnNWO148Yv3n6U&s=gf9TpHTEBd1desWZIptlJHCe2JWvY-Tk_5pRdmurw4k&e=>


Kathy
CEO & Founder
Interactive Accessibility

T (978) 443-0798  F(978) 560-1251 C (978) 760-0682
E kathyw@ia11y.com<mailto:kathyw@ia11y.com>
www.InteractiveAccessibility.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.interactiveaccessibility.com_&d=CwMGaQ&c=jxhwBfk-KSV6FFIot0PGng&r=UK__SX18Mp9Fb6tIJfzgjkhM1qTux9WksegD3zR-Bss&m=Kyx2xjSikKdohzK4YYjpf6lkpNeSYzbcW2-3BWkmRfM&s=QvEa6SOOfiPYi3edgtQBne9UjZFUHulJz3xqkGwAu7o&e=>

NOTICE: This communication may contain privileged or other confidential information. If you are not the intended recipient, please reply to the sender indicating that fact and delete the copy you received. Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful.




-----------------------------------------------------------------
ATTENTION:
The information in this e-mail is confidential and only meant for the intended recipient. If you are not the intended recipient, don't use or disclose it in any way. Please let the sender know and delete the message immediately.
-----------------------------------------------------------------