Git Basics: <Accessibility of screenshots> about curriculum HOT 4 OPEN

Thank you for opening the issue @MatthewWestDev!
Accessibility is definitely something we're steadily working on improving throughout the site and curriculum.

@thatblindgeye I think we'd greatly value your thoughts here

from curriculum.

We definitely do rely too heavily on screenshots to convey important information. Where providing a screenshot is helpful we should also provide a text alternative (beyond just alt text, because that will only be visible for users navigating via AT such as screen readers or only when the image fails to load). Otherwise, yes we should replace screenshots with text. Relying on screenshots so much also just makes it even more upkeep if even the slightest thing changes on the UI vs the screenshot ("Well now there's another field between these two fields from the screenshot")

I'll open this as help wanted for now, but may try to get around to it myself if I can/nobody else asks to do it.

from curriculum.

Looks like there is a lot of work to do here. I'd like to take it, but don't know if I will have time in the coming days.

from curriculum.

@kol3x I'll assign you for now. If you end up not having the time no worries, just let us know. And if you need any help don't hesitate to reach out.

Just to clarify, the solution for this lesson could be one or both of:

• Replacing screenshots as needed with text based instructions
• Adding/tweaking additional text based context around the screenshots, e.g. instead of "Click the button shown in the following screenshot," we'd say "Click [description or text content of the button, possibly with additional context of where it is on the page], as shown in the following screenshot." or something.

from curriculum.