Re:Microsoft, Please Stop This Madness
by kevingadd on Saturday September 18, 2010 @10:30AM
(#1704218)
I don't know if I buy it. The jump list isn't really part of the page itself, it's metadata attached to the 'website' in question, so I sort of understand them putting it in <meta>... at the very least, I don't think it makes sense as an inline <menu> element in the middle of the page content. It sucks having all those meta tags there, though, since that's a huge blob of html that has to go in the header of every page when it really should live in a metadata file somewhere on your site... sort of like a stylesheet.
[ Parent
| on HN ]
Re:Microsoft, Please Stop This Madness
by alsomike on Saturday September 18, 2010 @03:00PM
(#1704734)
His solution is to put the menu in the page content, and use a CSS work-around to not display it. What about screen-readers? I don't think he thought this through.
> What about screen-readers? I don't think he thought this through.
yes, what about screen readers? Screen readers get a well-thought-of menu of accelerators to existing features of the website. If the website is well coded, this can even be one of the website's own, displayed menus.
What is there not to like?
Instead, by embedding it in random meta elements, screen readers have to download the useless code (as does every other browser out there) and can not use any of it.
And screen readers would implement that by detecting a meta tag named "ms-application-jumplist"? In other words, screen reader developers should support proprietary Microsoft extensions rather than using the standard methods of supporting screen readers?
You're right, it's brilliant.