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

Nobody has claimed this yet.

Assessment

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

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.

Description

Medium Task UX

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.
Dominant language
Python
Stars
7
Forks
7
Avg merge
2d 13h
Merged PRs (30d)
78

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bcgov/lcfs

All issues in bcgov/lcfs

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.