UI Design - DRS | Document ID Component Enhancement: Accessibility Requirements

### **Purpose**
This enhancement will include an accessibility review to ensure the Document record component can be used by people who navigate using keyboards, screen readers, and other assistive technologies.

**Accessibility Design Deliverables**

- [ ] Field + A11Y Matrix
- [ ] Focus states

🔗 **[Figma Design](https://www.figma.com/design/JrKkB3Lwaw8DvUzOujlvC0/DRS-%7C-Document-ID-Component?node-id=383-2418&t=gHqDaqBA9bCqPcxM-4)**

---
Will need to cover the following from Court Order Doc upload | **Ticket 34624**

### Accessibility Behaviour
Because these weren’t discussed or fully laid out, they may need to be explored a bit futher. We can move them to the next upload work if needed so we can get Corrections out the door, but we’ll need to revisit them later.

- [ ] **Upload Error Is Not Announced**

When a file fails to upload, the error appears visually, but the screen reader does not announce it. It also announces the failed file as the “Current Court Order File.”

Suggestion based on past conversations:
- Add the error to an aria-live="polite" region so it is announced when it appears.
- Use aria-describedby to connect the upload control to the error so users can hear it again when they return to the control.
- Announce the same error shown on the screen, including the filename.
- Do not identify the failed file as the current Court Order file.

Expected: The screen reader announces something like, “Unable to upload 8.5x11.jpg.”

In TEST:

----