I specialise in the front-end, especially accessibility and maintainability.

I've used CSS when everyone was still using tables for layouts. Although I knew all the quirks of IE6 and how to deal with them, I am happy that it's gone.
I get excited about every new CSS3 feature and start using them as soon as the majority of browsers support them.

The main challenge of CSS nowadays is how to organise it and maintain it. Using pre-processors like SASS or LESS helps but, like every tool, can also cause issues when not used the right way.


I advocated web accessibility since I started being a web developer. I follow the WCAG 2.0 as much as possible, my HTML is semantic and I practice progressive enhancement. As a by-product the website gets SEO-friendlier and more usable.

I know how hard it can be to get accessibility prioritised. The most basic improvements are actually not that difficult or resource-consuming. Everything else gets easier the earlier in the project you start and the more aware you are of potential issues.

In my last two jobs I taught a lot of my colleagues about various accessibility techniques and raised awareness across the company.

I like how HTML5 came to be and how it was a huge factor in the rise of mobile. I always loved to code in a flexible way. So when responsive design came around, I understood its concept within minutes and it was very easy for me to apply it.

I would never think of making a website not responsive. "Mobile first" is a good approach, although I prefer "simple first".

Personal details

Anika H.

Summary

Technical skills