Thinking about the shadow interface

[ianvanhoof]

Notes

• I need to change come of the existing classes in the HTML from "visuallyHidden" to "Hidden" this will scope the content being presented at any given time. Thinking about it here this might just require me to change some things in the JS as well. Especially in the TOC/Help menu.
• getting from the main heading to the content area is a nightmare. It is forcing me to hit the help menus, and toc menu each time. This makes it really important for me to get those hidden in reader view as well as visually. The ideal situation would be go from The Main Header (h1) to the subheader (h2), and then to the content. Once the content has been read, they jump to the next prev nav bundle. After that they can jump to the main nav elements if they would like to choose a slide out of sequence.
• Think about the NAV. How will someone using a screen reader navigate to the next slide.
• Keep in mind how will the user keep track of where they are using only a screen reader.

[ianvanhoof]

OK, I created the skip links in such a way as to always allow imediate skip link access directly to the content area of the slide, and right after that is a link that leads directly to the table of contents menu. So every time you change the slide you have a choice.

[ianvanhoof]

• created the shadow interface the way that I envisioned the experience to be.
• Tested everything with vigor .
• Added tabindex to enable keyboard focus on certain elements.
• Managed element.focus() to bring the keyboard focus to the elements that need it.
• added hints in strategic places so the keyboard user understands their scope.