Difference between revisions of "June 5, 2024 - Updates, priorities of the week"

From wiki
Jump to navigation Jump to search
(Created page with "Back to GC Web Priorities Meetings - Réunions des Priorités Web du GC ==Meeting information== ===Agenda=== 1. Updates 2. Roundtable =Notes and action item= ===Updates==...")
 
 
(2 intermediate revisions by the same user not shown)
Line 7: Line 7:
 
=Notes and action item=
 
=Notes and action item=
 
===Updates===
 
===Updates===
−
'''PCO'''
+
'''New UX Community of practice'''
−
*Thanks to the community for sharing your May promos with us
+
 
−
'''Stephane Bachard - New reporting requirements - Supply Chains Act reporting requirements'''
+
* First meeting on June 20 at 1pm
−
*This is a policy led initiative
+
* Fostering collaboration
−
*It’s a reaction to the Act we have to follow
+
* Advancing UX across government
−
*Departments have some flexibility where to post
+
* Meeting link: https://forms-formulaires.alpha.canada.ca/en/id/clw9ksj1i00qmx883suajuhcq
−
*Formats are flexible
 
−
*Have to follow Official Languages Act
 
−
*Public Safety has to make their reports available in a central location
 
−
*Can be .pdf or web only, as long as it’s accessible
 
−
*Public Safety is working to post their report early as an example for other departments to follow
 
−
*Timeline: the questionnaire and .pdf version are due May 31, but as far as publishing on website, there are not definite deadlines
 
−
*For more information: https://www.publicsafety.gc.ca/cnt/cntrng-crm/frcd-lbr-cndn-spply-chns/index-en.aspx
 
−
'''Questions:'''
 
  
−
Q: Are you going to come back when Public Safety Publishes its reports?
+
'''AI Trust study - draft design'''
  
−
A: Yes, I can come back.
+
* In 2022, DTO conducted a trust study on design elements such as FIP and sign-in
 +
* Now, we will look at trust in regards to AI on Canada.ca
 +
* From the 2022 study, we learned that how the flag is depicted is very important
 +
* Now for the AI study, we’re looking at the H1
 +
* We’re studying the importance of location of breadcrumbs for H1
 +
* AI image citations, want to create guidelines for transparency for using AI, example: should user be notified that an image is created by AI
 +
* Government doesn’t always knows how images are created - for instance if we use shutterstock or other image licensing sites
 +
* Testing which images do people trust most on Canada.ca
 +
** Image from live site with no caption
 +
** AI generated with notice
 +
* Text testing which is trusted more:
 +
** Text with no notice
 +
** Notice that AI was reviewed by human
 +
* Testing chatbot, do people trust:
 +
** Chatbot button
 +
** Overlay at bottom of page
 +
* AI applications working on Canada.ca (not from government) such as Google AI overview, Bing copilot AI, knowing which is most trusted helps us move faster if necessary
 +
* Next steps:
 +
** Fine tuning
 +
** Pilot testing/qualitative testing with video comments
 +
** Sending invitation form to Principal Publisher and approvals
 +
** Launch
  
−
Q: Do we need to alert other teams in our department about these reports?
+
'''Questions:'''
  
−
A: Other teams should be aware of this.
+
'''Q:''' People are worried that teams will rely on the chatbots, however if we’re worried about that, it means that we’re not doing their job
  
−
'''Mary Beth Baker PCO, Stephane LeBlanc - VAC - BROKEN LINKS'''
+
Answer:
−
*At VAC, we moved from Cold Fusion to Drupal
 
−
*Resulted in almost 7,000 broken links by day 2
 
−
*To fix the problem was a joint effort with IT and the Web team
 
−
*This brought up the issue - what is the “industry standard” for amount of broken links
 
−
*Some say 5%
 
−
*We put in a customized page to alert users that we were making some changes, with navigation help, but internally this page wasn’t popular
 
−
'''Q''': There’s an alert at the top of the page, is that how you told people to contact you? And maintenance implies a short time period.
 
  
−
'''A:''' Yes, that’s what we used. At the beginning we got some contact, but it has greatly gone down over time.
+
The chatbots will use Canada.ca citations, so there will be no way around posting good content for web teams.  
  
−
'''Comments from chat - managing broken links:'''
+
'''Q:''' What will the labeling guidelines for images be?
−
*We used to have Link Tiger for broken links, a very small investment for a solid tool. But now with Drupal we have a built-in broken link report.
 
  
−
*The best part of SiteImprove is that you can send out automatic reports for both broken links and accessibility issues, this push style reporting is super useful as a reminder
+
'''A:''' This will be more of a role for Treasury Board policy to take care of.
  
−
*At GAC, we monitor broken link CLICKS, not the actual broken links. If the broken links are not getting clicked, it's not really a problem. We try to address links that are clicked more than 10 times a week over many weeks. At 10 clicks/week we end up having to review / fix just a handful of links each week which is manageable by our busy teams
 
−
Also note that broken links can also be caused when redirects are left in place longer than they should be...redirects should only be used temporarily, until user traffic is going straight to the new URL. If Principal Publisher implemented your redirects in MWS, please let us know when you want them removed. http://requestform.portal.gc.ca/tickets.html
 
 
===Roundtable===
 
===Roundtable===
−
'''WAGE'''
+
'''ESDC'''
−
*GBA+ Awareness week is next week we're hosting an event with CSPS on May 6. Check it out here: https://www.canada.ca/en/women-gender-equality/gender-based-analysis-plus/gba-plus-awareness-week.html
+
 
 +
* We are currently building a Seniors single point of access site, and looking for any senior related content not currently promoted from https://www.canada.ca/en/employment-social-development/campaigns/seniors.html as that content has been considered already.
 +
* Reach out to:[mailto:Lalithajoshua@servicecanada.gc.ca lalithajoshua@servicecanada.gc.ca] by 19th of June or earlier.

Latest revision as of 15:50, 17 June 2024

Back to GC Web Priorities Meetings - Réunions des Priorités Web du GC

Meeting information

Agenda

1. Updates

2. Roundtable

Notes and action item

Updates

New UX Community of practice

AI Trust study - draft design

  • In 2022, DTO conducted a trust study on design elements such as FIP and sign-in
  • Now, we will look at trust in regards to AI on Canada.ca
  • From the 2022 study, we learned that how the flag is depicted is very important
  • Now for the AI study, we’re looking at the H1
  • We’re studying the importance of location of breadcrumbs for H1
  • AI image citations, want to create guidelines for transparency for using AI, example: should user be notified that an image is created by AI
  • Government doesn’t always knows how images are created - for instance if we use shutterstock or other image licensing sites
  • Testing which images do people trust most on Canada.ca
    • Image from live site with no caption
    • AI generated with notice
  • Text testing which is trusted more:
    • Text with no notice
    • Notice that AI was reviewed by human
  • Testing chatbot, do people trust:
    • Chatbot button
    • Overlay at bottom of page
  • AI applications working on Canada.ca (not from government) such as Google AI overview, Bing copilot AI, knowing which is most trusted helps us move faster if necessary
  • Next steps:
    • Fine tuning
    • Pilot testing/qualitative testing with video comments
    • Sending invitation form to Principal Publisher and approvals
    • Launch

Questions:

Q: People are worried that teams will rely on the chatbots, however if we’re worried about that, it means that we’re not doing their job

Answer:

The chatbots will use Canada.ca citations, so there will be no way around posting good content for web teams.

Q: What will the labeling guidelines for images be?

A: This will be more of a role for Treasury Board policy to take care of.

Roundtable

ESDC

Retrieved from "https://wiki.gccollab.ca/index.php?title=June_5,_2024_-_Updates,_priorities_of_the_week&oldid=122102"