Context Navigation

Changes between Initial Version and Version 1 of Ticket #26602, comment 3

initial	v1
1		I think that a patch for this somewhat depends on what happens with the keyboard focus patch; I can provide a patch that assumes the current behavior (navigation by keyboard through the <div> elements), but an actual commit to this really depends on choices made in keyboard navigation. If, instead of navigating to the <div> element, navigation passes from action items (Activate & Customize links), then instead this needs to use aria-describedby or screen-reader-hidden to indicate which theme the link references.
	1	I think that a patch for this somewhat depends on what happens with the keyboard focus patch (#26527); I can provide a patch that assumes the current behavior (navigation by keyboard through the <div> elements), but an actual commit to this really depends on choices made in keyboard navigation. If, instead of navigating to the <div> element, navigation passes from action items (Activate & Customize links), then instead this needs to use aria-describedby or screen-reader-hidden to indicate which theme the link references.
2	2
3	3	Regardless, right now, my experience navigating by keyboard in Chrome or Firefox is that focus is moving from each individual Activate & Customize anchor element within the themes page, which is not the behavior described in this ticket.