[w3ctag/design-reviews] Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT) - Google Chrome - Daniel (w3.org) (Issue #973)

こんにちは TAG-さん!

I'm requesting a TAG review of Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT).

Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT) describes how the Web Content Accessibility Guidelines (WCAG) can be applied to non-web information and communications technologies (ICT), including documents and software. 

  - Explainer¹ (minimally containing user needs and example code): https://www.w3.org/WAI/standards-guidelines/wcag/non-web-ict/
  - Specification URL: https://www.w3.org/TR/wcag2ict-22/
  - Tests: [wpt folder(s), if available]
  - User research: [url to public summary/results of research]
  - Security and Privacy self-review²: https://www.w3.org/TR/wcag2ict-22/#privacy-considerations https://www.w3.org/TR/wcag2ict-22/#security-considerations
  - GitHub repo: https:///www.github.com/w3c/wcg2ict/
  - Primary contacts (and their relationship to the specification):
      - Mary Jo Mueller (maryjom), IBM, TF Facilitator
      - Daniel Montalvo (daniel-montalvo), W3C, Staff Contact
      - Phil Day (pday1), NCR Atleos, Editor
      - Chris Loiselle (ChrisLoiselle), Oracle Corporation, Editor
  - Organization(s)/project(s) driving the specification: IBM, NCR, Oracle, 
  - Key pieces of existing multi-stakeholder (e.g. developers, implementers, civil society) support, review or discussion of this specification
  - Key pieces of multi-implementer support:
    - Chromium comments: [url]
    - Mozilla comments: https://github.com/mozilla/standards-positions/issues/NNN
    - WebKit comments: https://github.com/WebKit/standards-positions/issues/NNN
    - etc...
  - External status/issue trackers for this specification (publicly visible, e.g. Chrome Status):

Further details:

  - [X] I have reviewed the TAG's [Web Platform Design Principles](https://www.w3.org/TR/design-principles/)
  - Relevant time constraints or deadlines: [please provide]
  - The group where the work on this specification is currently being done: https://www.w3.org/groups/wg/agwg/
  - The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue):
  - Major unresolved issues with or opposition to this specification:
  - This work is being funded by:

You should also know that...

[please tell us anything you think is relevant to this review]

------------------------------------------------------------------------------------
CAREFULLY READ AND DELETE CONTENT BELOW THIS LINE BEFORE SUBMITTING

Please preview the issue and check that the links work before submitting.

In particular, if anything links to a URL which requires authentication (e.g. Google document), please make sure anyone with the link can access the document. We would prefer fully public documents though, since we work in the open.

¹ We require an explainer to give the relevant context for the spec review, even if the spec has some background information. For background, see our [explanation of how to write a good explainer](https://tag.w3.org/explainers/). We recommend the explainer to be in [Markdown](https://github.github.com/gfm/).

² A Security and Privacy questionnaire helps us understand potential security and privacy issues and mitigations for your design, and can save us asking redundant questions. See https://www.w3.org/TR/security-privacy-questionnaire/.

³ For your own organization, you can simply state the organization's position instead of linking to it. Chromium doesn't have a standards-positions repository and [prefers](https://source.chromium.org/chromium/chromium/src/+/main:docs/standards/positions/GoogleChrome/README.md) to use comments from the teams that maintain the relevant area of their codebase.


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/973
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/973@github.com>