AW: Call for Consensus (CfC): Comments on WCAG2ICT

+1

-----Ursprüngliche Nachricht-----
Von: Janina Sajka (janina@rednote.net) <janina@rednote.net> 
Gesendet: Dienstag, 30. Juli 2024 19:36
An: public-apa-admin@w3.org
Betreff: Call for Consensus (CfC): Comments on WCAG2ICT

Colleagues:

This is a Call for Consensus (CfC) to the Accessible Platform Architectures (APA) Working Group proposing three APA comments on "Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)"  as requested in this github issue:

https://github.com/w3c/a11y-request/issues/88

***Proposed APA Comments***

***Issue #1

APA appreciates the proposed Introduction section,  but we believe that it would be helpful to mention the POUR principles explicitly, and to clarify the intended audience, and to reinforce the importance of obtaining user feedback when testing. We offer the following draft paragraph.

"This document provides informative guidance on mapping WCAG to non-web ICT contexts. Readers are encouraged to keep in mind the core framing principles which undergird WCAG Success Criteria and are commonly expressed by the acronym, POUR: Perceivable, Operable, Understandable, and Robust. Developers are also strongly encouraged to obtain testing input from persons with disabilities using applications and content. The sections below provide further details on how individual success criteria may be interpreted outside of the web context."

***Issue #2
Seeking clarity for key term 'underlying platform software'

Throughout most of the document, we understand the following uses of two key terms:
* 'Web content' is generally replaced by either 'content' or 'software' - i.e. instead of a web page, we may be considering an app running on a system.
* 'User agent' is generally replaced by [1]'platform software' - which is defined as 'software that runs on an underlying software or hardware layer and that provides a set of software services to other software components'. To us, this reads as 'the OS, or libraries installed on the system'.

However, in some SCs (and one glossary entry) the following terms are used instead of the above two:
* 'Underlying platform software' seems to be used to mean what we understood 'platform software' to mean above (i.e. the OS, or libraries installed on the system).
* 'Platform software' seems to be used to mean 'an app (running on an OS instead of within a user agent)'

This relates to the following SCs, and a glossary definition:

* 2.5.1 (non-web software branch)
* 2.5.2 (non-web software branch)
* 2.5.7 (non-web software branch)
* 3.3.8 * Glossary entry 'keyboard interface'

What are we asking for?

* If we understand the definitions of the terms correctly, then it seems like there could be an inconsistency with some SCs, as they use the phrase 'underlying platform software'.
* However, if we don't understand correctly, and there is a distinction between 'platform software' and 'underlying platform software', would it be possible to clarify the use of 'underlying platform software' - perhaps adding it to the key terms?

***Issue #3
Closed functionality list - suggested additions

Section in document: [2]Closed functionality list

The closed functionality list is accommodating, but could be expanded to include the following:
1. Medical devices such as digital blood pressure monitors, glucose metres, or other wearable devices.
2. Educational devices like whiteboard, smart boards.
3. Gaming platforms or consoles.

It's noted that some games consoles have extensive accessibility features (especially with respect to controller hardware, and sometimes including TTS functionality) but that, as per the note in this section of the document, not all of these aspects are open to user choice.

***Action to Take***

This CfC is now open for objection, comment, as well as statements of support via email. Silence will be interpreted as support, though messages of support are certainly welcome.

If you object to this proposed action, or have comments concerning this proposal, please respond by replying on list to this message no later than 23:59 (Midnight) Boston Time, Friday 2 August.

As always with an APA CfCs, editorial corrections, such as spelling or grammar, will be made as needed without further notice.  Please do draw our attention to any editorial issues you find in this draft.
 
NOTE: This Call for Consensus is being conducted in accordance with the APA Decision Policy published at:

http://www.w3.org/WAI/APA/decision-policy

Janina and Matthew
APA Co-Chairs

-- 

Janina Sajka (she/her/hers)
Accessibility Consultant https://linkedin.com/in/jsajka

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa

Linux Foundation Fellow
https://www.linuxfoundation.org/board-of-directors-2/

Received on Wednesday, 31 July 2024 14:12:07 UTC