Myths:
1. Automated testing is all you need
2. A framework will guarantee accessibility
3. Designers and developers know about accessibility
4. Specifying “accessibility” as a project requirement means it’s covered
5. Great accessibility just means fixing the issues you find

For example:
Header and footer information in Word/Excel documents is NOT exposed to assistive tech, so repeat it on the first page or cell.

2/2

I can relate!

Make sure you (and team) take some time to recover from the emotional turmoil!

I've been left extremely drained.

Worse obviously for those made redundant, especially those with visa requirements. But don't forget that it's traumatic for everyone including you.

Add to that, you're likely overlooking
- people with disabilities
- people in rural areas
- people who have caring commitments

Same on mine!

Might be worth contacting the @rnib.bsky.social to see if they can suggest improvements available to that system

When I was a teenager in the 90s my brother (also my lift to the gym) got me after 2 minutes once saying "They've cancelled Neighbours coz of the bloody tennis. I can't run watching that! We're leaving"

Another great article!
I'll be referencing this in CMS content editor training I think

p.s. If money is your only motivation for getting into frontend or tech in general, please walk on. The industry won't want to work with you (or at least, I won't!)