[CONSIDER] Force location name (to avoid heading level defects)

[mmiddaugh]

Issue Description

the absence of a H4 location name caused a skipped heading level, identified as a 508-defect-2: #15701. The defect has been resolved. However, it was proposed by Ryan to force a location name to avoid causing this issue in the future.

Location names, such as Center for Treatment of Addictive Disorders, (seen within Addiction and Substance Abuse Treatment), use H4 headings, making the H5 for **Hours** and Phone headings appropriate.

  

Without this H4 location name heading, **Hours** and Phone headings skip a level.


---

Tasks

• [ ] Determine business rationale for location names as mandatory

Acceptance Criteria

• [ ] What will be created or happen as a result of this story?

  How to configure this issue

• [ ] Attached to a Milestone (when will this be completed?)
• [ ] Attached to an Epic (what body of work is this a part of?)
• [ ] Labeled with Team (product support, analytics-insights, operations, service-design, tools-be, tools-fe)
• [ ] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
• [ ] Labeled with Type (bug, request, discovery, documentation, etc.)

[mmiddaugh]

Should be addressed as part of #13140 VA Services Taxonomy improvements / iterations

[jilladams]

@laflannery FYSA this exists

[laflannery]

@jilladams These headings were worked on in a different ticket to get rid of the skipping heading levels.

• Accordions are now H3s (after the work PWs did which was separate)
• "Contact Information" is now an H4 instead of H3
• All headings under that are H5 (that was unchanged)

[jilladams]

And that satisfies this issue / we're ok to close?

[laflannery]

Yep, I wasn't sure if anyone else (i.e. Michelle) needed to review or be aware but I'll close if you're good!