Skip to content

fix(SDK-1261): hide the visible Status column header label - #2719

Open
krisxcrash wants to merge 1 commit into
mainfrom
kw/fix/sdk-1261-status-column-header
Open

fix(SDK-1261): hide the visible Status column header label#2719
krisxcrash wants to merge 1 commit into
mainfrom
kw/fix/sdk-1261-status-column-header

Conversation

@krisxcrash

Copy link
Copy Markdown
Contributor

Summary

  • The "Upcoming payroll" table's Status column renders empty for unprocessed payrolls with no calculatedAt and a deadline either absent or more than 14 days out — an intentional gap in the status rule set (there's a passing test asserting 0 badges for exactly this case), not addressed here.
  • Per the reported fix, this only removes the visible "Status" header label, leaving the column and its cell logic untouched.
  • Reuses VisuallyHidden, the same pattern DataTable already uses for its own built-in select/actions column headers, so the column keeps an accessible name for screen readers.

Jira: SDK-1261

Test plan

  • PayrollList.test.tsx / PayrollListPresentation.test.tsx pass (31/31)
  • eslint/tsc --noEmit clean
  • Confirm in the browser that the Status column header shows no visible text, and inspect the accessibility tree to confirm the column still has an accessible name

The Status column reads empty for unprocessed payrolls outside the
14-day due-soon window -- an intentional gap in the status rule set,
not something this change addresses. Per the reported fix, the visible
"Status" header label is removed while keeping the column and cell
logic intact, using the same VisuallyHidden pattern DataTable already
uses for its own select/actions column headers so the column keeps an
accessible name.
@krisxcrash
krisxcrash marked this pull request as ready for review September 4, 2026 23:35
@krisxcrash
krisxcrash requested a review from a team as a code owner September 4, 2026 23:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant