Sunday 30 November 2014

OUGD504 // Studio Brief 03: Staying web safe

Web design requirements:

Are the fonts web safe?
Baskerville is a web safe font, however Bebas Neue is not.

  • My reason for not changing Bebas Neue to a web safe font is that I will use it in image format, which suits the menu options; it is not used for body text. Doing this will mean it is not changed into a default web safe font automatically in people's browsers.
  • A challenge is the website being used by non-English speaking viewers; using the text as an image means there will be no option to translate it into a different language. However, the font is only used to express the art movements which have (almost) global names to them, making it less of an issue (and the top menu). It is also used for the drop down menu of artists' names, which obviously can't be translated.
  • The menu options across the top of the page however, are just english words which wouldn't be recognised by non-English speakers. This is a small downfall to my website, but it is a website which is just starting off, meaning that a huge surge of people using the site who can't understand 'About, Artists, Search, Contact' in simple terms would be unlikely.
  • If the website started getting a large amount of viewers, this is something that would probably become more of an issue, but at this stage it is not.

Are the colours web safe?
Almost all my colours are except for one or two. However, in this day and age this does not seem to be an issue anymore. Technology has developed so that computers made over the past five years have monitors capable of displaying 24-bit/32-bit colour, which is a possible 16.7 million colours. This means that most people viewing my website would be able to view the colours I have used, unless they are used a very old piece of technology. My target audience is young people, meaning this risk is unlikely.

No comments:

Post a Comment