[Content styleguide] The content has spelling, punctuation, or typo errors. (05.02.1)

[shiragoodman]

General Information

VFS team name

10-10 Health Apps

VFS product name

10-10EZR

VFS feature name

Health Benefits Update form

Point of Contact/Reviewers

Rebecca Ferguson - @rferguson13 - Content

*For more information on how to interpret this ticket, please refer to the Anatomy of a Staging Review issue ticket guidance on Platform Website.

---

Platform Issue

The content has spelling, punctuation, or typo errors.

Issue Details

Insurance information > What is your Medicare Part A effective date? - The example date doesn’t have commas between the day and the year, which is incorrect formatting.

Link, screenshot or steps to recreate

VA.gov Experience Standard

Category Number 05, Issue Number 02

Other References

Platform Recommendation

Please revise by adding a comma between the day and year so the example date formatting is correct.

---

VFS Guidance

• Close the ticket when the issue has been resolved or validated by your Product Owner
• If your team has additional questions or needs Platform help validating the issue, please comment on the ticket
• Some feedback provided may be out of scope for your iteration of the product, however, Platform's OCTO leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue.
• If you do not believe that this Staging Review issue ticket is the responsibility of your team, comment below providing an explanation and who you believe is responsible. Please tag the Point of Contact/Reviewers. Governance team will research and will follow up.

[longmd]

@shiragoodman / @rferguson13 , this appears to be a global issue with the va-memorable-date web component. This is appearing everywhere where the memorable date pattern is used.

You can see it in the Storybook sample, too: https://design.va.gov/storybook/?path=/docs/uswds-va-memorable-date--default

cc: @hdjustice / @alexseelig

[shiragoodman]

thanks for the info, @longmd !

I have added the Design System team label and am tagging @caw310 and @micahchiang for awareness. Once they confirm that this is a Design System issue, we'll get your teams label removed from this ticket.