Mark input purposes list as non-normative

[fstrr]

Closes #3777

Building the site locally doesn't build a homepage, so I can't check to see if the newly-added class does what I think it's supposed to.

---

Preview | Diff

[scottaohara]

approved on the assumption that Mike's suggestion will be accepted, or a separate "appendix" heading precedes this section (in the off chance there would need to be other items that should have been / could be added to the appendix)

[bruce-usab]

Discussed on TF call 4/12 and Ready for approval. Might be impacted by resolution of #3539

[alastc]

Should we be using the appendix class from respec? @iadawn presumably this would be an errata and need re-publishing to show?

[iadawn]

Yes, this would need to be republished to show.

There is something else to consider. Currently this is a section which is not marked as 'non-normative'. Based on Interpreting Normative Requirements this is normative. Changing it to an 'appendix' will make it non-normative.

[fstrr]

@iadawn see this comment—that section is meant to be non-normative.

[alastc]

... Changing it to an 'appendix' will make it non-normative.

@iadawn it's something we lost between WCAG 2.0 and 2.1 (see Mike's comment). So it means some sections were intended to be appendixes, but lost that marking.

[dbjorge]

Currently, 1.3.5 is normatively defined in terms of this seciton. I think that means we can't mark this section as informative unless we also rewrite the first bullet in SC 1.3.5.

[bruce-usab]

Discussed on TF call 9/13. Closing as we need to track this one by the issue, not this PR.