Mobile devices are a great way to check the Web when you're on the go or away from your computer. It seems that almost all mobile devices today have web capabilities. Yet, each mobile device is unique. Different screen resolution, screen dimensions, and shapes.
It could be very important for one to develop a mobile device oriented site. I guess it might depend on what site you design, like say a sales website. Either way, knowing how to develop a site for a mobile device will eventually be a must the way I see it. The future seems to hold the promise that everyone will have a personal mobile device that will perform multimedia tasks. Browsing the Web happens to be one of those tasks.
What technology excites me is the actual mobile devices that can connect to the Web, along with their other features. In a sense, they're like mini laptops. Especially ones with a full keyboard and wide screen that could easily function for the Web.
Sunday, October 12, 2008
Sunday, October 5, 2008
Accessibility
While doing research, I came across the Web Content Accessibility Guidelines (WCAG), which happens to be published by the W3C's Web Accessibility Initiative. Not only are these guidelines about making content more accessible for disabled users, but also for all user agents, including highly limited devices.
There are three priority levels to these guidelines:
Priority 1: Web developers must satisfy these requirements, otherwise it will be impossible for one or more groups to access the Web content.
Priority 2: Web developers should satisfy these requirements, otherwise some groups will find it difficult to access the Web content.
Priority 3: Web developers may satisfy these requirements, in order to make it easier for some groups to access the Web content.
Web accessibility in general aims to address: Visual, Mobility, Auditory, Seizures, and Cognitive issues amongst users. By following the 14 guidelines of the WCAG, you should be able to make your website accessible.
I think it's important to keep your website accessible because you want all users to be able to see and read your content. If someone with a disability tries to access your website, with say a screen reader, if your website isn't accessible for them, the screen reader won't be able to communicate the content properly. It's almost as if you're keeping these users out and only allowing fully able users into your "club".
There are three priority levels to these guidelines:
Priority 1: Web developers must satisfy these requirements, otherwise it will be impossible for one or more groups to access the Web content.
Priority 2: Web developers should satisfy these requirements, otherwise some groups will find it difficult to access the Web content.
Priority 3: Web developers may satisfy these requirements, in order to make it easier for some groups to access the Web content.
Web accessibility in general aims to address: Visual, Mobility, Auditory, Seizures, and Cognitive issues amongst users. By following the 14 guidelines of the WCAG, you should be able to make your website accessible.
I think it's important to keep your website accessible because you want all users to be able to see and read your content. If someone with a disability tries to access your website, with say a screen reader, if your website isn't accessible for them, the screen reader won't be able to communicate the content properly. It's almost as if you're keeping these users out and only allowing fully able users into your "club".
Subscribe to:
Posts (Atom)
