722
edits
Changes
June 19, 2024 - Updates, priorities of the week (view source)
Revision as of 16:06, 19 July 2024
, Yesterday at 16:06Created page with "FR: 12 juin 2024 - Mises à jour, les priorités de la semaine Back to GC Web Priorities Meetings - Réunions des Priorités Web du GC ==Meeting information== ===Agend..."
[[FR: 12 juin 2024 - Mises à jour, les priorités de la semaine]]
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===
'''Principal Publisher'''
* Successful implementation of new search solutions
* Departments won’t see a difference in functionality or appearance but results will hopefully improve
* If you have any issues, send us a ticket and we will look into it: [http://requestform.portal.gc.ca/tickets.html Request form for Principal publisher (portal.gc.ca)]
'''CDS - Abdul Aminu - GC Design System Roadmap'''
* [[/docs.google.com/document/d/e/2PACX-1vRol9Xx2o9y9gShFCG-vwaNRpYvcxCYMfglSk6FJrQWH3dXYOlxX 1n6cTv57wxWdvLFxcdIXPARkHE/pub|Roadmap document]]
* Q1:
** Focused on product growth, research and engagement for Q1
** Have begun testing on Canada.ca managed web service (AEM) and Drupal with encouraging results so far
** Researching pain points, how can we make this easier to use
* For Q2
** We’ve received feedback that templates are really important so we’re making templates in Figma library as well as in code
** Working with DTO to resolve any conflicting styles with Canada.ca mandatory elements
* Q3:
** Improving integration with design.canada.ca, working with DTO team
* Q4:
** Aiming for Beta or full release
** Standardized process to integrate with AEM and Drupal
** 5 completed research studies throughout the year
* Links for Figma:
** English: https://www.figma.com/design/mh2maMG2NBtk41k1O1UGHV/GC-Design-System?node-id=4-1006&t=gYX1714XJGqS9g7A-0
** French: https://www.figma.com/design/o4SguSZdar2CCFzSkWNrmB/Syst%C3%A8me-de-design-GC?node-id=226-31997&t=48XQgoluEM1pXFFW-0
'''FAQs and accessibility - Chad F - CRA'''
* NIVIDIA and JAWS are the most used accessibility screen readers
* The way they both read aloud FAQs to readers is an expletive
* This is another reason to not use FAQs
* More info about avoiding FAQs: https://blog.canada.ca/2020/05/25/avoiding-faqs.html
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===
'''Principal Publisher'''
* Successful implementation of new search solutions
* Departments won’t see a difference in functionality or appearance but results will hopefully improve
* If you have any issues, send us a ticket and we will look into it: [http://requestform.portal.gc.ca/tickets.html Request form for Principal publisher (portal.gc.ca)]
'''CDS - Abdul Aminu - GC Design System Roadmap'''
* [[/docs.google.com/document/d/e/2PACX-1vRol9Xx2o9y9gShFCG-vwaNRpYvcxCYMfglSk6FJrQWH3dXYOlxX 1n6cTv57wxWdvLFxcdIXPARkHE/pub|Roadmap document]]
* Q1:
** Focused on product growth, research and engagement for Q1
** Have begun testing on Canada.ca managed web service (AEM) and Drupal with encouraging results so far
** Researching pain points, how can we make this easier to use
* For Q2
** We’ve received feedback that templates are really important so we’re making templates in Figma library as well as in code
** Working with DTO to resolve any conflicting styles with Canada.ca mandatory elements
* Q3:
** Improving integration with design.canada.ca, working with DTO team
* Q4:
** Aiming for Beta or full release
** Standardized process to integrate with AEM and Drupal
** 5 completed research studies throughout the year
* Links for Figma:
** English: https://www.figma.com/design/mh2maMG2NBtk41k1O1UGHV/GC-Design-System?node-id=4-1006&t=gYX1714XJGqS9g7A-0
** French: https://www.figma.com/design/o4SguSZdar2CCFzSkWNrmB/Syst%C3%A8me-de-design-GC?node-id=226-31997&t=48XQgoluEM1pXFFW-0
'''FAQs and accessibility - Chad F - CRA'''
* NIVIDIA and JAWS are the most used accessibility screen readers
* The way they both read aloud FAQs to readers is an expletive
* This is another reason to not use FAQs
* More info about avoiding FAQs: https://blog.canada.ca/2020/05/25/avoiding-faqs.html