bcgov / bcgov/entity

UI - Corrections | Enhancements: Resolution/Court Order Component

Open
#34,525 0 comments 0 reactions 0 assignees View on GitHub
Colin Egress enhancement UX Assurance
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

These are enhancements that will need to be addressed post migration.

**Update date pick to match base component:**

- [ ] Keyboard focus tabbing states (Calendar, show less/show more, Split buttons)
- [ ] Screen reader announcements match the base component for key interactions (e.g., field focus, opening the calendar, icon buttons, clearing the field, and selecting or entering a date)

---

- [ ] **Disable Selection of Future Date** Moving to enhancement [ticket #34535](https://app.zenhub.com/workspaces/colin-egress-team-6904d552be2bb0000fa13ad6/issues/gh/bcgov/entity/34525)
Would it be possible to disable future dates on the calendar, rather than letting users select one? It seems like an unnecessary extra step for them to work around, so disabling it outright would make things simpler. (Disable hex # 757575)
Screenshot 2026-07-28 at 3.27.35 PM.png

- [ ] **Error clearing on valid date selection**
When I select a valid date (not in the future), I still get an error until I tab out. Would it be possible to have the error clear as soon as the date becomes valid, instead of waiting for tab out?

**Note: if we end up disabling future dates per the point above, this won't need validation.**

----

**UI updates that were missed first round | _System-Wide updates, where applicable_**
- Helper text should be 16px not 14px
- Deleted/diabled text should be Hex# 757575, currently to light at # 212529

Screenshot 2026-08-12 at 10.34.50 AM.png

Screenshot 2026-08-12 at 10.34.42 AM.png

Contributor guide

No contributing guide indexed for this repository

Research direction

Locate the Resolution/Court Order date component and its base component, then compare their keyboard focus, screen-reader behavior, date validation, helper text, and disabled text styles. Check the enhancement ticket #34535 before starting. Done means the listed interactions and visual updates match the base component and valid-date behavior is correct.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
accessibility, design, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.