508 & Accessibility Questions: Tabbing, Alt Text on unnecessary images, alt text on buttons and quiz answers.
Forgive me if these are answered elsewhere. I've been searching and haven't found quite what I'm looking for.
1. When viewing a course, you can use your Tab button to jump around to different buttons. In a plain jane browser, does this tabbing ONLY pick up things the user can interact with, OR does it approximate at all what a screen reader might pick up?
2. When adding alt text to items on slides, am I correct in saying we should only add alt text to necessary images/items and not purely decorative items? For example, many of our slides have images synced to the narration to make the slide more visually interesting but you don't NEED to see the images to learn the lesson. Since they are flying in and out, I dont see how a screen reader would be able to pick them up anyway. So, could we add an invisible rectangle on the slide with alt text saying something like "This slide has illustrative images synced to the narration." Just so they know what's up? And then focus on adding instructive alt text to things like buttons, visual items that are necessary for the understanding of the lesson, interactive elements, and the like?
3. On buttons, in the Alt Text, do we need to say "Button: Continue" or is the default text that says "Continue" sufficient? Same question, on quiz questions and the multiple choice answers, do we need to say like "Choice A: blah blah", "Choice B: blah blah", or is the auto-created alt text sufficient?
THANK YOU all in advance for your ideas! :)
(In case you're thinking "Why doesn't she have a list of requirements to follow?", our company creates stock training content that other companies can license, and in the last 8 years, we've had maybe 3 or 4 requests for 508 compliant material, so it's never been a priority. In those cases, we created audio-only versions of courses, and they took our quiz questions and built their own quizzes directly inside the LMS. BUT we're getting more questions about it now, and I'd like to try to make some of our content more accessible whenever possible.)