Thoughts, ideas and solutions on UX, web accessibility and design
Should we ignore the 0.3% of site visitors that use Internet Explorer 6? Or should we provide a fairly basic, yet functional experience? Matt Lawson explains how at Nomensa, we can create functional sites for all, no matter which OS, browser or device.
In recent posts we have talked about what a front-end tool kit is, how we are using them, and why we feel they are important. Thus I thought I would share some of our experiences when using different tools so far.
A Technical Delivery Document is designed to aid the client's understanding of the way we work and what the outcome is on the end user. We feel it is beneficial to try and communicate our approach at the start of a project and better manage the client's expectations at the same time.
A short guide to how and why you should validate your code.
This is a quick guide on how to check the colour contrast on your website. A simple way to check colour combinations meet the requirements set by version two of the Web Content Accessibility Guidelines.
Links that opened in a new window have always been a sticky point when it comes to accessibility; ever since the Web Content Accessibility Guidelines (WCAG) 1.0 were released way back in 1999. These guidelines made it clear that pop-up windows should be avoided whenever possible. However, there are occasions when opening a new window or tab cannot be avoided. If this is the case, we can avoid confusing or disorientating the users by providing a textual indicator.
The third in a series of How To guides from Nomensa. Matt Lawson, Web Developer at Nomensa discusses how to use the lang attribute to specify the language of your website and individual elements on a page.
A look into how we can detect font smoothing using JavaScript to improve visual styling for different users.