Update/date-input-guidance.md

[Charcharbinkz]

📝 Summary | Résumé

Update date input guidance to address the addition of a new format option: iso

🧩 Related Issues | Cartes liées

• Zenhub issue: #2309

🧪 Test instructions | Instructions pour tester la modification

Minor content updates

Preview links

English

• English preview

French

• French preview

✍️ Author checklist | Liste de vérification de l'auteur

Choose one (primary change type):

• This PR introduces content changes (text, images, documentation updates).
• This PR introduces structural changes (add/remove pages, navigation updates).
• This PR introduces design changes (CSS, layout, visual adjustments).
• This PR introduces development changes (scripts, utilities, features, API, domain, infrastructure).

---

Breaking / impact flag:

• This PR does not break existing links (URLs, anchors, navigation).
• If it does, redirects or migration guidance are documented under Impact/Risks.

---

Ready for review (all items must be checked):

• I have verified the English and French versions are accurate, consistent, and properly displayed.
• I have verified content follows GC Design System product content standards (if applicable).
• I have verified changes on mobile viewports.
• I have verified changes across supported browsers.
• I have checked accessibility and ensured accessibility requirements continue to meet standards.
• I have verified links, routes, and navigation behave correctly.
• I have added or updated documentation as needed.
• For visual or design changes, I have posted in the dev-design Slack channel.
• I have ensured test instructions are clear and reproducible.

🧐 Reviewer checklist | Liste de vérification du réviseur

Developer checklist (if applicable)

For complex PRs, in lieu of a simple approval or "LGTM" ✅, include the following with your approval:

• I have verified the changes using the provided test instructions.
• I have verified the site builds successfully and runs without errors.
• I have reviewed the implementation for clarity, maintainability, and potential issues.

---

Design checklist (if applicable)

For designers, include the following with your approval:

• I have verified layout, spacing, visual hierarchy, and behaviour.
• The changes align with design expectations, component guidance, and the design system.
• I have verified accessibility considerations (contrast, focus states, semantics, motion, etc.).
• I have verified behaviour matches documentation and expected interactions.
• Changes have been reviewed across breakpoints and device sizes.
• Any design inconsistencies have been raised in Slack or tracked via an issue.

---

Content checklist (if applicable)

For content, include the following with your approval:

• I understand the context and intent of the content changes.
• I have reviewed all content for clarity, readability, tone, and plain language alignment.
• I have reviewed English and French content for accuracy, terminology consistency, and parity.
• Terminology and naming follow GC and design system standards.
• I have verified links, references, and examples are correct and functional.
• I have verified descriptive (alt) text for accuracy and brevity.
• The content follows and does not contradict design system guidance elsewhere on the site.
• No spelling, grammar, or formatting issues are present.

⚠️ Impact/Risks | Risques

Optional: Highlight any potential implications, risks, or important notes for reviewers or maintainers (e.g., breaking changes, domain changes, removed pages, dependency updates, performance implications, etc.).
Highlight any deprecations or migration guidance here.

[aws-amplify-ca-central-1]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-796.djtlis5vpn8jd.amplifyapp.com

[aws-amplify-ca-central-1]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-796.d35vdwuoev573o.amplifyapp.com

[ethanWallace]

Could it be confusing to have this information laid out like this since the month, day, year format is only available in English and the day, month, year is only available in French?

[Charcharbinkz]

Yeah this is a bit tricky. Thanks for flagging it.

In Figma, all options are available for selection regardless of what language is being used. (The language toggles after the format is selected) I tried to flag that one is for French written formats, one is for English. But you're right, it's still confusing.

I'll try to make this a little more obvious that m/d/y = English only and d/m/y = French only.

[nmakuch]

LGTM

[nchoquet]

French content updated to match EN

[Charcharbinkz]

LGTM!

[Charcharbinkz]

@daine ready to be reviewed and merged whenever makes sense for the code implementation.