Hello. I’m a freelance web content writer and editor. I create concise, accessible copy in plain English. Nice to meet you.

Simple, clear copy (in any language)

One of the first rules of web copywriting is to use plain English, to give every reader the best chance of understanding your content. Your website is available to the entire world and will have visitors who have a first language different to your own. Don’t forget, however, that native speakers also have differing reading and writing abilities.

Writing in a simple, clear style benefits all users; it makes your website easier to read and understand (communicating your messages more effectively). Concise copy fulfils accessibility requirements for both people and search engines, making your website also easier to find.

Reading ability will vary within your own audience

The W3C’s WCAG 2.0 has a reading level criterion that says if the ‘text requires reading ability more advanced than the lower secondary education level’, a version that is not more advanced should also available.

This caters for ‘people with reading disabilities [which may include highly educated members of the intended audience] while also allowing authors to publish difficult or complex web content’.

Consider users with different native languages

Some websites (and printed materials) provide services for audiences that they know speak a different first language. These sites are often well written, with this fact at the forefront of their writers’ minds. As an immigrant in Spain, I’ve been experiencing this first hand.

I’ve had to sign up to all sorts of exciting (!) government departments, ranging from the local council to social security. Naturally, I’ve tried to find out online what I need to do (I speak some Spanish; learning more).

Where the language has been simple, structured in short sentences and paragraphs, I’ve had fewer problems. (There’s also a point about website usability, in terms of expecting certain buttons in certain places, but that’s for another day.)

This has only reinforced what I already know, but it’s good to be at the receiving end to remind me.


Posted: February 26th, 2009 | Author: admin | Filed under: Accessibility, Language, Writing style | Tags: | No Comments »

Mobile websites…or not?

Twitter has been buzzing about Jakob Nielsen’s latest Alertbox newsletter, in which he says:

“To solve the problems [users experience on mobile devices], websites should provide special mobile versions.”

My initial thought was that it makes sense in some cases. This is from the perspective of corporate, not e-commerce, websites, because this is where my experience lies.

Does it depend on audience need?

While mobile users may wish for the same experience as other users, for some audiences (such as investors) it comes down to wanting access to business-critical information as quickly as possible.

If this is via a simple site with limited navigation, then surely the minimal investment makes sense? An example is the Rolls-Royce dedicated mobile site, which has been around for some years.

Accessible websites already cater for mobiles

However, I’m not an expert in this area and it’s been interesting to read others’ opinions, especially in relation to accessibility. A particularly good article was posted by Iheni (and she should know, because she IS an expert), who basically said absolutely not:

“To me this just extends the problems of walled gardens for users and leads developers down the road of additional and unnecessary work.”

She goes on to highlight the overlap between the W3C’s Mobile Web Best Practices (MWBP) and the Web Content Accessibility Guidelines (WCAG), as discussed by the Web Accessibility Initiative (WAI). If a website is accessible, by default it should be practically device independent too.

Corporate websites have more pressing issues

So, if companies’ sites complied to accessibility best practice, in theory mobile users would have fewer problems. I now wonder if some businesses might think that providing a separate site for mobiles would relieve them of some of the responsibility of creating more accessible websites overall?

Although as Graham Charlton at Econsultancy says, perhaps they should ‘improve the usability of their main website[s] before even thinking about mobile’.

I think this debate will run and run, and I’m going to follow it with interest.


Posted: February 17th, 2009 | Author: admin | Filed under: Accessibility, Mobile web, Usability | Tags: , , , , , , | No Comments »