I'm a big proponent of this being added - especially after trying to use the site exclusively for a few days on the iPad.
- Another icon in the edit bar adds clutter or bumps something still widely used.
- Those that don't like seeing ⌘ might oppose tools that encourage use of the
- The formatting of these disrupt paragraphs just like an image embed can.
- The iPad keyboard is way less efficient to get to < and / than a physical keyboard.
- Keying S takes 12 presses on a real keyboard (i suppose 5 of those are shift "letters" but it is one action to make the letter not two taps like on the iPad)
- Keying S takes 25 presses on an iOS keyboard (try it yourself right now... I bet you'll mess up the / and have to use a few more taps than the most efficient way about half the time you try this)
- It makes discovery of and use of that tag easier for new users.
- It makes the site look professional and matches Apple's style of documenting key presses. (See the following pages of the 2009 version of the style document: 41, 100-101 especially read pages 100 through 101 for the difference between order, using - vs +, and more)
- It makes it easier non-native level english readers to understand in a flash that the answer calls for a specific key to be pressed.
- AutoCorrect on iOS and now Mac OS X futzes with these non-dictionary tags making automation more important to avoid incorrect tags.
Here's where my opinion really gets aired - I realize and like that it's not a universally shared opinion :-)
I would like to be lazy and have the toolbar help me add key caps markup syntax easier to type.
< kbd > and < /kbd > could be added just like block quote and code sample.
Are there any stats on how often these tags get used on Ask Different? What percentage/count of users has ever used X tag might be interesting to compare. Also - what percentage/count of questions have used said tags.
Perhaps no-one is using < kbd > except for me?
I think the style guide is a bit harsh on how bad these are in practice - so I'll add an answer there in defense of how easily people new to mac can see option + command +P +R intuitively means you hold them all down together.
Specifically, the confusion over naming of keys is due to Apple changing their symbols over time, people remembering the old way, and the fact that keyboards are different around the world as well as on Windows / Mac.
The other confusion is the difference between the silkscreened mask on the keyboard doesn't match the menu shortcuts. For example, all macs now use ▲ and ▼ printed on the keyboard, but if you look in the Bookmarks menu of safari, you will see the characters drawn as ↑ and ↓
Blaming the key cap
<kbd> format for these problems is a red herring - the confusion exists whether you spell out command or use ⌘, whether it's an up arrow or an up triangle. We as a community have to deal with that confusion either way. Why not automate the formatting so people can pay attention to the message - making answers here match what mac users have had in their language for describing key presses for years.
I am of a strong opinion that when used properly, these tags make the site look professional and better match the documentation that Apple provides. I would want to encourage people to know it's possible and make it easier to select a word like option and automate wrapping it.
Geting to the < > and / are tedious alone on iOS and autocorrect needs to be beat into submission which makes it even harder to get that edit done while mobile.