Enhancing Component Testing for Better User Experience

uswds monthly call january 2023 january 2023 n.w
1 / 60
Embed
Share

Explore how the USWDS team incorporates real user testing in their component development process to improve accessibility and user experience. Learn about their internal review practices and commitment to engaging with developers and the community for continuous improvement.

  • User Testing
  • Component Development
  • Accessibility
  • User Experience
  • USWDS

Uploaded on | 1 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.

E N D

Presentation Transcript


  1. USWDS Monthly Call January 2023 January 2023 1

  2. Hi! Thanks for being here! Thanks for being here! 2

  3. USWDS FAQ Component testing Tabs Design kits Theming USWDS Custom fonts and colors Banner flash USWDS in other frameworks Importing USWDS component JavaScript 3

  4. James Mejia he/him Engineer USWDS Core Team Contractor 4

  5. Amy Leadem she/her Front End Developer USWDS Core Team Contractor 5

  6. USWDS FAQ Our frequently asked questions 6

  7. Do we test components with real users before releasing? 7

  8. Yes and no. And we can also do better. 8

  9. We always do an internal review that includes manual accessibility testing 9

  10. We always review our work with developers and our community 10

  11. Weve started adding testing with real users of assistive technology 11

  12. This has proven extremely valuable 12

  13. We always respond to issues in our code repo 13

  14. Testing with real users needs to be an ongoing part of a component s lifecycle 14

  15. Accessibility-first usability testing is a big focus of our short-term roadmap 15

  16. More to come this year 16

  17. Whats going on with Tabs? 17

  18. Were designing a repeatable process. And it s going slowly. 18

  19. If you wish to make an apple pie from scratch, you must first invent the universe. Carl Sagan 19

  20. Fair, practical, and repeatable. 20

  21. Common component acceptance criteria checklist 21

  22. Component lifecycle model 22

  23. Pattern-first development. 23

  24. We appreciate your patience. 24

  25. When will the design kit be updated? 25

  26. We update the design kit after every release with design changes. 26

  27. Sketch Adobe XD Figma 27

  28. Coming Spring 2023. github.com/uswds/uswds-for-designers 28

  29. Are you allowed to change how USWDS looks? 29

  30. Yes. 30

  31. We want USWDS to be a tool for designers 31

  32. Make decisions faster 32

  33. Start with defaults and customize with tokens 33

  34. Experimentation drives adaptation 34

  35. Let us know what you find. 35

  36. How do you set custom fonts and colors? 36

  37. Its all in settings. 37

  38. Use tokens when possible 38

  39. System color tokens Over 400 colors in 25 color families, like red- 30 and blue-warm-40v 39

  40. Theme color tokens Type-based tokens used in our component stylesheets, like base and primary-light. 40

  41. @use "uswds-core" with ( $theme-color-primary-lighter: "gold-30v", $theme-color-primary-light: "gold-40v", $theme-color-primary: "gold-50v", $theme-color-primary-vivid: #F5CA55, $theme-color-primary-dark: "gold-60", $theme-color-primary-darker: "gold-70", ) Adding custom colors via settings then using the customized token in component code. .example { background-color: color("primary-vivid"); } 41

  42. Accessibility considerations Use color settings when possible and get built-in contrast checking Do this: @use "uswds-core" with ( $theme-color-primary: #8068D8, $theme-link-color: "primary"; ) Not this: a { color: #8068D8; } 42

  43. Adding a custom font 43

  44. Adding a font from a hosting service 1. Add a reference to the JavaScript and CSS provided by the font hosting service in the head of your markup 2.Create a new font token in USWDS 3.Use the font new token in your theme 44

  45. @use "uswds-core" with ( $theme-typeface-tokens: ( "lato": ( "display-name": "Lato Web", "cap-height": 364px, "stack": "Helvetica Neue", Helvetica, Roboto, Arial, sans-serif', ), ), $theme-font-type-sans: "lato", $theme-font-role-heading: "sans", ) Creating and using a new font token Define the typeface token, assign it to a font type, and use it in your stylesheets. .example { @include u-font("sans", "md"); } 45

  46. Adding a self-hosted font 1. Create a new font token in USWDS 2.Assign this new token to font type 3.Add custom path information for this font type 4.Use the new font type token in your theme 46

  47. Given a path: [$theme-font-path]/lato/Lato-Regular.otf [$theme-font-path]/lato/Lato-Regular.ttf Adding custom path information for a font type You ll need .woff, .woff2, and .ttf versions of your self- hosted font. Use settings like: @use "uswds-core" with ( $theme-font-sans-custom-src: ( dir: "lato", roman: ( 400: "Lato-Regular", 700: "Lato-Bold", ), italic: ( 400: "Lato-Italic", 700: "Lato-BoldItalic", ), ), ) 47

  48. Considerations 48

  49. How do I stop the banner from flashing open on page load? 49

  50. Use the uswds-init script. 50

More Related Content