├── w3c.json ├── README.md └── .github ├── ISSUE_TEMPLATE ├── request-a-check-of-a-self-review.md ├── request-review-for-a-spec-in-cr.md ├── request-review-for-another-type-of-spec.md ├── request-review-for-a-wd-that-is-moving-to-cr-soon.md └── request-review-for-a-fpwd.md └── workflows └── auto-label-and-link.yml /w3c.json: -------------------------------------------------------------------------------- 1 | { 2 | "group": 83907 3 | , "contacts": "michael-n-cooper" 4 | , "repo-type": "process" 5 | , "policy": "restricted" 6 | } 7 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # a11y-request 2 | Horizontal review requests will be made via issues in this repo. 3 | 4 | Past reviews are available on the [APA specification review wiki pages](https://www.w3.org/WAI/APA/wiki/Category:Spec_Review). 5 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/request-a-check-of-a-self-review.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Request a check of a self-review 3 | about: If you have completed a self-review, use this form to request that APA check 4 | it out. 5 | title: Spec_name YYYY-MM-DD 6 | labels: pending, REVIEW REQUESTED, SR, WD 7 | assignees: '' 8 | 9 | --- 10 | 11 | We have conducted a self-review of our spec [SPEC_NAME_HERE](URL_GOES_HERE), and the results can be found at URL_FOR_THE_ISSUE_IN_YOUR_REPO. 12 | 13 | Please check our findings. 14 | 15 | - name of spec to be reviewed: 16 | - shortname: 17 | - URL of spec: 18 | 19 | - Do you need a reply by a particular date? 20 | 21 | 22 | Other comments: 23 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/request-review-for-a-spec-in-cr.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Request review for a spec in CR 3 | about: If your spec is already in CR, use this form. 4 | title: Document_name YYYY-MM-DD > YYYY-MM-DD 5 | labels: CR, pending, REVIEW REQUESTED 6 | assignees: '' 7 | 8 | --- 9 | 10 | In the issue title above add the document name followed by the date of this request, then the date of your proposed deadline for comments. 11 | 12 | - name of spec to be reviewed: 13 | - shortname: 14 | - URL of spec: 15 | 16 | - What and when is your next expected transition? 17 | - What has changed since any previous review? 18 | - Please point to the results of your own self-review (see https://w3c.github.io/fast/checklist.html) 19 | - Where and how to file issues arising? 20 | - Pointer to any explainer for the spec? 21 | 22 | Other comments: 23 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/request-review-for-another-type-of-spec.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Request review for another type of spec 3 | about: If your spec doesn't fit one of the other options, use this. 4 | title: Document_name YYYY-MM-DD > YYYY-MM-DD 5 | labels: pending, REVIEW REQUESTED, WD 6 | assignees: '' 7 | 8 | --- 9 | 10 | In the issue title above add the document name followed by the date of this request, then the date of your proposed deadline for comments. 11 | 12 | - name of spec to be reviewed: 13 | - shortname: 14 | - URL of spec: 15 | 16 | - Current Rec/Note phase? 17 | - What and when is your next expected transition? 18 | - What has changed since any previous review? 19 | - Please point to the results of your [self-review](https://w3c.github.io/fast/checklist.html) 20 | - Where and how to file issues arising? 21 | - Pointer to any explainer for the spec? 22 | 23 | Other comments: 24 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/request-review-for-a-wd-that-is-moving-to-cr-soon.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Request review for a WD that is moving to CR soon 3 | about: Use this if you have a transition date coming up, and need to get a final review. 4 | title: Document_name YYYY-MM-DD > YYYY-MM-DD 5 | labels: LC, pending, REVIEW REQUESTED 6 | assignees: '' 7 | 8 | --- 9 | 10 | In the issue title above add the document name followed by the date of this request, then the date of your proposed deadline for comments. 11 | 12 | - name of spec to be reviewed: 13 | - shortname: 14 | - URL of spec: 15 | 16 | - What and when is your next expected transition? 17 | - What has changed since any previous review? 18 | - Please point to the results of your own self-review (see https://w3c.github.io/fast/checklist.html) 19 | - Where and how to file issues arising? 20 | - Pointer to any explainer for the spec? 21 | 22 | Other comments: 23 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/request-review-for-a-fpwd.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Request review for a FPWD 3 | about: Use this if you are approaching or have just passed FPWD. 4 | title: Document_name YYYY-MM-DD 5 | labels: FPWD, pending, REVIEW REQUESTED 6 | assignees: '' 7 | 8 | --- 9 | 10 | 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/fast/checklist.html. 11 | 12 | If you still want us to review your spec, please provide the information below. 13 | 14 | In the issue title above add the document name followed by the date of this request. 15 | 16 | - name of spec to be reviewed: 17 | - shortname: 18 | - URL of spec: 19 | 20 | - Do you need a reply by a particular date? 21 | - Please point to the results of your own self-review (see https://w3c.github.io/fast/checklist.html) 22 | - Where and how to file issues arising? 23 | - Pointer to any explainer for the spec? 24 | 25 | Other comments: 26 | -------------------------------------------------------------------------------- /.github/workflows/auto-label-and-link.yml: -------------------------------------------------------------------------------- 1 | name: Auto Label and Link Related Issues 2 | 3 | on: 4 | issues: 5 | types: [opened] 6 | 7 | jobs: 8 | label-and-link: 9 | runs-on: ubuntu-latest 10 | 11 | steps: 12 | - name: Extract shortname, add label, and link related issues 13 | uses: actions/github-script@v6 14 | with: 15 | script: | 16 | const issueBody = context.payload.issue.body || ""; 17 | const issueNumber = context.payload.issue.number; 18 | 19 | // 允许 shortname: [ value ] 这种格式，并支持符号 20 | const match = issueBody.match(/shortname:\s*\[?\s*([\w\-.:/]+)\s*\]?/i); 21 | if (match && match[1]) { 22 | const shortname = match[1].trim(); // 去除额外空格 23 | const labelName = `s:${shortname}`; 24 | const labelColor = "6bc5c6"; 25 | 26 | // 获取当前 repo 的所有标签 27 | let existingLabel = false; 28 | try { 29 | const labels = await github.rest.issues.listLabelsForRepo({ 30 | owner: context.repo.owner, 31 | repo: context.repo.repo, 32 | per_page: 100 33 | }); 34 | existingLabel = labels.data.some(label => label.name === labelName); 35 | } catch (error) { 36 | console.error("Failed to fetch labels:", error.message); 37 | } 38 | 39 | // 如果标签不存在，则创建 40 | if (!existingLabel) { 41 | try { 42 | await github.rest.issues.createLabel({ 43 | owner: context.repo.owner, 44 | repo: context.repo.repo, 45 | name: labelName, 46 | color: labelColor, 47 | description: `Automatically created label for shortname: ${shortname}`, 48 | }); 49 | console.log(`Label '${labelName}' created with color #${labelColor}.`); 50 | } catch (error) { 51 | console.error(`Failed to create label: ${error.message}`); 52 | } 53 | } else { 54 | console.log(`Label '${labelName}' already exists.`); 55 | } 56 | 57 | // 给 Issue 添加标签 58 | try { 59 | await github.rest.issues.addLabels({ 60 | owner: context.repo.owner, 61 | repo: context.repo.repo, 62 | issue_number: issueNumber, 63 | labels: [labelName], 64 | }); 65 | console.log(`Label '${labelName}' added to issue #${issueNumber}.`); 66 | } catch (error) { 67 | console.error(`Failed to add label: ${error.message}`); 68 | } 69 | 70 | // 查找 w3c/apa-review 仓库中是否有相同标签的 issue 71 | try { 72 | const relatedIssues = await github.rest.issues.listForRepo({ 73 | owner: "w3c", 74 | repo: "apa-review", 75 | state: "open", 76 | labels: [labelName], 77 | per_page: 10 78 | }); 79 | 80 | if (relatedIssues.data.length > 0) { 81 | const relatedLinks = relatedIssues.data 82 | .map(issue => `- [#${issue.number}](${issue.html_url}): ${issue.title}`) 83 | .join("\n"); 84 | 85 | const commentBody = `Related issue from APA WG:\n${relatedLinks}`; 86 | 87 | await github.rest.issues.createComment({ 88 | owner: context.repo.owner, 89 | repo: context.repo.repo, 90 | issue_number: issueNumber, 91 | body: commentBody, 92 | }); 93 | 94 | console.log(`Added comment linking related issues from w3c/apa-review.`); 95 | } else { 96 | console.log(`No related issues found in w3c/apa-review.`); 97 | } 98 | } catch (error) { 99 | console.error(`Failed to fetch related issues: ${error.message}`); 100 | } 101 | } else { 102 | console.log("No shortname found in the issue body."); 103 | } 104 | --------------------------------------------------------------------------------