LCFS - Company Overview Comment Font Size Consistency After Save
- Dominant language
- Python
- Stars
- 6
- Forks
- 6
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 87
Description
**Describe the task**
Update the Company Overview comment feature within the Organisation Dashboards so that comments display at a consistent font size before and after saving. Currently, the comment text changes to 20px after it is saved, when it should remain at 16px.
**Purpose**
Ensure a consistent user experience and maintain visual accessibility standards by displaying comment text at the intended 16px size throughout the comment lifecycle. This improves readability, reduces visual inconsistency, and supports WCAG 2.2 accessibility expectations for content presentation.
**Acceptance Criteria**
- [ ] Saved comments display at 16px font size, matching the font size used during comment entry.
- [ ] Font size remains consistent across create, save, edit, and view states of a comment.
- [ ] The updated behaviour is validated across supported browsers and devices, with no visual regressions.
- [ ] The comment feature continues to meet WCAG 2.2 accessibility requirements for readability and content presentation.
- [ ] Keyboard-only users can create, save, edit, and review comments without any change in visual presentation or focus issues.
**Additional context**
- Current behaviour: comment text displays at 20px after being saved.
- Expected behaviour: comment text should remain at 16px before and after saving.
- Review associated comment display styles to ensure no other comment states inherit unintended font sizing.
- Include UX validation to confirm the saved comment experience remains visually consistent throughout the workflow.
Contributor guide
Research direction
Start with the Company Overview comment entry, save, edit, and view states, then inspect the associated comment display styles for the differing font size. Done means comments remain 16px through each state, keyboard-only workflows remain usable, and browser or device checks show no visual regressions.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100