Day 27: Managing Focus and Logical Order
I learned a few things today that will not only make me a better accessibility specialist, but also a better developer.
Things I accomplishedPermalink for "Things I accomplished"
- Watched a couple of A11ycasts on YouTube.
What I learned todayPermalink for "What I learned today"
- There's a 'template' HTML element for rendering content when called upon. Cool! Not supported by IE 11, of course.
- In the case of an SPA, don't forget to change the page title alongside managing the focus of the pages element.
- The position of the some "subscribe to newsletter" components can be problematic if not positioned appropriately in the DOM. I had to quickly evaluate this site, and was relieved that it didn't have that problem.
- Labeling (naming) techniques are not all treated equally. Importance is computed. In other words, if several techniques are combined, one could overwrite another. Examples of labels (names) that may overwrite one another, dependent upon importance:
- Reminder: not every person who uses a screen reader is a keyboard user; likewise, not every keyboard user is a person who uses a screen reader.
ResourcesPermalink for "Resources"
- Managing Focus, Allycasts #22 (YouTube)
- Does reordering content affect accessibility? Allycasts #21 (YouTube)
- Understanding Success Criteria 4.1.2: Name, Role, Value (WCAG)
- Link text replaced by aria-label attribute (PowerMapper)