Implement UX recommendations for VBA fieldset of VA Service Taxonomy

[davidmpickett]

User Story or Problem Statement

AS an editor of nationalized VBA content (OCTO-DE, CAIA, Sitewide team),
I NEED to understand what each field in the VA Service taxonomy does
SO THAT I can enter appropriate content

Description or Additional Context

• Figma design
• Add new VA Service term form
• Related KB ticket

Steps for Implementation

VBA fieldset widget

Preview Give feedback

1. Change the form display widget from Fieldset to Details
2. Check the "Display element open by default" setting
3. Fieldset should now function as an accordion like VAMC and Vet Centers fieldsets
4. Add a description - These fields determine what service details are displayed on VA benefit office pages. For example, Portland VA Regional Benefit Office (opens in a new window).

Fields to remove / re-label

Preview Give feedback

1. Type of care -> rename to Service category
2. VBA patient friendly name -> remove this field
3. VBA common conditions -> remove this field
4. VBA description -> National service description

Add character counters to these fields

Preview Give feedback

1. Follow guidance for widget settings in Experimental Design for Character Counters on Text Fields #16659
2. Regional service header
3. Regional service description
4. Facility service header
5. Facility service description

Add help text to these fields

Preview Give feedback

1. National service description - Add a few sentences explaining the overall scope of the service.
2. Regional service header - Add a short, action-oriented sentence that describes the primary task at a VBA Service Region. For example, “Get help checking the status of your COE.”
3. Regional service description - Add a short sentence listing additional tasks at a VBA Service Region. Leave this field blank if the Regional service header already covers all tasks.
4. Facility service header - Add a short, action-oriented sentence that describes the primary task at a local benefits office. For example, “Get help requesting a COE or filling out paperwork.”
5. Facility service description - Add a short sentence listing additional tasks at a local benefits office. Leave this field blank if the Facility service header already covers all tasks.
6. Online self-service (change) - Link to a page that helps users manage this service online.

Might need discussion

Preview Give feedback

1. URL and Link text -> I believe the help text for these subfields is hardcoded in Drupal core and therefore not able to be customized per instance of a Link field
2. VBA Service Regions -> I don't know why this field was added to the taxonomy. The Service Region will set what term it is associated with on creation, so if anything this field should just be a list of associated Service Regions. But I'd say it can just be removed. Unless it's used in GraphQL query? Can probably punt this discussion to #18000

Acceptance Criteria

• Special considerations for Fields that are deleted/removed?
• Drupal interface matches Figma design
• Character counters function as intended
• Requires design review
• Requires accessibility review