🧑🏾‍💻 prep

🔖
  1. Enroll as a Trainee
  2. Record a Goose
  3. backlog

Enroll as a Trainee 🔗

Learning Objectives

https://application-process.codeyourfuture.io/

Learning Objectives

Why are we doing this?

Enroll as a trainee to:

  • claim course expenses to support your studies
  • access unlimited Udemy for Business courses
  • access GitHub Student Developer Pack
  • access any further CYF courses

1. Complete your step submission

This is the same as in ITD. Everyone should do this, even if you are not eligible to enrol as a Trainee. You will do this every module:

  1. Go to https://programming.codeyourfuture.io/onboarding/success/
  2. Check off the learning objectives
  3. Make an issue on your Coursework Planner: https://github.com/YOURGITHUB/My-Coursework-Planner/issues
  4. Put links to all the evidence asked for on the module success page
  5. Submit your step on the CYF Course Platform (sometimes called “the dashboard” by volunteers)

2. For this onboarding module only:

  1. Complete this enrollment form.
  2. If you hit a blocker write to pastoral@codeyourfuture.io if it’s private, or post on Slack if it’s not private

Maximum time in hours

.5

How to get help

If you hit a blocker and it’s something private, write to pastoral@codeyourfuture.io Otherwise, post on Slack. Encourage and support each other to complete onboarding!

How to review

You will receive your enrolment by email.

  • 🎯 Topic Requirements
  • 🏕 Priority Mandatory
  • 🐇 Size Small
  • 📅 Sprint 3

Record a Goose 🔗

Learning Objectives

Record a goose sighting

What to do

Go to the ‘Record a goose sighting’ exercise

This is a fictional service, to help you record any sightings of geese (geese are awesome). It’s using the GOV.UK Design system, which are WCAG 2.1 AA compliant, and benefits from hundreds of hours of work and testing. However, even if you’re using a Design System, stuff can still go wrong…

There are places where the Design System is misused, misimplemented or misunderstood. This has caused accessibility issues, which range across code, design and content - because accessibility issues can be introduced by all of these disciplines. As such, anyone is welcome to have a go and use this as an exercise!

How to use this

The task is to find as many of the accessibility issues in this site as you can in ~20 minutes.

There is a worksheet, and there is also a list of answers - but give it the full 20 minutes before you look at the answers first, if you’re working through this alone!

If you are running this as a group workshop, there is an answerless ‘Record a goose sighting’ exercise, that you can use with attendees. This prevents you from finding answers before you’re ready to go through them as a group!

What testing tools to use

I would recommend working through the site in the following order:

  • Can you access everything by pressing the tab key?
  • Does WAVE show any errors, or highlight any issues with the HTML structure?
  • Does the colour contrast tab on WAVE throw up any errors?
  • Install and run Accessibility Insights. What advice does it give you?

Government Digital Services have recently published how to conduct a basic accessibility audit, which is worth a look at too.

Testing like this is a good way to identify basic accessibility issues. It would not replace an audit against WCAG 2.1 to level AA, and its ~50 criteria. Why still do it? These are tests that are quick to run, and it’s easier to fix accessibility issues at the start, rather than the end.

Backlog

Learning Objectives

In software development, we break down complex projects into smaller, manageable parts, which we work on for a week or two. These periods are called “sprints.”

A sprint backlog is like a to-do list. It lists what the team has decided to work on this sprint. It’s chosen from a larger list, usually called the “product backlog,” which holds the entire project to-do list.

In this course, the backlog is a set of work designed to build understanding beyond the concepts introduced in the course prep. For your course, we have prepared a backlog of mandatory work for each sprint. You will copy these tasks into your own backlog. You can also add any other tickets you want to work on to your backlog, and schedule all of the tasks according to your own goals and capacity. Use your planning board to do this.

You will find the backlog in the Backlog view on every sprint.

Copy the tickets you are working on to your own backlog. Organise your tickets on your board and move them to the right column as you work through them. Here’s a flowchart showing the stages a ticket goes through:

flowchart LR Backlog --> Ready Ready --> in_progress in_progress[In Progress] --> in_review in_review[In Review] --> Done

Backlog (30 minutes)

  1. Find the sprint backlog
  2. Copy your tickets to your own backlog
  3. Organise your tickets on your board