Accessibility violation: missing aria-label on browsable API form inputs

The goal is to make every input, select, and textarea in the Django REST Framework browsable API form perceivable to screen‑reader users by providing explicit accessible names.

However, adding ARIA labels or altering tab order must not break existing projects that override the browsable API templates, and it is unclear which labeling strategy offers the best balance between automation and developer control.

• Which ARIA attribute (aria-label, aria-labelledby, or aria-describedby) should be added to each form control, and should its value be taken from the associated <label> element or generated from the field name?
• Should a fallback label be supplied when the <label> element is missing or empty, and if so, what text should be used?
• How can the tab order be adjusted to follow the visual layout while preserving compatibility with custom template overrides?