When we introduce accessibility and lighthouse, our trainees have only encountered static pages which don't change.
When we introduce using the DOM to modify the page (https://curriculum.codeyourfuture.io/itp/data-groups/sprints/3/) we should add a note that this may change the accessibility of pages, and introduce using snapshot mode to check this.
I'm imagining a short prep block which introduces this as a concept, and then adding a backlog item to give people first-hand experience of this. Let's put together a tiny page where each time you press a button it adds something to the page, but does so in a way that isn't accessible (e.g. each time it uses a different foreground colour, but the second one doesn't have enough contrast).
When we introduce accessibility and lighthouse, our trainees have only encountered static pages which don't change.
When we introduce using the DOM to modify the page (https://curriculum.codeyourfuture.io/itp/data-groups/sprints/3/) we should add a note that this may change the accessibility of pages, and introduce using snapshot mode to check this.
I'm imagining a short prep block which introduces this as a concept, and then adding a backlog item to give people first-hand experience of this. Let's put together a tiny page where each time you press a button it adds something to the page, but does so in a way that isn't accessible (e.g. each time it uses a different foreground colour, but the second one doesn't have enough contrast).