bcgov / bcgov/entity

UI Design - DRS | Document Record Component Enhancement

Open
#33,665 1 comment 0 reactions 1 assignee Claimed by @liz-govier View on GitHub
Colin Egress DRS Corps UX
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

Original MVP criteria | [Assets Ticket 27736](https://app.zenhub.com/workspaces/assets-team-space-new-655515cb02e714000e74f9f3/issues/gh/bcgov/entity/27736)

**[Figma Design](https://www.figma.com/design/JrKkB3Lwaw8DvUzOujlvC0/DRS-%7C-Document-ID-Component?node-id=197-2180)**

**[Field Matrix](https://bcgov.sharepoint.com/:x:/r/teams/07717/Shared%20Documents/DRS%20(Document%20Record%20System)/Design/DRS_Field+A11y%20Matrix.xlsx?d=w13f0e575067e4fc58d23c6c37ae7d372&csf=1&web=1&e=Q7lytd)** _(In progress)_

---

### Design Requirements
Based on requirement meetings with staff, the following enhancements are needed to improve their workflow efficiency by reducing unnecessary steps and saving staff time when processing filings:
- Allow staff to enter all required document record information directly within the filing.
- Look into digital stamps to reduce the paper scan process
- Eliminate the need for staff to open the document record separately to enter or review information.

### Component Requirements
The component should include the following enhancements:
- Make sure updates are completed in NUXT
- Add Digital Stamps to the form
- Add functionality to upload documents
- Provide an option to proceed when there are no supporting documents
- Allow staff to both scan and upload documents within the same filing, rather than limiting them to one option
- Add Pages to Scan.
- Add Scan Details
- Add Document Record Notes

### WCAG 2.1 AA Accessibility Requirements

- Use clear labels for all form fields.
- Make sure staff can navigate the form using a keyboard.
- Ensure text, buttons, and fields have enough colour contrast.
- Do not use colour alone to show errors, required fields, or other important information.
- Provide clear error messages when information is missing or incorrect.
- Use clear and meaningful names for buttons, links, and other controls.
- Ensure the form works with screen readers and other assistive technologies.
- Make sure the tab order follows the flow of the form and clearly shows which field is selected.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.