What fresh hell is THIS now? - Patrick Lauke
[jyung] @marcysutton: Thanks for the response!
does the containing action really need to be accessible
So the User profile_ does not (like you said, it’s redundant), but _Stats link would need to be accessible somehow, right?
[jyung] Sure! I actually posted the question as a comment to the file, but here it is!
:wave: Hey all! I’m building a list of profiles. Both User profile and Stats are links that will navigate to another page. In addition, when clicking anywhere (except for the _Stats link), inside each container, I want it to also navigate to the user’s profile page (same as clicking the _User profile link).
I initially wanted the container itself to be an <a>
such that right clicking anywhere in the container will show the Open link in new tab menu option, but we cannot have an <a>
nested inside an <a>
.
Alternatively, I was thinking of having the list container element be role=“listbox”
with aria-activedescendant
. What’s the right approach here to ensure everything is accessible?
listbox
? For voiceover, I want the ability for users to navigate through the item containers first and when they are interested in a specific item, then they can jump into the item and get into the two links. make sense? (voiceover beginner here)
.ext-webkit:focus { outline: none !important; }
[aria-busy="true"] { cursor: progress; } [aria-controls] { cursor: pointer; }
* { background-color: pink; background-size: 98% 99% !important; color: #ff69b4; display: none !important; }
* { usability: none; }
display: table;
?