Design pattern for page headings as input labels

[outerpress]

Task Description

In a one-thing-per-page workflow, there's often a single input on a page. Design for the use-cases where the heading may act as an input label, including marking requiredness.

References

• Slack thread on using inputs as headings
• Outreach to platform design system
• Design explorations WIP
• Experimental design ticket

Acceptance Criteria

• [x] Design file created
• [x] ED ticket created
• [ ] Platform decision recorded
• [ ] Dev spec created

[outerpress]

ED ticket has been created, will present to design council on the 27th

[outerpress]

Notes from design council are here

Next steps are for devs to work on implementation. Once they have a proof of concept, we'll get feedback from platform accessibility.

[outerpress]

Not prioritized for PI 8, moving to Icebox

[outerpress]

This pattern was added to the design system! We're experimenting with it on the CC request content improvements, see #51668 and #51648