steveax

40 ms·

361.
by steveax 14y ago
The technique in question here is omitting labels and relying upon the placeholder attribute only. If you're suggesting that a JavaScript technique could hide the labels for non-screen reader users, how exactly do you intend to determine th
362.
by steveax 14y ago
The key phrase there being: "allows everyone to access the basic content and functionality". By not using labels you are excluding screen reader users.
363.
by steveax 14y ago
Supporting screen reader users is not "progressive enhancement", rather, it is basic and essential.
364.
by steveax 14y ago
Yes, really bad trend. In addition to the usability issues the article mentions for sighted users, using placeholder without labels leaves screen reader users without any clue what the input is for.
365.
by steveax 14y ago
Of course it's always best to consult with an attorney, but Nolo Press has good self-help legal resources.
366.
by steveax 14y ago
You're missing one very important detail: if a user already has jQuery loaded from Google's CDN (which is pretty likely, way more likely than having loaded your local copy) the browser won't make any requests.
367.
by steveax 14y ago
I (slightly) prefer tabs because as others have noted, it allows different users to set their preferred indentation. I'm surprised no one has mentioned EditorConfig: http://editorconfig.org/
368.
by steveax 14y ago
Nice! Incredibly clear what the choice is.
369.
by steveax 14y ago
Portland salaries WRT cost of living will probably never be as favorable as some other cities, that said, there are intangibles that make up the difference for many of us. A couple of links that might be useful: http://siliconflorist.com/j
370.
by steveax 14y ago
I have a different idea on pricing for new developers: decide what you want to really get paid (hourly rate) and if you need to "eat" some time learning, then eat it. You'll get faster as you learn more and hone your process and eventually
371.
by steveax 14y ago
Screen readers will use whatever document outline that the browser renders, no?
372.
by steveax 14y ago
I've gone back to static generators almost exclusively - full circle really as some of my first web pages were generated with Userland Frontier (anyone remember Clay Basket?) nanoc ( http://nanoc.stoneship.org/ ) is currently my tool of cho
373.
by steveax 14y ago
I don't really see the issue. Prep an ogg ant a mp3, include both sources in the audio tag and your golden.
374.
by steveax 14y ago
All the social buttons and 3rd party crap on that website crashed Safari on my iPhone. Lord what I would pay to have Adblock and noscript on my iPhone.
375.
by steveax 14y ago
Nice, succinct article and good examples. Very helpful.
376.
by steveax 14y ago
The HTML 5 spec refers to it simply as "the title element" (as opposed to a title attribute) http://dev.w3.org/html5/spec/single-page.html#the-title-elem... There is no such thing as "on page title". There may be a top level heading in th
377.
by steveax 14y ago
Indeed. Also add "ninja" to the list (WTF is that supposed to mean anyway?) Other tip off phrases: "must love fast paced environment", "ability to juggle multiple projects" (read: our process is non-existent or broken)
378.
by steveax 14y ago
Good info without quackery but why do you call the title element "meta title"?
379.
by steveax 14y ago
Sounds like a good case for a Greasemonkey userscript. Maybe trap the up/down arrow keys rather than tab.
380.
by steveax 14y ago
More about the DRM than the ads.
381.
by steveax 14y ago
I gave up using the Apple supplied Apache a while back. It became difficult to accommodate the diverse collection of server configurations I have to support and Vagrant + Puppet handles that very nicely. For those who have more modest needs
382.
by steveax 14y ago
Worst advice ever. I thought "click here" died years ago. Hostile to AT users. Please value humans over google.