Tuesday, 13 May 2008
Final Live Client Work
Bachmann Junior website is completed, games and images are finally uploaded. It has now been tested and it is uploaded online. To view the website click here www.tumeiluong.com/bachmannjunior
Sunday, 4 May 2008
Personal Research Project - Artefact 5 HTML markups
As stated in theW3C Web Content Accessibility Guidelines checkpoint 9.4, it is important to create a logical tab order through links, form controls and objects.
But tabindex attribute are often neglected or forgotten by many web developers. There is an argument that when using the tabindex, a user could be misguided through a web document when using the tab key. Therefore I applied the tabindex attribute onto certain elements such as: a, area, button, input, object, select and textareas and evaluated this prototype to investigate for myself whether or not it should be in great use on every webpage.
I found this was slightly time-intensive when applying this attribute. I had to be sure the coding was correctly entered, so the web page/content flows in a logical manner or therefore the website will be in bad use for mobility impaired users. For example on the inaccessible website that I created, the tabindex was coded incorrectly. So if a user with mobility
impairment is trying to navigate their way through the website or trying to fill in a form, it will certainly be impossible for them to do that. As a result I think this attribute is very useful for users who have a condition which prevents them from making effective use of a mouse. Referring back to the argument, it could possibly misguide users. If I was to only apply a tabindex structure within the form on my website, a mobility impaired user would be navigated straight to the first tabindex when the first tab key is pressed. Therefore the user is probably expecting to be navigated straight to the first hyperlink on the page. However the problem was solved by providing an extensive structure on my website by taking site navigation and form elements into consideration. Personally, I thought tabindex works effectively on users who have difficulty with using a pointing device and it should therefore be applied on every website so every user have equal access.
But tabindex attribute are often neglected or forgotten by many web developers. There is an argument that when using the tabindex, a user could be misguided through a web document when using the tab key. Therefore I applied the tabindex attribute onto certain elements such as: a, area, button, input, object, select and textareas and evaluated this prototype to investigate for myself whether or not it should be in great use on every webpage.
I found this was slightly time-intensive when applying this attribute. I had to be sure the coding was correctly entered, so the web page/content flows in a logical manner or therefore the website will be in bad use for mobility impaired users. For example on the inaccessible website that I created, the tabindex was coded incorrectly. So if a user with mobility
impairment is trying to navigate their way through the website or trying to fill in a form, it will certainly be impossible for them to do that. As a result I think this attribute is very useful for users who have a condition which prevents them from making effective use of a mouse. Referring back to the argument, it could possibly misguide users. If I was to only apply a tabindex structure within the form on my website, a mobility impaired user would be navigated straight to the first tabindex when the first tab key is pressed. Therefore the user is probably expecting to be navigated straight to the first hyperlink on the page. However the problem was solved by providing an extensive structure on my website by taking site navigation and form elements into consideration. Personally, I thought tabindex works effectively on users who have difficulty with using a pointing device and it should therefore be applied on every website so every user have equal access.
Subscribe to:
Posts (Atom)