Add HTML AAM considerations to PR template and enable for HTML

[annevk]

@domenic @scottaohara let me know if you have any thoughts. The main thing this adds to the PR template for HTML will look like this:

• Corresponding HTML AAM issue or PR:

and I would expect it to be completed like this:

• Corresponding HTML AAM issue or PR: N/A

or:

• Corresponding HTML AAM issue or PR: PR link

(This has been edited to instead feature the latest suggestion.)

[aphillips]

What about other horizontal concerns, e.g. security, privacy, sustainability, and the like?

Why would separate PRs be created for a11y/i18n? Shouldn't these types of issues be addressed in PR being created with the template?

I might prefer to just see the i18n-tracker label on PRs that have I18N-related gorp in them. If the checkbox is just a reminder that we think I18N is important, perhaps instead:

• Horizontal issues (A11Y, I18N, etc.) have been addressed

Or am I not understanding?

(PS> Consider adding i18n-tracker label to this PR so that it's tracked in our repo)

[annevk]

Hmm yeah.

Maybe I should restrict this to accessibility and in particular HTML AAM which "frequently" ends up needing changes due to changes in HTML semantics.

Most other horizontal concerns don't really have that kind of integration.

[scottaohara]

thanks for this @annevk

i think this would be a good add. arguably a second check for aria in html issue/pr might be helpful? but, maybe just html aam is enough since that'll get it on the ARIA wg's radar and then we can determine if an aria in html issue/pr would be necessary or not.

[zcorpan]

@scottaohara asked to add "ARIA in HTML" which is https://w3c.github.io/html-aria/ . I think ARIA usually don't need changes for changes in HTML.

[annevk]

Sigh. Okay. Will create some more PRs.

[annevk]

#77
whatwg/html#10830

And thanks for catching!