bcgov / bcgov/lcfs

LCFS - Correct Column Title for "Any Additional Factors" in Discretionary Penalty Table

Open Beginner friendly
#4,923 0 comments 0 reactions 0 assignees View on GitHub
Medium Task UX
Dominant language
Python
Stars
6
Forks
6
Avg merge
2d 7h
Merged PRs (30d)
87

Description

**Describe the task**
Update the column title for "Any Additional Factors" within the Discretionary Penalty table on the Penalty Log tab of the Organisation Dashboard to correct the existing spelling error.

Image

**Purpose**
Ensure user-facing content is accurate, professional, and consistent with approved business terminology. Correcting the column title improves usability, reporting quality, and accessibility by ensuring screen readers announce the correct wording.

**Acceptance Criteria**
- [ ] The column header is updated to display "Any Additional Factors" with the correct spelling.
- [ ] The corrected column title is displayed consistently across all views where the table appears.
- [ ] The corrected column title is reflected in any exports, downloads, or reports generated from the table, where applicable.
- [ ] Screen readers announce the corrected column title accurately.
- [ ] No visual or functional regressions are introduced as a result of the update.

**Additional context**
- The issue exists within the Discretionary Penalty table on the Penalty Log tab of the Organisation Dashboard.
- This is a content correction and does not require changes to business logic.
- Review surrounding table headers to identify any similar content quality issues.
- Validate compliance with WCAG 2.2 accessibility requirements.
- Test across supported browsers and devices to confirm consistent behaviour.

Contributor guide

Open the contributing guide

Research direction

Start at the Organisation Dashboard's Penalty Log tab and locate the Discretionary Penalty table and its "Any Additional Factors" column header. Update the spelling, then verify the corrected title in every table view and applicable export or report, including its screen-reader announcement, without changing business logic.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
accessibility, frontend
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.