Empty table header cells in data tables in CMS

[laflannery]

Description

Still an issue in D10

There are data tables within the CMS that are missing content within the table header cells. Empty table header cells create confusion for users as they may not be able to fully understand the content in the associated table data cells.

Additional Context

List of tables where this was found (may not be the full list of all tables within the CMS):

• VAMC Facility Edit screen: Hours Table
• VAMC Facility Non-Clinical Service Edit screen: Hours Table
• VAMC System Billing and Insurance Edit screen: Hours Table
• VAMC System Operating Status Edit screen: System-wide alerts Table
• VAMC System Operating System Edit screen: Facility Operating statuses Table
• Vet Center Dashboard: Satellite Locations Table
• Vet Center - Locations List Edit screen: Display additional mobile vet centers Table
• FAQs Page Edit Screen: Q&As Table
• Checklist Edit Screen:
  • VA Benefits Hubs Table
  • Contact Information Table
• FAQs Page Edit Screen:
  • VA Benefits Hubs Table
  • Contact Information Table
• Image List Edit Screen:
  • VA Benefits Hubs Table
  • Contact Information Table
• Resources and Support Detail Page Edit Screen:
  • VA Benefits Hubs Table
  • Contact Information Table
• Step-By-Step Edit Screen:
  • VA Benefits Hubs Table
  • Contact Information Table
• Video List Edit Screen:
  • VA Benefits Hubs Table
  • Contact Information Table

Screenshot

Accessibility Standard

WCAG version 2.0 A, Criterion 1.3.1

Acceptance Criteria

• Technical review to determine feasibility of adding content to table headers
• UX/IA to determine what content should say
• Implementation ticket created

CMS Team

Please check the team(s) that will do this work.

• Program
• Platform CMS Team
• Sitewide Crew
• ⭐️ Sitewide CMS
• ⭐️ Public Websites
• ⭐️ Facilities
• ⭐️ User support

[laflannery]

Updated description to indicate which ones were remediated by update to office_hours module

[laflannery]

@ndouglas Does this need to be broken up into product tickets? It's not just one field type or markup that generates tables this way and would be one ticket?

[ndouglas]

@laflannery

For Benefit Hub(s), are you referring to this interface when you select Benefit Hubs?

Or are you referring to the field as it appears "at rest"?

[laflannery]

At rest, the modal doesn't actually have headers (which is neither here nor there at the moment but possibly something that should have another ticket)

[ndouglas]

@laflannery It seems most of these can probably be fixed in a hook that injects "Weight" (or something else?) in the table header for certain fields. I'll defer to @edmund-dunn and @tonytaylor on implementation, though. I think this can all remain in one ticket, unless either of them disagree.

[laflannery]

@ndouglas thank you for looking! It's definitely a lower priority but I started going through a lot of tickets today so I just wanted to split this up if I needed to. I really appreciate you taking the time!

[srancour]

This is something that still exists and should still be worked on.