Re: WCAG 2.2 - tightened requirements approach

Sailesh,
I'll need to look back to your email, but I'm a little confused in that 'Programmatically determined' and 'change of context' are already defined terms in the glossary.

Other items like a clarification of 'keyboard focus is visible' are SC-level questions that are already being discussed as part of 2.2 SC proposals.

I'll look back to your email...

Thanks,
AWK

 

Andrew Kirkpatrick

Head of Accessibility

Adobe 

 

akirkpat@adobe.com

http://twitter.com/awkawk


On 7/31/19, 9:25 AM, "Sailesh Panchang" <sailesh.panchang@deque.com> wrote:

    Hello All,
    Further to my proposal dated July 10, 2019, I wish to add that terms
    like 'programmatically determined' 'change in context' or 'Input
    Purposes for User Interface Components section', etc. used in an SC
    are explained in the definitions section.
    Likewise, and based on experience over 10+years, the AG can justify
    that  the term 'keyboard focus indicator is visible' needs to be
    clearly defined leaving little room for ambiguity.
    This is in line with Patrick's comment that the absence of a
    definition is an 'enormous loophole' which seems to suggest he is sort
    of supportive  to this proposal.
    It is in this context the proposed 3-part suggestion in the email of
    July 10 should be considered.
    I reiterate  that I am against changing the level of, or adding text
    to existing SC 2.4.7 or having two SCs that address 'focus visible'.
    Thanks and best wishes,
    
    -- 
    Sailesh Panchang
    Principal Accessibility Consultant
    Deque Systems Inc
    381 Elden Street, Suite 2000, Herndon, VA 20170
    Mobile: 571-344-1765

Received on Wednesday, 31 July 2019 13:41:27 UTC