How can I improve keyboard navigation and screen‑reader support in a DRF browsable API form workflow?

When using Django REST Framework’s browsable API, the automatically generated HTML forms for create and update actions lack explicit labels and ARIA attributes that screen‑reader users rely on, and keyboard focus can become trapped in nested divs.

I want to improve accessibility by associating each form field with a <label> element, adding appropriate ARIA‑live regions for validation messages, and ensuring a logical tab order without completely overriding the browsable API templates.

What are the supported extension points or mixins that let me inject these accessibility enhancements while keeping the default browsable API layout, and how can I verify the changes with automated accessibility testing tools?