So if a website wants to put the navigation menu at the bottom in the source code because it's better for mobile users, while the menu is visually plaved at the top, what are solutions to not confuzling the hell out of sighted keyboarders?
After reading some of the touchy problems out there by Patrick Lauke, I'm not certain that's always foolproof, but I'm already doing it to remove fugly focus styles I add to sites for keyboard focus
So if we were listening for keystrokes, we'd start assuming we have some kind of keyboard user. We could next listen for viewport width, but I don't think that's useful if the problem is really only affecting large-screened keyboarders
Then based on that I'd either see if I could 1) with Javascript, set positive tabindices on the menu items. I would have to test if then the next focusable after the last menu item is automatically the first content link, and if that works backwards with Shift-Tab. If it doesn't work that nicely, positive indices are out, as normally they suck balls
A skip link prevents a user from needing to tab through the whole page first, but it's still going to have a message that confuses the first-time user with my cognitive deficits
also, focus styles are quite mild so it's very easy to miss what's going on. Basically I was tabbing and shifttabbing all over trying to figure out why I couldn't get to the menu... as the page scrolled down I saw i was obviously going down the page
[karlgroves] re: putting nav at the end: Now they have to tab through all the content to the navigation. Also, it becomes confusing/ frustrating to people who want to get to the nav
My only issue with patching up this particular site only with skip links is the cognitive issue of, why am I being offered to skip TO the navigation? I would probably mis-read that the first time
I use a little javascript to let CSS remove extra focus styles from mousers (so those would just get the current dotted outline if their browser puts focus on clickables post-click)
But, if the nav MUST be last in the DOM and MUST be shown at the top, then my most ideal would be to use JS to detect keyboard and change the focus order so it makes visual sense
which is why it's more ideal to have the HTML correct... but as I said, if it was insisted that we couldn't do things the right way, I would do extra work to make the non-right-way make less work for stupids like me.
meaning landmarks are still basically a SR-only sort of thing. If I'm using FF and want super keyboard powers, I'd go whole-hog and use vimperator or something
meaning something that only navv'd by landmarks would be way less appealing.. unless it was some sort of plugin that worked on, like, all major browsers.
@StommePoes while positive tabindex is normally bad I don't see why putting (say) tabindex = 1 on everything which is focusable in that footer/header thingy wouldn't work.
there's cedders and gezmond and henny penny and watters! and hansome and putz and brand karl and buffalo billy can and gra gra and Charlie Farlie
and mitch - at least in my mind
[deborah_kaplan] I'm trying to figure out if I can make the obvious joke about nicknames without actually being partisan or bringing politics into the conversation
I love that I just spent the entire week trying to figure out why this video player we were all set to release wasn't working in Android. Dug deep into the code. Understood the problem. Submitted an issue. Got half way through developing a patch for it. Then someone pointed out that it needed <video crossorigin="use-credentials"> to work. I had <video crossorigin="anonymous"> for some reason I don't even remember at this point