Re: Comments on WCAG2ICT Overview

I read thru the docs and here is my post on it. We'll collect comments and
suppose I will send them to this address
https://kma.global/guidance-by-wcag2ict-on-closed-systems/

Doesn't seem to be that many changes from the 2013 2.0 version.

I'm somewhat baffled by your examples of closed systems (reiterated from
the 2013 doc).  I would have thought POS, POS terminals, Grovery SCOs and
ATMs which comprise the vast majority of "closed systems" today would have
been the more relevant examples for you to note (not ebooks, OS login
screens or "travel kiosks").  For that matter, modern TVs these days.  No
mention of mobile apps? There are many more menu boards than kiosks for
that matter. Not sure what "travel kiosks" are specifically to be honest.



*-------------------Signature----------------------------*
Thanks very much for your support!
*We are at IAAPA <https://kioskindustry.org/iaapa-kiosk-update/> in
November*
*Here is my calendar <https://calendar.app.google/nJ2xxkXgvmbYf1c39> for
calls*

Craig

Kiosk Association manager & Consultant
Craig Allen Keefner
720.324.1837 m
www.linkedin.com/in/kiosk
craig.keefner@gmail.com
Teams or Zoom for share



On Thu, Aug 24, 2023 at 10:28 AM Day, Phil <Phil.Day@ncr.com> wrote:

> Dear Craig,
>
>
>
> Thanks for taking the time to comment on this draft. The task force has
> spent a lot of time considering closed functionality products, including
> kiosks. We also have some participants within the task force with
> experience working with kiosks (both software and hardware). Sending out
> drafts for public review is an important way for our task force to obtain a
> wider review of the WCAG2ICT document. We welcome your input and that of
> others in your association who may have more diverse product knowledge, as
> we recognize that this is a challenging area. If there are specific changes
> that you think are required, please submit your comments. You may find the
> sections focusing on Closed Functionality to be particularly relevant to
> kiosks (including Section 3
> <https://urldefense.com/v3/__https:/www.w3.org/TR/wcag2ict/*closed-functionality__;Iw!!In4Qlw!p9mSjlQeOV1pFsCYuLtrAr6PswWSFs29M3hx2jjzPlX3u22xFfkfHESmNKohM926saA8m4ihWlc-5A$>,
> and Appendix A
> <https://urldefense.com/v3/__https:/www.w3.org/TR/wcag2ict/*success-criteria-problematic-for-closed-functionality__;Iw!!In4Qlw!p9mSjlQeOV1pFsCYuLtrAr6PswWSFs29M3hx2jjzPlX3u22xFfkfHESmNKohM926saA8m4jvkRKWug$>
> ).
>
> We are still working on updates to Appendix A
> <https://urldefense.com/v3/__https:/www.w3.org/TR/wcag2ict/*success-criteria-problematic-for-closed-functionality__;Iw!!In4Qlw!p9mSjlQeOV1pFsCYuLtrAr6PswWSFs29M3hx2jjzPlX3u22xFfkfHESmNKohM926saA8m4jvkRKWug$>,
> so any input you submit can help us to refine and further improve this
> section.
>
>
>
> Regards,
>
> Phil Day, on behalf of the WCAG2ICT Task Force.
>
>
>