Q: How do we get our website(s) announced as using USWDS?
A: You can email us at [email protected].

Q: Is there an update regarding the incorporation of a Toast component in the design system? I see that the component proposal is in the ‘discussions started’ phase.
A: Great question! We've been leaving the discussion open for others to contribute their thoughts, but our current opinion is that items that disappear without user interaction probably introduce accessibility concerns for government sites. We plan to say more about this in that discussion soon.

Q: Are there plans to offer a more robust table component with lots of (now standard elsewhere) features that will be more conducive for web application and modernization efforts? Specifically, I need tables that are searchable, actionable, have in-line edit capabilities, etc.
A: We have some requests in our repo related to tables currently open for voting. Any additional information you can add or even upvoting helps us understand requests and prioritize in the future.

Q: Do designers often design multiple pages at once, as for CSS? Or, is that only for developers?
A: Each team and project has their own process, but generally, yes. A component-based design approach is popular and effective for designers as well as developers. This establishes commonality across pages and establishes internal consistency across a website or application.

Q: Will USWDS utilities be continuing in the new Web Components future?
A: Yes. We currently don’t have any plans for getting rid of utilities once USWDS Web Components are released. They still play an important role for prototyping and in some kinds of style customization. With Web Components, we'll work to integrate utilities with CSS variable–based tokens. How tokens and utilities will work together and with our Web Components is still an open discussion, but we still see a role for utilities moving forward.

Q: Would it be possible to share the survey used to gain information from the population on their design system use?
A: We've now archived the survey form, but we plan to publish a summary of the results in our research wiki. We don’t have an expected publication date yet, but we’ll be sure to share when it’s live. If you are interested in anything specific, please reach out to us on Slack or via email and our UX researcher can respond with more details.

Q: Have you aligned on using shadow DOM or light DOM with your components?
A: We will most likely use a mixture of both, depending on the component. We’re on the path of using HTML enhanced web components, which uses some light DOM. For other components it might make more sense to rely more on shadow DOM. It’s something we’re exploring and will share updates via GitHub and Monthly Calls as we have more to share. But for our alpha and beta components, we are currently using shadow DOM.

Q: Can Web Components be server-rendered?
A: In general, it’s possible to render Web Components on the server using declarative shadow DOM. Lit, the library we’re currently using to implement our Web Components, does have a pre-release plugin to make server-side rendering (SSR) easier. However, components need to be written with SSR in mind in order to use this approach. In particular, components need to avoid calling on browser APIs that won’t be available when the code runs on a server.

While we haven’t decided our approach to ensure that Web Components work before JavaScript is able to run, we’re mindful of adding additional complexity for teams who want to use components in a resilient way, but might not have the resources to implement support for SSR.

Q: Looking at the different ways to model Web Components, did you find any pros/cons with how search engines might parse them?
A: Our research indicates that search engines support Web Components (and the shadow DOM), just like they do other content rendered with JavaScript. We’re currently focused on matching existing component functionality, making components themable, and maintaining accessibility.

Q: Is there a theme that can be imported for Salesforce?
A: We have a Salesforce lightning implementation listed on our site that you may find useful, but let us know if you are looking for a different tool.