Merge pull request #3840 from department-of-veterans-affairs/298/mana…

…ge-benefits-tools-docs

Add page for pattern:  Manage benefits and tools, and component: Service List Item

src/_components/service-list-item.md

@@ -0,0 +1,125 @@
+---
+layout: component
+title: Service list item
+intro-text: The Service list item summarizes a benefit or tool. For example, a Service list item could show the most important details about an appointment, prescription, or benefit. It shows high-level details, offers a link to view more information, and can alert the user to any actions that need to be taken. It is always displayed in a list, as described in the “Help users to… Manage benefits and tools” pattern.
+status: use-with-caution-candidate
+research-title: Service list item
+figma-link: https://www.figma.com/design/ZIGDfSb8D5YLBdJavzDdqi/AE-Design-Patterns---Service-list?node-id=1-129&t=52qYQM9JQBOPO71q-1
+contributors: Lynn Stahl (Agile Six), Adam Whitlock (Ad Hoc), Belle Poopongpanit (Agile Six), Christine Rose Steiffer (Agile Six), Kristen Faiferlick (Ad Hoc)
+draft: true
+web-component: va-service-list-item
+anchors:
+  - anchor: Examples
+  - anchor: Usage
+  - anchor: Code usage
+  - anchor: Content considerations
+  - anchor: Accessibility considerations
+  - anchor: Related
+  - anchor: Component checklist
+---
+
+## Examples
+Storybook previews are coming shortly
+
+### With only the required elements (header, status, details)
+
+{% include component-example.html alt="A set of information—designed to be shown within a list—that contains a header, a status tag, and one set of data formatted as a “Label: Value” pair." file="/images/components/service-list-item/service-list-item-minimal.png" class="x2" %}
+
+### With the Critical information component
+
+{% include component-example.html alt="A set of information—designed to be shown within a list—that contains a header, a bright call to action, a status tag, and four sets of data formatted as “Label: Value” pairs." file="/images/components/service-list-item/service-list-item-critical-action.png" class="x2" %}
+
+### With the optional link
+
+{% include component-example.html alt="A set of information—designed to be shown within a list—that contains a header, a status tag, four sets of data formatted as “Label: Value” pairs, and a link." file="/images/components/service-list-item/service-list-item-link.png" class="x2" %}
+
+
+
+### With all possible elements
+
+{% include component-example.html alt="A set of information—designed to be shown within a list—that contains a header, a bright call to action, a status tag, four sets of data formatted as “Label: Value” pairs, and a link." file="/images/components/service-list-item/service-list-item-all-info.png" class="x2" %}
+
+## Usage
+
+### Terms
+
+* **Benefit**: Aid or assistance provided by VA to Veterans, family members, or caretakers. Examples include health care, education and training, disability compensation, life insurance, and pension.
+* **Tool**: A digital product that Veterans, family members, or caretakers use to manage benefits. Examples include appointments, prescriptions, payments, secure messages,  and claims.
+* **Service**: A term used to describe both benefits and tools.
+* **Service list**: A list of services. The [“Help users to… Manage benefits and tools” pattern]({{ site.baseurl }}/patterns/help-users-to/manage-benefits-and-tools) describes how to build a Service list.
+* **Service list item**: An item in a service list. Each item contains a summary of the benefit or tool, with a link to for the user to get more information. This component explains how to use and build a Service list item.
+
+### When to use Service list item
+
+* **When you want to show benefits or tools the user is currently enrolled in or has access to.**
+
+### When not to use Service list item
+
+* **When you are representing items that are neither a benefit nor a tool.** Do not use the same visual appearance or structured data to represent items that are not a benefit nor a tool. If you want to group short, related pieces of information that are not benefits or tools, consider using the [Card component]({{ site.baseurl }}/components/card).
+* **When you want to put links, radio buttons, or checkboxes in a container.** There are some components that have variations with containers around them. These might look like Service list items, but they are distinct. Service list items are exclusively for benefits and tools, offer a brief snapshot of information, and link to another page with more details. The guidance within the [Not a card]({{ site.baseurl }}/components/card#not-a-card) section of the Card component also applies to the Service list item.
+* **When you want to show benefits within a form.** Do not use this component to show benefits or services in an interactive list with checkboxes or other selection methods.
+* **When you want to display content in an unordered list.** Content that can be shared with bullet points should use an unordered list. Find more information in the [List component]({{ site.baseurl }}/components/list) and the [Bulleted list style guide]({{ site.baseurl }}/content-style-guide/bulleted-lists).
+
+### Anatomy or layout details
+
+{% include component-example.html alt="An annotated Service list item, calling out the header, critical information, status, details, and link." file="/images/components/service-list-item/annotated-service-list-item-component.png" %}
+
+A Service list item can have:
+
+* Header (required)
+  * The header consists of an icon (optional), header text, and chevron. These elements combine to create a link to a page with more details about the benefit or tool. All Service list items must link to a details page from the header.
+  * Headers should be visually consistent in each list item within the list. For example, if some list item headers have icons, all list items in the list should have icons.
+  * The header has a default, hover, active, focus, and visited state. See details in the [Header states section](#header-states) below.
+* Status (required)
+  * Status must be represented by a gray Tag component.
+  * Every benefit or tool in a list has a set of internal states, which are used to track the progress of enrolling in that benefit or using that tool. A status is the way to communicate the item's state to the user (such as Active, Pending, etc).
+  * Statuses do not have to mirror internal states in a one-to-one manner. (They can, but they are not required to.) Every state change does not necessarily warrant a status change.
+* Critical information
+  * This component is still under development. It navigates the user to the most direct path to take action on the critical information. Future updates will include adjustments to color contrast, focus states, and more.
+* Details (required)
+  * The details provide users with helpful information, formatted in a “Label: Value” structure (for example, “Approved on: May 5, 2011”).
+There can be anywhere from one to five lines of “Label: Value” pairs.
+* Link (optional)
+  * Some service list items might require an additional link, in addition to the details page linked to from the header and the actionable link offered in the Critical information component. In these cases, one additional link may be displayed at the bottom of the Service list item.
+The link should use the standard default, hover, focus, active, and visited link states.
+
+### Header states
+* Default: The link and chevron are the standard vads-color-link.
+* Hover: The link becomes underlined and both the link and chevron turn to vads-color-link-active. There is no background shading.
+* Focus: Similar to the default state, but with a yellow outline. The outline is similar to the focus state of action links.
+* Active: Similar to the default state, but underlined and with a yellow outline. The outline is similar to the focus state of action links.
+* Visited: Similar to the default state, but the color of the link and chevron turn to vads-color-link-visited once the link has been visited.
+
+{% include component-example.html alt="A table of headers for the Service list item. There are two columns, one for mobile and one for desktop. The five rows show each of the states described above: default, hover, focus, active and visited." file="/images/components/service-list-item/annotated-service-list-item-header-states.png" %}
+
+## Code usage
+
+(Coming soon)
+
+## Content considerations
+Teams used the Card component before this component existed. When evaluating if your team needs to use Service list items instead of cards, consider if your content is either a “benefit” or “tool,” as defined in the [Usage](#usage) section.
+
+Statuses should be normalized with CAIA so that the same terms are used when the same meanings are intended (for example, “pending” versus “in-progress”). CAIA will define which of those is correct across benefits and tools.
+
+## Accessibility considerations
+
+Review the accessibility concerns section of the following components:
+* [Card]({{ site.baseurl }}/components/card#accessibility-considerations)
+* [List]({{ site.baseurl }}/components/list#accessibility-considerations)
+* [Link]({{ site.baseurl }}/components/link/#accessibility-considerations)
+* [Link - Action]({{ site.baseurl }}/components/link/action#accessibility-considerations)
+* [Tag]({{ site.baseurl }}/components/tag#accessibility-considerations)
+* Critical information (link coming soon)
+
+## Related
+
+Service list item may be confused with several other components:
+* [List]({{ site.baseurl }}/components/list): See [When not to use Service list item]({{ site.baseurl }}/components/service-list-item#when-not-to-use-service-list-item) for information on when to use a list instead of a Service list item.
+* [Card]({{ site.baseurl }}/components/card): See [When not to use Service list item]({{ site.baseurl }}/components/service-list-item#when-not-to-use-service-list-item) and [Content considerations]({{ site.baseurl }}/components/service-list-item#content-considerations) for information on when to use a card instead of a Service list item.
+
+The below components are nested within the Service list item component:
+* Critical information (NEW; link coming soon)
+* [Tag]({{ site.baseurl }}/components/tag)
+* [Link]({{ site.baseurl }}/components/link/)
+
+{% include _component-checklist.html component_name="va-service-list-item" %}

src/_data/component-checklist/va-service-list-item.yml

@@ -0,0 +1,29 @@
+maturity:
+  - name: guidance
+    score: false
+  - name: research
+    score: false
+  - name: stability
+    score: false
+  - name: adoption
+    score: false
+code-assets:
+  - name: variations
+    score: false
+  - name: responsive
+    score: false
+  - name: interactive-states
+    score: false
+  - name: tokens
+    score: false
+  - name: internationalization
+    score: false
+visual-assets:
+  - name: variations
+    score: false
+  - name: responsive
+    score: false
+  - name: interactive-states
+    score: false
+  - name: tokens
+    score: false

src/_patterns/help-users-to/manage-benefits-and-tools.md

@@ -0,0 +1,113 @@
+---
+layout: pattern
+title: Manage benefits and tools
+draft: true
+permalink: /patterns/help-users-to/manage-benefits-and-tools
+aka: Service list
+contributors: Lynn Stahl (Agile Six), Adam Whitlock (Ad Hoc), Belle Poopongpanit (Agile Six), Christine Rose Steiffer (Agile Six), Kristen Faiferlick (Ad Hoc)
+sub-section: help-users-to
+intro-text: Follow this pattern to help users manage their benefits and tools.
+figma-link: https://www.figma.com/design/ZIGDfSb8D5YLBdJavzDdqi/AE-Design-Patterns---Service-list?node-id=1-129&t=ndStAutrvUcgt5Um-1
+github-title: manage-benefits-and-tools
+research-title: Help users to manage benefits and tools
+status: use-with-caution-available
+anchors:
+  - anchor: Usage
+  - anchor: How to design and build
+  - anchor: Examples
+  - anchor: Code usage
+  - anchor: Content considerations
+  - anchor: Accessibility considerations
+  - anchor: Research findings
+---
+
+## Usage
+
+### Terms
+
+* **Benefit**: Aid or assistance provided by VA to Veterans, family members, or caretakers. Examples include health care, education and training, disability compensation, life insurance, and pension.
+* **Tool**: A digital product that Veterans, family members, or caretakers use to manage benefits. Examples include appointments, prescriptions, payments, secure messages,  and claims.
+* **Service**: A term used to describe both benefits and tools.
+* **Service list**: A list of services. This pattern articulates how to design a Service list.
+* **Service list item**: An item in a service list. Each item contains a summary of the benefit or tool, with a link to for the user to get more information. See more details in the [Service list item component]({{ site.baseurl }}/components/service-list-item).
+
+### When to use this pattern
+
+* **When you are using the [Service list item]({{ site.baseurl }}/components/service-list-item) component.**
+* **When you want to show benefits or tools the user is currently enrolled in or has access to.**
+
+### When not to use this pattern
+
+* **When you are representing items that are neither a benefit nor a tool.** Do not use the same visual appearance or structured data to represent items that are not a benefit nor a tool.
+* **When you want to show benefits within a form.** Do not use this pattern to show benefits or services in an interactive list with checkboxes or other selection methods.
+* **When you want to display content in an unordered list.** Content that can be shared with bullet points should use an unordered list. Find more information in the [List component](https://design.va.gov/components/list) and the [Bulleted list style guide](https://design.va.gov/content-style-guide/bulleted-lists).
+
+## Design Principles
+
+* **Scannable—limited amount of information per list object**: The job of the list view is to display a summary of the object, not the entire object.
+* **Consistency of content and hierarchy**: The content should be consistent from item to item in the list and show the same types of information in each list item. For example, in a list of appointments, every appointment should have the same details (time, date, status, appointment type, etc.).
+* **Consistent implementation of supporting functionality**: If used, sort or filter functionality should interact the same despite different needs. For example, one list might sort items by date while another sorts items alphabetically, but the interaction should work the same.
+
+## How to design and build
+
+### How this pattern works
+
+This pattern vertically stacks Service list items to form a list, called a “Service list.” As noted in the [Service list item component]({{ site.baseurl }}/components/service-list-item), the user can access a page with more details about each list item by clicking or tapping on the header. Various other elements of the list item–such as a Critical information component, and status–all convey additional information to the user. View more information about these elements and their interactivity in the Service list item component.
+
+### Display order
+
+* List items should be displayed in an order that best suits the content. Common options include ordering alphabetically or by date. Check with subject matter experts and consider running usability studies to confirm the most appropriate display order for your content.
+
+* Note that when list items include a Critical information component (coming soon), these items should be displayed at the top of the list, regardless of the chosen display order. This avoids burying items that need review or action at the bottom of a list or on a subsequent page.
+
+### Components used in this pattern
+
+* [Service list item (NEW)]({{ site.baseurl }}/components/service-list-item)
+* Critical information (NEW; link coming soon)
+* [Tag component](https://design.va.gov/components/tag])
+
+## Examples
+
+### Benefits
+
+Below are some potential benefits a Veteran or family member may enroll in, which might use this pattern:
+
+* Burials
+* Careers and employment
+* Disability compensation
+* Education
+* Housing assistance
+* Life Insurance
+* Pension
+* Vocational rehabilitation (VRE)
+
+{% include component-example.html alt="A list of benefits a Veteran is currently enrolled in. Two of the benefits have critical information components shown, linking the user to a page where they can take important actions." file="/images/patterns/help-users-to/manage-benefits-and-tools/service-list-example.png" caption="An example of how this pattern can be applied to help users navigate and learn about their benefits." %}
+
+### Tools
+
+Below are some  tools that a Veteran, family member, or caretaker may use to manage a Veteran’s benefits, which might use this pattern:
+
+* Appointments
+* Claims
+* Forms
+* Letters
+* Medical records
+* Payments
+* Prescriptions
+* Secure messages
+
+## Code usage
+
+(Link coming soon)
+
+## Content considerations
+
+Statuses should be normalized with CAIA so that the same terms are used when the same meanings are intended (for example, "pending" versus "in-progress"). CAIA will define which of those is correct across across benefits and tools.
+
+## Accessibility considerations
+
+Review the accessibility considerations for the [Service list item component]({{ site.baseurl }}/components/service-list-item#accessibility-considerations).
+
+## Research findings
+
+[Secondary research](https://github.com/department-of-veterans-affairs/va.gov-research-repository/issues/810) suggests that users view lists positively and should be able to navigate through them with relative ease. This particular pattern has not yet been tested directly with users.