Heading structure in Service Accordions is not helpful to user

[laflannery]

Description

This is somewhat related to the ticket regarding "Appointments" showing with no content but ultimately because we have so many headings, and it's all connected to other templates, they aren't hierarchical like they should be.

For example, the phone number under appointments should be an h6 but there is really no reason to be going that far down, which is why I'm advocating to just get rid of these headers here - they aren't necessary.

The bigger issue is that having the heading level the same is potentially going to create more confusion because it's muddying the relationship of these elements

Acceptance Criteria

• Determine if it is possible/feasible/desirable to update headings without touching VAMCs
• If so, determine how to update the headings for the best UX and a11y experience
• Requires design review
• Requires accessibility review

[davidmpickett]

This might need to be split into a few tickets to cover the various places where we are using headings that we want to move toward bold/strong text instead.

- VBA main page template
- Should be pretty small scope and could be launch blocking
- I think Location and Contact information is the main area to fix
- Address, phone numbers, and office hours

• VBA & VAMC service accordions
  • I think we should fix these on VAMCs and VBA at the same time since they share partial templates

- Other places on VAMCs
- Etc.

[Agile6MSkinner]

To Dave's comment, let's split out another ticket for the Man Page Template, which will will consider launch blocking. This ticket will stay in the backlog for fast follow/national rollout. I will work with @laflannery and/or @davidmpickett to create the ticket.

[laflannery]

To be clear, this ticket is referring to the heading structure within the accordions, as described in the description above. The headings outside the accordions, while eventually they could probably be improved, they aren't hindering the user's ability to understand the content.

[Agile6MSkinner]

After talking with @laflannery we are moving this to the national rollout epic because it is related to a more global issue and will require a lot of design discovery. It's not a high-priority issue, it just looks bad.

@thejordanwood Do you have an epic that this could be included in or a design discovery ticket that we could set as a pre-req?

[davidmpickett]

@thejordanwood Do you have an epic that this could be included in or a design discovery ticket that we could set as a pre-req?

• @thejordanwood did some work on this before as part of Design updates for VAMC non-clinical contact information #17342
• That ticket is part of a catchall epic for anything about service locations or service accordions Improve services accordions and service locations across Facilities products #17350
• Likely would need a "Finalize design recommendations for Service Accordion visual hierarchy" ticket ala Finalize design recommendations for Service Location Address paragraph type #17489

[davidmpickett]

To be clear, this ticket is referring to the heading structure within the accordions, as described in the description above. The headings outside the accordions, while eventually they could probably be improved, they aren't hindering the user's ability to understand the content.

Updated ticket title to reflect this scope

[Agile6MSkinner]

@davidmpickett @thejordanwood Do we think that the work described here is discrete or will it be taken care of in other issues/tickets/epics?

[davidmpickett]

@davidmpickett @thejordanwood Do we think that the work described here is discrete or will it be taken care of in other issues/tickets/epics?

To my knowledge this is the only place this work is documented in a ticket. This could potentially be a fix to make during AP template migration.