Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

📐 Separate "TEAM LEAD" and "INDIVIDUAL CONTRIBUTOR" from table of classifications #17

Open
25 tasks
Jerryescandon opened this issue Apr 4, 2023 · 3 comments

Comments

@Jerryescandon
Copy link

⚙️ Summary

Should we separate "TEAM LEAD" and "INDIVIDUAL CONTRIBUTOR" as two different classifications on the classification table?

image

Impact

This table is used in a lot of places to calculate different content throughout the platform.

Visit the Figma file

[PURPOSE AND DESCRIPTION]

💾 Files and resources

  • [FILE]

✅ Design checklist

  • Component library elements have been used where appropriate
  • Component library elements have been updated where changes where required
  • Newly added interface elements have been added to the component library for reuse
  • Newly added interface elements have been added to Github Discussions using the component issue template
  • The interface is responsive or provides responsive context
  • The interface provides both light and dark mode designs
  • Complex interactions have been prototypes in a way that showcases every step in the flow
  • Empty/null states have been accounted for
  • A content spreadsheet has been created and copywriting has been assigned
  • The design has been reviewed by at least one other team member
  • The design has been presented to the design team
  • The design has gone through at least one round of usability testing
  • The design has gone through at least one round of accessibility testing
  • The design has been approved by stakeholders

✅ Accessibility checklist

Please refer to the comprehensive list for more details.

  • Links have meaningful label text
  • Navigation matches previously established patterns
  • Headings are identified using annotations and follow a logical hierarchy
  • Layout is linear and consistent with established patterns
  • New interactive elements have unique focus states that match the established pattern
  • Tab order has been identified using annotations
  • Relevant images and icons have appropriate alt text
  • Use of color meets AA WCAG contrast requirements
  • States or information are not identified by color alone
  • New interactive elements have appropriately sized touch targets on touch devices

📸 Screenshot

[SCREENSHOT]

✅ Requirements

  • [REQUIREMENT]

🛠️ [REQUIREMENT NAME]

[REQUIREMENT DESCRIPTION]

[REQUIREMENT SCREENSHOT]

🙀 Optional requirements

[REQUIREMENT NAME]

[REQUIREMENT DESCRIPTION]

[REQUIREMENT SCREENSHOT]

🤔 Outstanding concerns

  • [CONCERN]

📝 Related issues

Please link all design and development sub-tasks related to this issue here for tracking purposes.

  • [ISSUE #]
@mnigh
Copy link

mnigh commented Aug 14, 2023

⚙️ Summary

Should we separate "TEAM LEAD" and "INDIVIDUAL CONTRIBUTOR" as two different classifications on the classification table?

@Jerryescandon is this issue still relevant or can this issue be closed?

@mnigh
Copy link

mnigh commented Oct 5, 2023

⚙️ Summary

Should we separate "TEAM LEAD" and "INDIVIDUAL CONTRIBUTOR" as two different classifications on the classification table?

@Jerryescandon is this issue still relevant or can this issue be closed?

@Jerryescandon any updates on this issue?

@Jerryescandon
Copy link
Author

🤷 ?

@gobyrne is this something we still considering? can we move this out of dev backlog into the design one?

@mnigh mnigh transferred this issue from GCTC-NTGC/gc-digital-talent Nov 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants