Closed amilash closed 2 years ago
Can this be an email address for 2.0?
@reitermb @stevenino @lfrohlich @ADPennington To collaborate - please use this link to view the Microsoft Forms.
Moving this to QASP - https://reitermb.github.io/Test/knowledge-center/give-feedback.html - Please review @lfrohlich @ADPennington @stevenino @reitermb
FYI I got this error when I tried to open the teams link, but i can see it in the knowledge center
Hi @lilybl1 -- a few comments/questions:
Your feedback is important to us! We use it to ensure our team is providing proper direction and to ensure we have the opportunity to change our approach to better suit your needs if necessary.
Suggest replacing "providing proper direction" with something more specific/meaningful. For example something like "We use it to ensure that the TANF Data Portal is meeting your needs and providing a smooth user experience."
Tell us a bit more. Why did you choose that rating? Share your experience with us. What went well? What could have gone better?
How about "What do you like? What could be improved?" As written, it sounds like you'll only use it once.
Can everyone get a print out of the responses or is that just because I was given access?
The form seems to be missing the Call to Action to sign up for office hours.
@lfrohlich
@lfrohlich The CTA for office hours is at the end on the Thank you page. I didn't want to include before the survey was submitted as the office hours page will take you away from the survey and people might forget to come back to submit the survey.
@lilybl1 that makes sense. A few edits:
In addition to upcoming formal rounds of user research we'd love to offer up some unstructured time to hear from you. If you have questions about the project, feedback about elements of the current system you'd like to see TDP address, or have anything else in mind, please sign up for an "office hours" time slot here:
LGTM!
@lfrohlich The comment above, I was trying to keep the messaging consistent with what exists already that Miles has posted in other locations. Are you wanting this message to change everywhere?
@lilybl1 what would the lift be to change it everywhere else?
@stevenino I'm not just referring to the Knowledge Center - I'm looking at our prod site... https://tanfdata.acf.hhs.gov/ - my understanding is that changes here would be a new dev ticket, right?
Yeah, I agree. Just trying to say that the lift would be much larger.
@lilybl1 this looks good to me. like the reframed questions based on lauren's input. not a strong preference here but the voice switch (i.e. i like....we want...) may need some formatting so response prompt is easily distinguishable from the instructions we're offering.
@lilybl1 are you referring to message around office hours? I don't think that is in the prod site, only project updates. There's a typo in the messaging ("In addition to many upcoming structure and planned rounds") and the latter change is to make it a more direct call to action.
I pulled the content from a screenshot from Project Updates. I fixed the typo in the first sentence and added the last bit to this survey. My original question was stemming from how consistent do we want to keep this language and do Project Updates in prod need to updated as well?
Moving this to QASP - https://reitermb.github.io/Test/knowledge-center/give-feedback.html - Please review @lfrohlich @ADPennington @stevenino @reitermb
@ADPennington @lilybl1 @reitermb, I was tagged for A11y but no longer see it here. If the Knowledge-center page is in the stage of modifying, please double check the findings below:
class="usa-sidenav">
was flag for List element has direct children that are not allowed inside <li>
elementsI pulled the content from a screenshot from Project Updates. I fixed the typo in the first sentence and added the last bit to this survey. My original question was stemming from how consistent do we want to keep this language and do Project Updates in prod need to updated as well?
Let's discuss after standup today
Content looks good with latest changes. No changes need to be made to project updates wording.
@ttran-hub I moved your comments to #1693. Can you confirm if you also a11y reviewed the "Give Feedback" tab of this page?
Hi @lfrohlich, the a11y reviewed also includes the "Give Feedback" tab
Thanks @ttran-hub ! This is now complete
Description We would like to be able to provide users a place / possibly a prompt for open-ended feedback about TDP.
Notes 4/25: I think there's value to soliciting anonymous feedback (with an optional field to provide contact info / discuss in more depth) early on, the ultra light lift version probably looks like using this ticket to spin up a Google form and adding a (presumably) 1pt dev ticket to add link(s) to it in-app
Notes 4/26: To be delivered via knowledge center CTAs on articles / Google form (or similar). Nice to have, but shouldn't block other
AC:
Tasks