We’d welcome hearing from you link feedback

[AnnaGingle]

Current Behavior

Hi .gov team! I was poking around the public help docs on get.gov and wanted to share some feedback.

The We'd welcome hearing from you link on this blog post navigates to the contact us page.

• I was expecting a form or mailto: link to open directly. Beyond that, the contact us page doesn't have a clear CTA for what to do if I think I'd be a good fit for enterprise mode, or for submitting general feedback and feature requests.
• This might fail the 2.4.4-link-purpose section 508 success criteria. I don't have all the up-to-date context, so you are best suited to make that call.

This might not be relevant if all enterprise-eligible orgs are already onboarded, but an opportunity crossed my mind that feels significant for similar scenarios. Last I checked, get.gov was in the top million pages visited (according to the 2024 WebAIM Million report), which means there's a real chance to hear from a large user base.

On a project I work on now, we surface our help desk email throughout the app and specify that feedback and feature requests should go there. We also offer an optional survey where users can share what they'd like to see or what isn't working. We hear from users consistently, and it's shaped our roadmap in meaningful ways.

Expected Behavior

A few specific ideas:

• If the We'd welcome hearing from you link fails 2.4.4-link-purpose, update it to clearly communicate to the user that they will be navigated to the contact us page if the link is clicked.
• Alternatively, include content and instructions on the contact us page specifically for enterprise mode interest, if still relevant.
• Update the We'd welcome hearing from you link with a direct mailto: link (if that's the desired communication channel)
• Separately, add content to the contact us page that specifies where to send feedback or feature requests, separate from general support

Steps to Reproduce

1. Navigate to this blog post
2. Click the We'd welcome hearing from you link found at the bottom of the blog post

Environment

Prod

Additional Context

No response

Issue Links

No response

[h-m-f-t]

Hi @AnnaGingle! Nice to see your name online. Thanks for sharing this!

I agree we can be more clear about where that link is going to send a user. We do intentionally push people to /contact instead of giving contact info directly (like in a mailto:) because that allows us to modify our support mechanism in one place, which is a constraint we've had to deal with. I think we'll likely update the text of the blog post and add some content to the contact us page about feedback or feature requests.