Merge branch 'main' into update-featured-post-and-resource

* main:
  Add Eriol to Spotlight (#1240)
  Showcase The Bootcamper's Guide to Web Accessibility (#1241)

src/_data/homepage.json

@@ -1,12 +1,12 @@
 {
 	"featuredResources": [
 		{
-			"title": "Accessibility for Everyone",
-			"author": "Laura Kalbag",
-			"description": "Laura gives an excellent primer on why accessibility matters, provides context for laws and guidelines, and gives insight on how to integrate accessible de#to your process.",
-			"image": "accessibility-for-everyone.jpg",
-			"alt": "Two stacked copies of the book, Accessibility for Everyone.",
-			"cta": "Learn more about Accessibility for Everyone"
+			"title": "The Bootcamper's Guide to Web Accessibility",
+			"author": "Lindsey Kopacz",
+			"description": "This book is geared towards bootcamp grads and self-guided front end web developers that explains the crucial takeaways of accessibility standards and makes them less intimidating.",
+			"image": "the-bootcampers-guide-to-web-accessibility.jpg",
+			"alt": "The title, The Bootcamper's Guide to Web Accessibility on a maroon background, surrounded by a blue chevron stripe pattern.",
+			"cta": "Learn more about this book"
 		},
 		{
 			"title": "Introduction to Web Accessibility",
@@ -19,11 +19,11 @@
 	],
 	"spotlight": [
 		{
-			"name": "Anna E. Cook",
-			"role": "Senior Product Designer",
-			"description": "Anne is a Senior Product Designer at Recurly. She leads product design efforts within one of their Scrum teams.",
-			"image": "anna-e-cook.jpg",
-			"cta": "Meet Anna"
+			"name": "Eriol Fox",
+			"role": "Human-rights centred designer",
+			"description": "Eriol works part-time as the lead designer at The Open Food Network and spends the other days of the week doing freelance projects, open source design contributions and then working on their PhD research, which is around humanitarian open source software and designer contributions.",
+			"image": "eriol-fox.jpg",
+			"cta": "Meet Eriol"
 		}
 	]
 }

src/_data/spotlight.json

@@ -18,6 +18,12 @@
 			"photo": "/img/spotlight/anna-e-cook.jpg",
 			"biography": "I’m a Senior Product Designer at Recurly. I lead product design efforts within one of our Scrum teams."
 		},
+		{
+			"name": "Eriol Fox",
+			"website": "/spotlight/eriol-fox",
+			"photo": "/img/spotlight/eriol-fox.jpg",
+			"biography": "I work part-time as the lead designer at The Open Food Network and spend the other days of the week doing freelance projects, open source design contributions and then working on my PhD research, which is around humanitarian open source software and designer contributions."
+		},
 		{
 			"name": "Want to nominate someone?",
 			"website": "{{ '/contact/' | url }}",

src/resources/the-bootcampers-guide-to-web-accessibility.md

@@ -0,0 +1,30 @@
+---
+layout: layouts/featured
+title: The Bootcamper's Guide to Web Accessibility
+image: /resources/the-bootcampers-guide-to-web-accessibility.jpg
+category: Featured resource
+featured_resource:
+  - title: Order The Bootcamper's Guide to Web Accessibility eBook
+    url: https://a11y-with-lindsey.ck.page/products/pre-order-the-bootcampers-guide-to-web
+eleventyNavigation:
+  key: The Bootcampers Guide to Web Accessibility
+  parent: Featured resource
+tags:
+  - featuredresource
+---
+
+## Can you describe what the book is about?
+
+Geared toward bootcamp grads and self guided front end web developers, this book explains the crucial takeaways of accessibility standards and makes them less intimidating. We investigate and learn the fixes to the most common accessibility mistakes, demystify ARIA, and learn more about accessible interactive patterns with JavaScript.
+
+## What were your goals in writing the book?
+
+I wanted to help other web developers who shy away from accessibility because they are intimidated or overwhelmed by the specs. I also wanted to fill in an educational gap I saw in bootcamp curriculum and "intro to coding" tutorials.
+
+## What is one important thing someone reading your book will learn?
+
+That it is our responsibility as web professionals to do what we can to help fight ableism, and that coding accessible web sites is only one part of the problem.
+
+## Is there any other info you'd like to share about it, or your experience doing accessibility work?
+
+This books represents what I've learned over the past 7 years as a web accessibility professional and blogger. My goal is to be transparent and break down intimidating "web speak" into relatable terms.

src/spotlight/eriol-fox.md

@@ -0,0 +1,40 @@
+---
+layout: layouts/featured
+title: Eriol Fox
+image: /spotlight/eriol-fox.jpg
+category: Spotlight
+further_reading:
+  - title: erioldoesdesign.com
+    url: https://erioldoesdesign.com/
+  - title: Twitter
+    url: https://twitter.com/EriolDoesDesign
+  - title: GitHub
+    url: https://twitter.com/EriolDoesDesign
+eleventyNavigation:
+  key: Eriol Fox
+  parent: Spotlight
+tags:
+  - spotlight
+---
+
+## What is your day job?
+
+I work part-time as the lead designer at [The Open Food Network](https://openfoodnetwork.net/) and spend the other days of the week doing freelance projects, open source design contributions and then working on my PhD research, which is around humanitarian open source software and designer contributions. Only some of these things I'm paid to do!
+
+I've recently been doing a lot of mentoring of early career designers both in and outside of the open source software space. Most of the people I mentor are designers interested in social good or human rights work generally.
+
+## How has learning about accessibility impacted what you do?
+
+I'm always learning new kinds of ways of being accessible and inclusive but I would say what knowing about accessibility has allowed me to do is to be firmer and stronger in my design work for software. I find myself unable to let inaccessible tech go through the pipeline of development without at the very least signalling and discussing why something isn't accessible.
+
+I think where it becomes trickier is where ways of being accessible and inclusive aren't as general 'well understood' or don't have clear guidance, documentation and resources. I think specifically the ways in which was can make technology and tools accessible to the wider spectrum of neurodiverse folks and folks with mental health needs and challenges.
+
+I've been particularly interested in the last 2 years how we can 're-traumatise' or even start a trauma reaction with the tools we build. This is especially important in technology for civil society, human rights and humanitarian purposes (like I've worked on in the past) but we often forget how seemingly innocuous technology can harm in small and large ways. One of the ways that affect me the most is tools that are not inclusive of non-binary genders and don't consider the complexity of human experiences.
+
+## What's one thing you'd want someone to know about doing accessibility work?
+
+I think I would want everyone to think broadly about accessibility and the myriad of ways that tools can be inaccessible by different kinds of people.
+
+Everyone, regardless of your job function, doing more exercises like empathy maps, user journeying and one of my favourite exercises [<cite>Red team and blue team, by Jonny Rae-Evans</cite>](https://medium.com/we-are-reply/the-role-of-the-red-team-in-innovation-3752b2d4f972) where you can really explore as a team how technology is used and how it could potentially do harm and also, be inaccessible to some.
+
+The last thing I would suggest is knowing about the personal risk that folks put themselves in to do accessibility advocacy. In the best case scenario, you're understood and well received and the work is done, but you have lead the effort and taken the time and energy to advocate. In the worst case scenario, you are faced with several difficult and energy draining conversations that might not succeed (but not for want of trying). This work, even when not successful is so meaningful but often unseen.