869
edits
Changes
Jump to navigation
Jump to search
Line 4:
Line 4: − + − + − Wednesday, August 23, 2023 – 2:00 PM - 2:30 PM+ − + − Microsoft Teams meeting+ − + − [https://teams.microsoft.com/l/meetup-join/19%3ameeting_YzYyNzg3YjAtZGYzZC00ZjcxLTliOWMtZWEzN2JjMmM5NzM3%40thread.v2/0?context=%7b%22Tid%22%3a%226397df10-4595-4047-9c4f-03311282152b%22%2c%22Oid%22%3a%2247775425-ee56-4f18-b71f-5d4197f032f2%22%7d Join the meeting]+ − + − Join by phone+ − +1 343-803-0870+ − + − Phone Conference ID: 208 840 448#+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + − ===Agenda===+ − 1. Updates − 2. Roundtable+ + + + + + + + + + + + + + + + + + + + + +
August 23, 2023 - Updates, priorities of the week (view source)
Revision as of 14:33, 24 August 2023
, 14:33, 24 August 2023no edit summary
==Meeting information==
==Meeting information==
===Invitation===
=== Agenda ===
1. Updates
2. Roundtable
== Notes and action items ==
=== Updates ===
=== DTO ===
DTO is short staffed until labor day, we apologize in advance if you get answers back slower than usual.
==== Findability testing ====
We are working on baseline findability testing on top tasks. About how people get our top tasks through IA. More updates in the fall on findability will come once we have the results to share.
Business theme pilot testing results will also be shared in the fall.
==== Sweet class action update ====
The head of communication email went out to 28 organizations last Thursday. We also sent it to web contacts we have from each organization. If you received the email for your department, could you please acknowledge you got it. It would be great to alleviate our legal services department.
Please put up an alert only on related GCKey key services (ones affected in 2020), legal units will be able to help you to identify them if needed. Please do not put it on or near services that were not affected in 2020. We want to avoid unnecessary worry for users.
You can change the capitalization, bolding, underlining in the alert.
The date to take down the alert is November 27th at this point but we will follow up in November to let you know when to take it down.
=== Style guide changes ===
Style Guide Presentation[1]
We are working through style guide changes that have been requested throughout the years.
We’re trying to make changes in batches and will advise the community of any changes.
Next updates will be plain language. We have a few backlogs. If you have any suggestions or questions please reach out to DTO mailbox.
==== Discussions ====
The use of Doctor (Dr.) or Ph.D. would be worth adding as an example. It is confusing whether Doctor applies to only medical professionals or someone who has a Ph.D. Having the discussion about the context on when to use it would be useful.
CRA : Gender neutral and inclusivity is also a discussion to consider. At CRA, at the beginning of COVID, we had to provide a lot of examples taking into consideration gender neutral so we have a well documented space around it. Making sure to take into account non-binary, to not use typical names (avoid targeting specific communities), generational names, or to not pair people from the same heritage, etc. In French, it’s also a challenge.
Suggestion from Jade Bourdages: maybe it has already been discussed, but would it be okay to mention which pronouns has the person right away in the text ? like : John (that refers as a he/him) ...... He did XYZ. So maybe we can address the pronoun directly at the beginning of the text.
* Comment : I think that's a good idea, but in some instances involving couples or polycules you just have to use the name of the person to whom you are referring rather than using a pronoun to avoid confusion. Shared resources : CDS sites this article in this Pride week blog post: <nowiki>https://uxcontent.com/the-international-guide-to-gender-inclusive-writing/#elementor-toc__heading-anchor-2</nowiki> Original digital.canada.ca source: <nowiki>https://digital.canada.ca/2023/07/04/creating-inclusive-spaces-for-gc-collaboration-an-interview-with-jose-jimenez/</nowiki> Other topics to consider : Use of tables in web content Consistent guidance on how to capitalize and punctuate degree initials
== Roundtable ==
'''Public Safety Canada'''
Wildfires - Added BC RFA news release, working with emergency comms to optimize content, Note with the current fire activity in NWT and BC, we have seen a resurgence of traffic to the Wildfire page which had been in a slowing trend previously.
Firearms buyback - Working with Principal Publisher to figure out the technical aspect of setting up a Canada.ca sub-domain for the compensation portal and the different environments. We'll be reaching out to DTO once we have a better sense of the sub-domain approach/text to facilitate approvals. Note: the web content elements once published are on Canada.ca in the Managed Web Service (AEM).
'''PCO''' - Toolkit for PS Pride week: <nowiki>https://gcconnex.gc.ca/file/group/40837724/all#122761421</nowiki>
'''PCO and PP''' : This Thursday August 24 in the 13h00 slot, Mary Beth Baker hosts a Learn How to Calculate session with Marianne Couture (Principal Publisher) for calculating campaign conversion metrics. They decided to have an open meeting so anyone can join, ask questions and as a bonus we can see if this sort of session makes sense. Reply in Slack thread if you want to get in on the invite.
'''Updates about twitter (X)''' : We still don't have the X new logo ready. Stick with what you have. We will do something in the interim if we don’t receive updates.
If you are using Font awesome on AEM version 5.14 it will have the bird. Version 6 you probably need to add manually the X somewhere.
<span name="_msocom_1"></span>
Insert link to presentation here
