CSS has a bunch of cursors already . Chances are, you’re not using them as much as you should be. Well, should is a strong word. I can’t cite any evidence offhand that special cursors is some absolute boon to user experience or accessibility. But it certainly seems like a nice touch. Like:
.copy-button { cursor : copy; } Code language: CSS ( css )
Or
[disabled] { cursor : not-allowed; } Code language: CSS ( css )
These cursors are actually supplied by your OS, and thus can be altered by the OS. That’s a good thing, as some OSs let you bump up the size of the cursor (with a url() value), for example, which is good for accessibility. You can set custom cursors as well, which won’t get bumped up, which is bad for accessibility .
Looking around at our 2.0 Beta editor, I can see lots of CSS-provided cursor changes.
I’m pretty pleased with those!
An interesting aspect of “custom” cursors is that they are only obviously a problem if you replace the actual cursor itself.…