| Line 6: |
Line 6: |
| | 2. Roundtable | | 2. Roundtable |
| | =Notes and action item= | | =Notes and action item= |
| | + | |
| | + | === DTO update === |
| | + | |
| | + | * We are updating the new main page title style (H1). It has been rolled out in AEM and is available in the latest release of GCWeb. The main heading styles will be automatically updated when you upgrade to the latest version. It should be available via CDTS, Dripal WXT and the GC design system by mid-March |
| | + | |
| | + | The typography specs are: |
| | + | |
| | + | * English: [[/design.canada.ca/styles/typography.html|https://design.canada.ca/styles/typography.html]] |
| | + | * French: [[/conception.canada.ca/styles/typographie.html|https://conception.canada.ca/styles/typographie.html]] |
| | + | |
| | + | * The social media channels pattern in GCWeb has been updated to reflect the new Twitter/X logo, but there’s no set deadline to make the changes. The change has been automatically in AEM. |
| | + | |
| | + | * Reminder our email has changed, our old forwarding email is not active anymore |
| | + | |
| | + | New email: [[Mailto:Cds.dto-btn.snc@servicecanada.gc.ca|cds.dto-btn.snc@servicecanada.gc.ca]] |
| | + | |
| | ===Roundtable=== | | ===Roundtable=== |
| − | '''Health Canada'''
| + | |
| − | *GC Health Theme Partners Community presentations and meeting notes from November 28 are now available on the GCwiki page under the meeting tab:
| + | |
| − | **[https://docs.google.com/presentation/d/1yxvAe-j9hzWzmSx-YjKDlV8JcKqSOTKv/edit?usp=sharing&ouid=105404872280407473538&rtpof=true&sd=true GC Health Theme Partners Community presentations]
| + | |
| − | **[https://docs.google.com/document/d/1LFYlbXhgNTDCVANPgIBp4i0GmXGYHPniyoHaaj-fJh8/edit?usp=sharing GC Health Theme Partners Community meeting notes]
| |
| − | **[[:en:Health_Theme_Partners_Community|GC Health Theme Partners Community GCwiki page]]
| |
| − | *Next meeting is scheduled for February 20. Let us know if you would like to present any items your team is working on or have any items you would like to discuss [https://forms.office.com/pages/responsepage.aspx?id=FZD9Qk3eI0KjaLrqyrSJJwA0Wfrdh7xBpdggPYcIhSVUMzlQN0EwQUtPTFY1WVNHSjNLMkNDOVEwNS4u by filling out our feedback form]. #GCHealthThemePartners
| |
| − | *A new Healthy Canadians podcast episode is now live. This week’s episode is on Undetectable = Untransmissible (U=U), the Behind the Science segment on the HIV self-testing kit.
| |
| − | **[https://www.canada.ca/en/services/health/stay-connected/healthy-canadians-podcast.html Healthy Canadians Podcast.]
| |
| − | *[https://catalogue.csps-efpc.gc.ca/product?catalog=TRN1-E19&cm_locale=en Register for upcoming Social Media Monitoring in the GC (CSPS)] Jan.16 from 1:30 pm to 3 pm ET.
| |
| − | **Details can be found in the Slack channel: [https://gc-web-comms.slack.com/archives/C01CLT1TJSX/p1701882559209409 #events-training-formation-apprentissage channel GC WP Slack]
| |
| | '''Principal Publisher''' | | '''Principal Publisher''' |
| − | *Mail went out from us about the GCWeb release on November 23rd, if you are a GC Web user and haven't received the mail, contact: [Mailto:maria.behan@servicecanada.gc.ca maria.behan@servicecanada.gc.ca].
| |
| − | '''Department of National Defense'''
| |
| − | *Usability updates to Military pay rates are live
| |
| − | '''Agriculture and Agri-food Canada'''
| |
| − | *They were using MS Dynamics but having serious technical issues since the spring. May be looking for a new solution if Microsoft can't fix it.
| |
| − | '''Canadian Food Inspection Agency'''
| |
| − | *They have started using GC Notify
| |
| − | '''Parks Canada'''
| |
| − | *Parks Canada 2024 reservation launch dates were published this week: [https://parks.canada.ca/voyage-travel/reserve Parks Canada reservations - Plan your visit]
| |
| − | '''Canadian Heritage'''
| |
| − | *Statement about Online New Act: [https://www.canada.ca/en/canadian-heritage/news/2023/11/statement-by-minister-st-onge-on-next-steps-for-the-online-news-act.html Statement by Minister St-Onge on next steps for the Online News Act - Canada.ca]
| |
| − | '''Updates from CBSA:'''
| |
| | | | |
| − | CBSA published its Year in Review 2023 news release and web stats (with infographics).
| + | * Release went through this week on changes to Institutional Landing Page Template that DTO discussed |
| − | *[https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcbsa-asfc.gc.ca%2Ftransparency-transparence%2Fyir-aer-fra.html&data=05%7C01%7CChelsey.Donohue%40tbs-sct.gc.ca%7Ca8c5e322971b4982dd4608dbf68e980e%7C6397df10459540479c4f03311282152b%7C0%7C0%7C638374864649286945%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=smFKcut8ej4RjF35VwAsOEFpPuFyv1YyfQ2%2Bq8G5ung%3D&reserved=0 Bilan de l'année 2023 : les réalisations en chiffres (cbsa-asfc.gc.ca)] | + | ** Update to the main page title (h1) style |
| − | *[https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcbsa-asfc.gc.ca%2Ftransparency-transparence%2Fyir-aer-eng.html&data=05%7C01%7CChelsey.Donohue%40tbs-sct.gc.ca%7Ca8c5e322971b4982dd4608dbf68e980e%7C6397df10459540479c4f03311282152b%7C0%7C0%7C638374864649443188%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=p9TFLtJZXup93FwNPcwF184tRXhUpoI2vwIK3GySAxk%3D&reserved=0 2023 Year in review: Accomplishments by the numbers (cbsa-asfc.gc.ca)] | + | ** Update to the bold class for the news feed |
| − | They are also going out with a holiday travel tips news release on approximately December 13.
| + | ** Logo change: Twitter to X |
| | + | |
| | + | '''WAGE''' |
| | | | |
| − | '''DTO Presentation - Canada.ca Style guide updates''' | + | * International Women's Day 2024 theme and toolkit are now live: ([[/women-gender-equality.canada.ca/en/commemorations-celebrations/international-womens-day/2024-theme.html|https://women-gender-equality.canada.ca/en/commemorations-celebrations/international-womens-day/2024-theme.html]]) |
| | | | |
| − | [[:en:images/a/a0/Style_Guide_updates_-_Dec_1_post.pptx|Presentation: Style Guide updates]]
| + | '''Service Canada''' |
| − | *Improved functional image example. We wanted to remove the image of a chart as it’s often better to dynamically create charts and graphs from table data if possible, as opposed to writing a long description for them. We instead chose a flow chart with a solid long description as the example for a functional image.
| |
| − | *Updated decorative image example. We removed the example that was there as it featured a carousel which we generally don’t recommend using. We also felt that a picture of an RCMP officer in the official uniform on an item about the RCMP could actually be argued as being a purposeful image as opposed to decorative. So we added something a bit more generic and also added advice about using the null indicator as alternative text.
| |
| − | *We made a small tweak to the simple table examples. We removed the footer as it was extra data that we didn’t need in there. Though it was coded correctly we felt it was unnecessarily distracting from the message for content providers to use the simplest structure possible for tables.
| |
| − | *We continue to work through requests that have been sent or flagged to us. In our next group of changes we plan to replace the reference to refer to the Canadian Style as it has been archived and replaced by Writing Tips Plus. But first we need to do a review to see if we just need to switch one-for-one or if we need to include additional references. The Plain language working group will resume in January to complete work started earlier this year. And we want to look at enhancing the guidance around images and ensure everything is consistent and in line with current best practices.
| |
| − | *Feel free to reach out to DTO team is you have any suggestions or comments for updates
| |
| − | '''[[:en:images/f/f3/Audit_-_Canada.ca_patterns_and_templates_(open_for_comments)_post.xlsx|DTO Presentation - Audit of templates and patterns]]''' | |
| − | *Currently 72 patterns in the audit
| |
| − | *We checked over to see if templates and patterns were currently being used by departments/agencies
| |
| − | *Checked if the patterns/templates were mandatory
| |
| − | *Discussed as a team and made preliminary recommendations for which ones to retire
| |
| − | *Found 29 possibilities for removal
| |
| − | *Commonalities of ones for removal
| |
| − | **Older, superseded by new ones
| |
| − | **No code, just pictures
| |
| − | **Some were too simple to be helpful
| |
| − | **Some were made for single instance
| |
| − | *Commonality to retain:
| |
| − | **Widely used
| |
| − | **Useful for helping users complete tasks
| |
| − | **Mandatory
| |
| − | Comment: Removing Canda.ca homepage template makes sense, also glad to see carousels go.
| |
| | | | |
| − | Comment: Is there a change management plan for these changes?
| |
| | | | |
| − | Answer: Just because the template is not in the library anymore, doesn’t mean departments have to change any pages that use the template.
| + | Presentation: Using page feedback to improve the Canadian Dental Care Plan |
| | | | |
| − | Question: Any value in keeping items as examples of what not to do, with explanation of why they are not good designs.
| + | Canadian Dental Care Plan case study: Iterative approach |
| | | | |
| − | Answer: Yes, good point, we will definitely consider this.
| + | * December 2023 - Published content on web |
| | + | * We included page feedback tool, for 8 pages of English, and 8 pages of French content |
| | + | * We analyzed feedback to make quick iterative improvements according to comments, this was a game-changer |
| | + | * Many issues identified in first week, period with highest amount of feedback |
| | + | * 4 post launch reports at different time periods |
| | + | * We manually tagged and sorted comments, 800 comments |
| | + | * Summarized top issues, provided recommendations for improvements |
| | + | * Reports were more detailed as time went on |
| | | | |
| − | Question: Some of CDS Design patterns contradict Canda.ca design system. Which one should we use. For example buttons.
| + | * Four big issues: |
| | + | *# Birth date calendar picker was hard to use to determine when to apply |
| | + | *#* So we simplified the way the calendar worked |
| | + | *#* We also gave users the choice of using the tool, or using a text chart to enter their information |
| | + | *# Children’s dental benefit alerts reduced the scent of information for seniors |
| | + | *#* 64 comments in first 24 hours from seniors who were confused if the program was for them, they were thrown of by the information about children |
| | + | *#* We added the text “starting with seniors” which helped and negative feedback decreased right away |
| | + | *# Adjusted family net income terminology confuses single seniors |
| | + | *#* The term is confusing |
| | + | *#* We improved the navigation to make it more clear where users should keep clicking, avoiding specific eligibility criteria on navigation pages |
| | + | *#* We also added expand and collapse to define eligibility criteria |
| | + | *# Policy for eligibility confusing: what if someone has partial dental coverage |
| | + | *#* This became a big issue, even internally the answer was not fully known |
| | + | *#* We grouped the questions from users we got and shared them with policy makers |
| | + | *#* In addition, media raised the issue which raised visibility |
| | | | |
| − | Answer: Good question, this is a change management issue we’re working through. We’re working with our CDS colleagues on this issue, and it’s something we will need to work through in upcoming months.
| + | LESSONS LEARNED |
| | | | |
| − | Question: Have these elements been assessed for WCAG AA?
| + | * Guidance in WET could be updated to help people with date picker calendars |
| | + | * It would help GOC web community to have discussion around when is best time to introduce eligibility criteria |
| | + | * Shared top policy questions with policy partners from the two departments |
| | + | * Worked with call centers to determine if answers were coming from other actors |
| | + | * That users questions are extremely valuable, to alert policy makers to problems with programs/policies |
| | + | * Brings up the interesting idea of crowd-sourcing for ideas |
| | + | * Reduce risk by audience testing, read and analyze feedback, share with partners |
| | | | |
| − | Answer: We did not look at accessibility for this audit. But through development , they have all been looked at for accessibility issues, even though some may be out of date.
| + | Questions: |
| | | | |
| − | '''[[:en:images/7/75/Findability_update_-2_-_GCWP_-_December_2023_post.pptx|DTO - Findability Presentation]]'''
| + | Q:Where is the best place to post about eligibility requirements? |
| − | *The web is changing, has implications for GC web findability
| |
| − | *New technology such as bots, AI, controversy over how this tech is “trained”
| |
| − | *Knowledge graphs and large language models are ways to give users of your website good answers
| |
| − | *Big shift is semantic search instead of lexical search, this is more sophisticated
| |
| − | *This shift lets computers infer new knowledge, can be very powerful
| |
| − | *Big impact on how Google’s SEO operates
| |
| − | *Semantic markup rather than use of keywords
| |
| − | *Google more orientated towards its paying customers, more product oriented
| |
| − | *GOC needs to develop a new strategy for schema markup
| |
| − | *Have created a slack channel to collectively work on the strategy [https://app.slack.com/client/T0105JB7T33/C069C1KJBL1 schema-markup-balisage - GC web comms - Slack]
| |
| − | '''Questions/comments'''
| |
| | | | |
| − | Question: We seem to have a training gap to work on the schema strategy?
| + | A: The main point is that the help has to be interactive. This is what we’ve learned from testing. |
| | | | |
| − | Answer:
| + | Q: For CRA , we have to go all the way up the approval chain. Was your approval process for this project fairly agile? |
| | | | |
| − | Not many formal training/resources at this time. The markup uses json ld, which is not difficult to use. People can do a lot of self learning. If we can provide sample markup, it would be a good way to go. Sharing examples on GitHub.
| + | A: Setting up the approval process, and a warning before it launched that there would be the need for approvals and iterative changes right away. We were clear with our senior leaders what the iterative approach meant, that there would be a need for quick approvals. We were able to get buy-in from senior management which was key. |
| | | | |
| − | Comment: Finding tax/CRA content is difficult in searches. There are competing products from business etc. We need to make sure that the new schema is not used to cover up bad content.
| + | LISA FAST - AB testing with IRCC |
| | | | |
| − | Comment: HC worked with Google to use FAQ schema to enhance search results for COVID-19 content.
| + | * Looking to understand the use of the alert band |
| | + | * We did an A/B test with what was on the website, and other kind of warnings |
| | + | * We discovered that on mobile an icon was missing |
| | + | * The warning worked better than the alert band, especially in mobile |
| | + | * So we moved on to test 2 |
| | + | * The band as designed on the live site is doing a good job |
| | + | * However, we consistently saw differences between the desktop and mobile, which isn’t supposed to happen |
| | + | * Test 3: Alert band vs warning alert vs contrast band |
| | + | ** Contrast band had more conversions |
| | + | ** Unfortunately it distracted from other content on the page which was more important |
| | | | |
| − | Are you sharing this information with OCIO?
| + | Takeaways: |
| | | | |
| − | Answer: OCIO has not been involved in web issues as much recently.
| + | * Contrast design is too noticeable |
| | + | * Standard warning alert should be placed before important content |
| | + | * Warnings/alerts are more distracting on mobile…so if your page is really popular on mobile, be careful you don’t overuse them |
| | + | * Warnings imply that something has changed, something has just happened |