-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement 3 Key terms #1356
Comments
Hey @SamHyler! Thanks for taking this issue. To help keep everyone in the loop, please comment your Estimated Time to Completion (ETC) below! Thanks again! |
1 similar comment
Hey @SamHyler! Thanks for taking this issue. To help keep everyone in the loop, please comment your Estimated Time to Completion (ETC) below! Thanks again! |
Issue will be finished and ready to work on after about a week, depending on lead schedules and availability to meet and plan.
|
Hey @SamHyler, @emmathrash! Thanks again for taking this issue.
|
Hey @SamHyler, @emmathrash! Thanks again for taking this issue.
|
3 similar comments
Hey @SamHyler, @emmathrash! Thanks again for taking this issue.
|
Hey @SamHyler, @emmathrash! Thanks again for taking this issue.
|
Hey @SamHyler, @emmathrash! Thanks again for taking this issue.
|
Moving implementation to 2.0 as we don't have clear terms for 2 of the 3. Needs follow up discussion and work |
I will be completing this in the next sprint here. First steps: discuss terms that need clarification in Content and make decision on term 3. Currently discussing how to implement across site with Design. Figma page is opened and ready for work. |
Hey @SamHyler! Thanks again for taking this issue.
|
Key terms: Declaration (will update to be legally correct as a first step, needs follow up discussion with UXR and follow up research around accessibility), Expungement (will update across CGs and website), and people with criminal records (will discuss within Content how to create continuity, simplicity, and accessibility). |
Terms have been added (started) to the Content Guidelines (CGs). Will finalize after clarifications |
Hey @SamHyler! Thanks again for taking this issue.
|
SOT is audited and ready, @TechWriterMelissa and I are changing 2 terms site wide as the next step, and the whole content team is discussing the third team. Ready for follow-up on accessibility of declaration with UXR, will create an issue. Content will be defining terms on the website (i.e. potentially a tool tip explaining what a declaration is and possible alternative terms). However, the term can still potentially pose an accessibility problem. |
Follow-up around declaration in #1647 handed over 15/11 |
Dependency
#1629 #1630 #1631
Overview
Follow up on Content terminology research issue 999 #999 for 3 key terms.
Discuss strategy within Content before finishing this issue.
Three key terms need to be 1. added to the Content Guidelines and 2. implemented across the site.
Action Items
Resources/Notes
For extra context and project tracking - see related issue, now closed #598
This is the research slide deck the also contains info about the 3 key terms https://docs.google.com/presentation/d/1sJgFQiAtwdWQxRvjT3Kx-rBy2cbx7m-J_FKp2oHN39A/edit#slide=id.g2cecb737568_0_0
Workspace: https://www.figma.com/design/hYqRxmBVtJbDv9DJXV6nra/Expunge-Assist-Main-Figma?node-id=2-8v
UXR follow-up issue around Declaration #1647
The text was updated successfully, but these errors were encountered: