Test how Copilot performs when we add normative language and acceptance criteria to the issue description (#950)

### What

I want to provide a clear checklist for Copilot to follow when
remediating these Axe issues. I also am opting to test normative
language `Must` `SHOULD` `MUST NOT`. My understanding is these methods
help AI focus and produce more tailored responses.

Author: kendallgassner

.github/actions/file/src/openIssueForFinding.ts

@@ -31,11 +31,20 @@ export async function openIssueForFinding(octokit: Octokit, repoWithOwner: strin
           : line
       )
       .join("\n");
-    const body = `
+    const acceptanceCriteria = `## Acceptance Criteria
+- [ ] The specific axe violation reported in this issue is no longer reproducible.
+- [ ] The fix MUST meet WCAG 2.1 guidelines OR the accessibility standards specified by the repository or organization.
+- [ ] A test SHOULD be added to ensure this specific axe violation does not regress.
+- [ ] This PR MUST NOT introduce any new accessibility issues or regressions.
+`
+
+    const body = `## What
 An accessibility scan flagged the element \`${finding.html}\` on ${finding.url} because ${finding.problemShort}. Learn more about why this was flagged by visiting ${finding.problemUrl}.
 
 To fix this, ${finding.solutionShort}.
 ${solutionLong ? `\nSpecifically:\n\n${solutionLong}` : ''}
+
+${acceptanceCriteria}
 `;
 
     return octokit.request(`POST /repos/${owner}/${repo}/issues`, {
@@ -46,4 +55,4 @@ ${solutionLong ? `\nSpecifically:\n\n${solutionLong}` : ''}
       labels
     });
   }
-}
+}