[a11y-request] Issue: DAPT 2021-07-18 (#66) marked as REVIEW REQUESTED

nigelmegitt has just labeled an issue for https://github.com/w3c/a11y-request as "REVIEW REQUESTED":

== DAPT 2021-07-18 ==
Note that the APA WG prefers groups to run a self-review around the time of FPWD. Let us know when you have done it. Get advice on how to do that at https://w3c.github.io/apa/fast/checklist.html.

If you still want us to review your spec, please provide the information below.

In the issue title above add the document name followed by the date of this request.

- name of spec to be reviewed: **DAPT**
- URL of spec: **https://www.w3.org/TR/dapt/**

- Do you need a reply by a particular date?

We are requesting all feedback by **2023-09-10** so that we can discuss and address issues raised during the TPAC week.

- Please point to the results of your own self-review (see https://w3c.github.io/apa/fast/checklist.html)

**https://github.com/w3c/dapt/wiki/Considerations-for-the-Accessibility-review**

- Where and how to file issues arising?

Please raise issues at **https://github.com/w3c/dapt/issues** 

- Pointer to any explainer for the spec?

The [introduction](https://www.w3.org/TR/dapt/#introduction) is intended to function as an explainer in its own right; however we will also draft a separate Explainer (needed also for TAG review) and link to it later. 

We have also prepared an accessibility-focused [text description of the FAST self-review](https://github.com/w3c/dapt/wiki/Considerations-for-the-Accessibility-review#user-content-textual-description-and-explanations-of-the-accessibility-considerations) to try to help explain the review answers.

Other comments:

Since DAPT is on the Rec track under TTWG, and TTWG's Charter lists APA WG as an internal coordination group, we have separately requested Wide Review feedback from APA WG [(member-only email reflector link)](https://lists.w3.org/Archives/Member/member-tt/2023Jul/0000.html), in addition to this Horizontal Review request.

See https://github.com/w3c/a11y-request/issues/66


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 18 July 2023 11:14:28 UTC