Create a Space - Create Team Space Modal : Visible label/form field are not associated

Issue Summary

In "Create team space" modal, the Space name & Space key form controls are not programmatically associated with their visible labels.

Tested URL:

https://confsrva11ya.instenv.atl-test.space/spacedirectory/view.action 

Steps to reproduce

1. Navigate to the 'Space directory' page inside confluence.
2. Navigate to 'Create space' button inside main content & activate it.
3. Select 'Team Space' radio button inside 'Create space' dialog.
4. Activate 'Next' button.
5. Navigate inside 'Create team space' modal dialog.

Actual Results

While navigating with screen reader tuned on, when user navigate to 'Space name' & 'Space key' form controls screen reader announces as 'Edit text' because the visual labels are not programatically associated with input fields.

This makes screen reader users difficult to understand the purpose of these input fields.

Expected Results

The screen reader should announce the labels when user navigate to 'Space name' & 'Space key' form controls. Associate the labels to the input fields explicitly via for & id relation.

Code Snippet:

<label for="name">Space name</label>
<input class="text long-field" id="name">

<label for="spaceKey">Space name</label>
<input class="text long-field" id="spaceKey">

Screenshot

Issue 721065: https://axeauditor.dequecloud.com/api/v1/file/fdec2a40-4eb9-11ec-803c-978d38381a1b 

BACKGROUND

People who are blind cannot use the visual layout of a form to determine which labels go with which form elements. In order to be certain which label goes with which form element, the label and form element must be programmatically associated. When labels and form elements are programmatically associated, a screen reader user can put focus on a form element and the screen reader will automatically read the label and element type together. In addition, some coding methods will create a larger clickable area for the form element which benefits people with motor disabilities.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available