Controls checklist.

It could be very useful for contributors and reviewers if we had a clear set of objectives for all or most of our controls, that way we can always have a clear goal for the quality of our controls.

Such a list could be high-level objectives like "accessible" and low-level objectives like "Uses throw helpers"

Also, we can use such a list to backtrack through existing controls and open issues related to such a list.

No file, test, or entry point is identified in the issue. Start by reviewing the WindowsCommunityToolkit wiki and existing control guidance, then define the checklist scope and objective levels. Done means a clear, reusable checklist exists for contributors and reviewers and can guide follow-up issues.

Written by the indexing model from the issue text.