Rubious

Posts Tagged ‘Web Standards’

Safari 4 beta released

Tuesday, February 24th, 2009

safariToday Apple released a new beta version of their browser, Safari. This release is for Mac and Windows.

The new browser features:

  • Cover Flow — You can browse through your site history or bookmarks the same way you browse album covers in iTunes
  • Top Sites — look at renderings of your favorite sites, and open any one of them with a single click
  • Full History Search — A clever way to visit sites you have been to in the past. You can type a word or phrase into the history search field and you’ll get a cover flow view of sites that match your criteria
  • Nitro Engine — Apple claims JavaScript now executes 30 times faster than IE7 and 3 times faster than Firefox
  • Tabs on Top — Allows Safari to have multiple pages open at the same time in a single browser window, and to switch back and forth with a click. This is very similar to Google Chrome. The new Safari beta gives you more room at the top of the screen when in tabbed mode.
  • Windows Native Look and Feel — The Windows Safari 4 beta more closely matches the look of other Windows applications and gives access to standard Windows fonts; Apple claims the same performance boost on Windows as in the Mac version

Other features include Full Page Zoom, a ‘smart’ address field, a ‘smart’ search field, and more robust phishing and malware protection.

Visit Safari on the Apple website | More information on upgrading your browser.

Accessibility in web design

Friday, January 30th, 2009

Many people see accessibility as a need to give those with disabilities special treatment. They consider it an additional expense that will not give much tangible improvement on their sales, and so ignore it completely.

In actual fact, accessibility is about treating everyone– no matter what their ability–the same. It also needn’t cost any extra – by creating websites with accessibility in mind you can write your code to the standards and have it accessible with no extra effort. Bolting on accessibility features as an afterthought (such as builders adding a ramp to a building which previously only had stairs) can be inefficient and expensive. Websites created by Spring Bud always have accessibility in mind.

Some of the common mistakes which hinder accessibility:

  • Building websites with tables/frames – two old practices which create complicated and messy code – screen readers have trouble understanding the order to read things in and the invalid code causes problems
  • Using images with no text alternative, often websites will be created as a large image which is chopped up – text in images cannot be read by screen readers, and cannot be enlarged for people with poor vision.
  • Using Flash for websites – although Adobe are making great strides to improve the accessibility of Flash, it still cannot compare to plain text. Additionally, people using older versions of screen readers (they are expensive!) will not have the latest updates that allow Flash to be readable.

An added benefit is that Google and other search engines act just like disabled viewers – they are not currently able to see text in images, they struggle reading Flash content and prefer HTML valid web pages. This means in ensuring your website is accessible you are also improving your search engine ranking.