The recent 'vexing viewports' article on Alistapart is a call on device manufacturers to choose a reasonable CSS-pixel resolution for each device so that responsive design works. This is something I totally agree with and support, but I'm not sure the iPad mini example they use is as clear it seems.
I keep reading recommendations for using EMs or other typographical units for layout, which I still don't understand. At best it is an extra layer of abstraction, at worst it is misleading and likely to cause more issues than it solves. I will try to demonstrate why pixels are the best relative unit.
Layout methods in web design have gone through a transition in the last few years, unfortunately we're still using floats a lot, but flexible layouts have made a comeback in the form of responsive design - which is great. Recently though, I have been puzzled by people suggesting that we should use EMs for layout...
I've noticed a bug in Webkit browsers that impacts accessibility: Zooming in does not trigger media queries. Responsive design techniques can really help people who zoom in with their browser, but not in Chrome or Safari at the moment.
I noticed something in the browser stats before I noticed it on my laptop - Google's Chrome doesn't ask you about updates. I knew, almost subconsciously, that there was a Google updater programme running. However, I didn't realise the impact it could have on web development, and potentially users as well.
Layouts are becoming an issue again. The (browser) landscape is changing, as are the fashion in layouts, but not really in unison. I can understand giving a greater weight towards design aspects, and maintaining the grid, however, I find the timing curious, as these changes seem likely to be obsolete soon.
With all the fuss over AJAX and Flash accessibility you get, I thought it might be worth outlining the process we used to create a Flash/AJAX widget and highlight one of the advantages you get with this method. It also means that the use of Flash has no impact on your Search Engine Optimisation.
Steve Falkner did a good presentation to the WSG last week, outlining how and why AJAX can work with screen readers. One tiny little point I wanted to pick up on was whether it was a waste of time to update AJAX content if you've attached an event to an element that isn't a link or form control.