Target Size SCs issue feedback

Hi all,

I'm moving this out of the CFC thread - we'd like those threads to be 
reserved for indications
of support (or not) of the CFC in question and not for detailed 
technical discussion.

I'll start to address some of the comments (others can chime in also).

Thanks for the those point Gregg - Gregg mentioned Zoom vs Magnification 
- and this is interesting as we have been discussing that we need a 
'definition of Zoom' - that has arisen from current work on a different 
SC. I guess most people would see them as the same.

Regarding your comments on 'links' etc - we do (as Detlev pointed out) 
have concerns that we don't want to exempt too much from the SC, as this 
would reduce its impact but others may comment on the issue you raise 
around links. Note, we have updated the exemptions so do have a look and 
see if that addresses your concerns. [1]

Steve Repsher said:

>  The little testing it has undergone has turned up several issues, 
namely focus highlights and >overlap, Which have the potential to end up 
creating significant inaccessibility.  However, if the
>  technique is to use a 44 pixel line, then I’ll support it.

Thanks for the suggestion. In terms of your request for clarification 
but I see that Kathy did reply.

There are differences of opinion here but this SC is trying to address a 
user need, and can for sure be iterated and improved by the group over 
the coming months - but at this stage the group consensus is that this 
is ready to go.

Thanks

Josh

[1] 
https://rawgit.com/w3c/wcag21/target-size_ISSUE-60/guidelines/sc/21/target-size.html 




Gregg said:

 > This appears to include links

There are two exemptions now 'Equivalent: The target is available 
through an equivalent link or control on the same page that is at least 
44 by 44 CSS pixels.' and 'In-Page: The target is a text link where the 
destination is on the same page.' as well as the final exemption 'User 
agent control: The appearance of the target is determined by the user 
agent and is not modified by the author.'

     1. If not - then why is it important to have these large and not
        links.  If they can’t operate the links why is it important to
        operate these
     2. if it DOES include links then we are forcing authors to never
        have small links on the page - even at the very bottom.
          Everything has to be big.
     3. (check my math but does this mean that all links on a page have
        to be in something like 33 point font?   That can’t be right —
        too late at night but that is what the online calculator says
        44px would be)

 1. Why does the author have to make these big for everyone — when users
    can easily (if the content meets other SC) just use the  CTRL+  (or
    equiv)  to make everything bigger so they can use it.
     1. why force everyone to have things large when it is so easy for
        the user who needs it to make theirs larger?
     2.


 2. Why does “customizable” exception exclude magnification.   Does this
    mean ZOOM is ok but Magnification is not?
     1. if ZOOM is OK   then maybe it should say  “
>           * *Customizable:* A mechanism is available to change the
>             size of the target independent of the level of page
>             magnification but not independent of Zoom.


(if I am missing something let me know)




-- 
Joshue O Connor
Director | InterAccess.ie