Digital Web Services Network: Past Events

DWSN Coordinator/presenter: we do not record these, thanks.

DWSN Coordinator/presenter: please feel free to forward the link to today’s meeting and they should be able to join right away! 

They’ll need to fill out the sign up form to be added to our distribution lists for future meeting invites, however

DWSN Coordinator/presenter: It may, or we may leverage recent discovery done through the normal quad-annual security assessment done by Department of Military.

DWSN Coordinator/presenter: Accessibility overlay tools are automated software solutions that claim to detect and fix web accessibility issues. Overlay tools work by modifying the code of a web page with a snippet of JavaScript and usually come in the form of a toolbar, plugin, app, or widget.

DWSN Coordinator/presenter: This is a great observation, we will look at making sure that features like this work for all components and list the ones that do not work.

DWSN member: Challenge – systematic customer lifecycle view.

DWSN member: Biggest challenge – adding accessibility data to thousands of scanned historical documents

DWSN Coordinator/presenter: Biggest challenge – Establishing content ownership and redefining how program folks think of web content

DWSN member: Challenge – Cross-organizational silos as a result of understaffing (esp. in the COVID age).

DWSN member: Challenge – Sufficient exposure to end users. The culture of testing and validating

DWSN member: Even if the services are disjointed, perhaps our role is to make access to each of them as intuitive, consistent and simple as possible?

DWSN member:@DWSN Member I would think of it more in this way: When you use an iPhone – everything functions in a similar way throughout very different functions. A good example of functional consistency while solving many different needs.

DWSN Guest member): @DWSN Member, have you tested with users to see if they are actually frustrated? Can be very revealing about what folks are confused about vs. what we think they’re confused about.

DWSN Coordinator/presenter: I LOVE the idea of adding cohesion across CA digital products. I think it was DWSN Member who mentioned the learning curve introduced when no two sites function similarly. The design system seems to alleviate that cognitive load for end-users and sets an expectation of how to find the information they’re looking for. The private sector, specifically sales, does an AMAZING job of this. It’s no accident that all shopping platforms have a similar look and feel with the virtual shopping cart. Or that all housing sites/apps function and look similarly. They give the people what they want/ expect which results in return users. It’s all in the design.

DWSN Coordinator/presenter: @DWSN Member – cdt.ca.gov/dwsn

All current and past presentations are made available on the DWSN website cdt.ca.gov/dwsn

@DWSN Member, The full slide deck will be available after the forum at https://cdt.ca.gov/dwsn/ You will find it under the “Prior Meetings” section.

DWSN Coordinator/presenter: @DWSN member – You’ll get a chance to see how we address this in our upcoming sneak peek.

DWSN Member: Google has an online UX program on Coursera.

DWSN Coordinator/presenter: IDEO, Norman Nielsen for UX basics.

DWSN member: I get different Lighthouse results for some of the websites that are on the leaderboard. Curious to hear about the methodology.

DWSN Coordinator/presenter: It might be where lighthouse is run from.

DWSN member: Web Dev: Measure uses default lighthouse settings which throttle bandwidth and cpu capacity to match the most common cheap android phones so you’ll see results at “Fast 3G” speeds with low end cpus. ODI’s leaderboard uses these same settings to rank state sites on performance and other accessibility metrics

DWSN member: Thank you Aaron Hans (ODI) (Guest). Did you know that this is run in the browser? Depending on the tester’s machine and the browser plugins you’ll get variable results (for most consistent results use incognito mode). I feel https://www.webpagetest.org is much more dependable and gives you consistent results because every website is tested on the same dedicated machine that doesn’t cache results.

DWSN member: Good point Marko Dugonjić webpagetest.org is a fantastic resource as well.

DWSN Coordinator/presenter: I have plentiful notes but I believe the chat is also saved

DWSN Coordinator/presenter: Britt not this one….

DWSN member: @DWSN member the datasets are neighbors right now – short answer: they can be

DWSN member: Just thinking about the UX of someone who filled out once, I think they should know if they are about to submit again. :)

DWSN member: If you’re interested in the design system, please connect with via this form.

DWSN member: @DWSN member let’s follow up separately on forms via our team Slack.

DWSN member: Long form.

DWSN Coordinator/presenter: @DWSN Member – For now we are using the icons from the state web template. We have plans to make these available as SVGs.

DWSN Coordinator/presenter: Not at the moment, all of the imagery is custom designed specifically for the design system.

DWSN Coordinator/presenter: Marko Dugonjić (Guest) it depends – I would wait for the initial design system release – you can use v6 plus components from the DS.

DWSN Member: Makes sense. Thanks!

DWSN Coordinator/presenter: We recommend using a build system and bundling your javascript for faster performance. If you do not use a build system, you can include the code from our CDN with a script tag:

<script type=”module” src=”https://cdn.designsystem.webstandards.ca.gov/components/ds-feedback/v1.0.11/dist/index.js”></script>

We can provide this instruction for CSS only components: @import url(“https://cdn.designsystem.webstandards.ca.gov/components/ds-button-grid/v2.0.2/index.css”)

We plan to have a more flexible and comprehensive solution around code bundling.