openproject/frontend/app/components/inplace-edit/directives/field-edit/edit-date/edit-date.directive.html

<div class="inplace-edit--date">
  <label
    class="hidden-for-sighted"
    for="inplace-edit--write-value--{{::field.name}}">
      {{::field.getLabel()}}
  </label>
  <input ng-model="field.value"
         ng-change="onEdit()"
         ng-click="showDatepicker()"
         title="{{ fieldController.editTitle }}"
         class="inplace-edit--date"
         id="inplace-edit--write-value--{{::field.name}}"
         type="text" />
	<div class="inplace-edit--date-picker"></div>
</div>
Merge of changes from different PRs. 10 years ago			`<div class="inplace-edit--date">`
have labels for all the inplace edit fields The labels are hidden, so they do not disturb. On the other hand, they enable blind users to have the fields properly named for them by a screen reader. It would be better, to have the element to the right of the input element (in the dt) turn into a label. But given the current structure of the directives that would have been way more complicated 9 years ago			`<label`
			`class="hidden-for-sighted"`
			`for="inplace-edit--write-value--{{::field.name}}">`
			`{{::field.getLabel()}}`
			`</label>`
			`<input ng-model="field.value"`
			`ng-change="onEdit()"`
			`ng-click="showDatepicker()"`
			`title="{{ fieldController.editTitle }}"`
			`class="inplace-edit--date"`
			`id="inplace-edit--write-value--{{::field.name}}"`
			`type="text" />`
Reduce fieldController redundancies [ci skip] 9 years ago			`<div class="inplace-edit--date-picker"></div>`
Merge of changes from different PRs. 10 years ago			`</div>`