A little over a week ago, my awesome employers graciously allowed (and paid for) me to trek up to Edinburgh to enjoy the recently-resurrected standards-based web conference, The Highland Fling. The theme was “back to basics”, which covered a whole lot of ground, and brought with it some very talented speakers. The whole event was compered expertly by Christian Heillmann, with each talk lasting 40 minutes and allowing 20 at the end for an entertaining Q&A chat between him and each speaker.
It all started with Steve Marshall talking about “Why Simple Isn’t”. Steve spoke about a variety of phenomena, such as cognitive dissonance & confirmation bias – he even made explicit reference to one of my favourite blogs, youarenotsosmart.com (dare you to go there and escape pre-3am, it’s like wikipedia and tvtropes had a more-addictive child). Sometimes the links between these themes and the conference-matter felt somewhat tenuous, but I found it to be a very interesting talk nonetheless. The Q & A really brought it back on track though, with Christian & Steve actively linking the aforementioned phenomena with selling things such as best practice to colleagues and management.
Rachel Andrew was up next, with a talk entitled, “Choosing the right Content Management System”. I was initially worried about a conflict of interest – what with her being involved in her own CMS, Perch. However, she proved very even handed, defending WordPress at times and only referencing her own system when it felt necessary. She talked through the many relevant heuristics that need thinking about when choosing a CMS – linking such a choice to users, the project spec & (possibly most-importantly) content strategy. What was particularly fascinating for me, was her idea of eschewing WYSIWYG and replacing it with structured content and markdown / textile / whatever for formatting. This is something that I intend to look a lot further into in the future, and going to take a lot of selling business-side at work!
Then came Jack Osborne, who gave a very thorough technical primer on HTML 5 – he went through a lot of the new elements and features, and showed them in action within the context of the latest version of Opera. Jack also talked about how you can start implementing them day-to-day right now, while compromising on business decisions such as supporting IE without JS. I especially liked the idea of using <div class=”article”> wherever you would eventually use <article>, in order to get you in the right mindset for when the HTML5 change inevitably happens. One interesting question that Christian asked was about explaining the new form elements to designers and whether they would necessarily be embraced, Jack explained that a unified, consistent UI is good for everyone – a viewpoint that I’m also a fan of.
Remy Sharp talked next about “Interaction Implementation”. In this, he spoke about his process of breaking down a visual comp into individual components and giving estimates of what it was going to cost. This talk was right up my alley, and probably the one which I took the most away from for day-to-day working. He broke an actual design he did many years ago down into individual elements – identifying possible troublespots. He talked about potential risks (such as 3rd parties) and actual costs (including how he assesses IE6 as an added feature). I have pages of notes from this talk, and can’t begin to summarise them all here without downright plagiarising his entire talk, needless to say, I’ll be pawing over them for a good while yet.
Conversely, for Mike Rundle‘s talk, ‘From Websites To Apps: The “Apple Look”‘, I have very little in the way of notes. It’s not that it wasn’t a good talk, I was just flagging by this point (just before the last coffee break), and I’m not hugely enamoured by the “Apple Look” (and yes, I know that I’m possibly in the minority there). Some of the bits he did point out with regards to small interface details, were interesting, and no doubt I’ll fail at emulating them myself next time I shit out another design. But I don’t think I can talk about the talk too much here while doing it the justice it deserves.
Finally, James Edwards talked about accessibility. He showed live, technical demos of WAI-ARIA features and how they’re all assembled. He talked about roaming tabbing, a feature I’d not heard of before, but makes so much sense in simply modifying tab-orders when changing contexts, I need to remind myself to have a play when I get a moment. He also talked about how these new technologies, such as ARIA, built to help interact with AJAX & the like, were being taken up by the screen reader vendors – ultimately, very slowly – but, similarly to HTML5, it’s good to learn these things in order to prepare for the future. The one thing about James that’s difficult to convey in text, is how obviously passionate he is about accessibility, regardless of the context of that word. He didn’t just talk with regards to screenreaders and disabled users, but also about how IE6 support is necessary in reaching people in developing countries and from poorer social situations. He was, however, quite pragmatic in talking about how IE6 support means achieving the same functionality as newer browsers, but not necessarily through the same means. A great session, and an absolutely fantastic way to end the day.