Skip to main content

Say Hi

We'd like to hear from you. Whether you've found an error, have a suggestion for improvement, or just want to share how you're using these resources, we read every message.

How to reach us

General inquiries: hello@theuxshop.com

This is the best way to reach us for most things:

  • Questions about content
  • Suggestions for new topics
  • Feedback on existing guides or patterns
  • General comments

Error reports: hello@theuxshop.com

When reporting an error, please include:

  • The URL of the page with the issue
  • A description of what's wrong
  • If it's a technical issue, your browser and device

Security issues: security@theuxshop.com

If you've discovered a security vulnerability, please report it directly rather than publicly. See our security policy for details on responsible disclosure.

Response times

We aim to acknowledge messages within a few business days. For straightforward error reports, we often push fixes faster than we send replies. If you've reported something and see it fixed on the site, that's our response.

For more complex suggestions or questions, it might take longer to provide a thoughtful reply. We prioritize reading everything over responding quickly to everything.

What we can help with

Content questions: Clarifications about guides, patterns, or tools. If something's unclear, we want to know so we can improve the explanation.

Error corrections: Typos, broken links, incorrect information, outdated guidance. These are high priority and usually fixed quickly.

Suggestions: Ideas for new content, improvements to existing content, or features you'd find useful. We can't implement everything, but we track suggestions and consider them when planning updates.

Accessibility issues: Problems using the site with assistive technology, or accessibility concerns with our guidance. These are treated as high priority.

What we can't help with

Project-specific consulting: We can't provide custom UX advice for your specific project. The guides and patterns here are meant to be general-purpose resources you can apply to your own context.

Tool support beyond our own: If you're having trouble with a third-party tool or platform, we can't provide support. We can only help with the tools hosted on The UX Shop.

Employment inquiries: We're not currently hiring. We'll update this if that changes.

Before reaching out

For common questions, check the FAQ sections on individual pages and the site-wide FAQ on the about page. Your question might already be answered there.

Meeting requests

We occasionally accept meeting requests for substantive discussions about UX practice. If you'd like to discuss something that doesn't fit in an email, mention that in your initial message and briefly describe what you'd like to discuss.

We prioritize:

  • Accessibility practitioners and advocates
  • Educators using these materials in teaching
  • Discussions that might improve the resources for everyone

A note on response expectations

We're a small team maintaining this as a resource for the community. While we strive to be responsive, there may be times when responses are slower than we'd like. We appreciate your patience.

If you've sent something urgent (like a security report or a significant error affecting many users), and haven't heard back in a week, please follow up—it may have slipped through.

Do you offer consulting or workshops?

Our focus is on maintaining these free resources. We don't currently offer paid consulting or training services.

Can I interview someone from The UX Shop for an article or podcast?

We occasionally participate in interviews if the topic aligns with our work. Send a brief description of what you're working on and what you'd like to discuss.

How do I report a broken link?

Email hello@theuxshop.com with the URL of the page containing the broken link and, if possible, where the link was supposed to go. We'll fix it promptly.

I sent an email and haven't heard back. What should I do?

If it's been more than two weeks, please follow up. Emails occasionally get lost or buried. For time-sensitive issues like security reports, following up after a week is appropriate.