In my first post I will briefly discuss two interesting observations from the two articles on web design linked below:
(1) The inclusion of stakeholders in the initial brainstorming process can reduce the risk of a design being signed off by a committee that has not participated in the actual design. By collaborating with those with an interest in the final product, ideas and issues are raised that could be potentially overlooked by the designer.
(2) A wireframe can be beneficial for communication as well as design. While outlining the content, layout and behaviour for the designer, the low fidelity wireframe provides a visual tool to communicate the proposed solution to stakeholders and is a simple way to prompt feedback early on in the process.
(1) As a user’s navigation is goal driven, users dislike this flow to be interrupted by pdfs, new windows or advertising. It is suggested that designs should omit anything that looks like an advertisement because web users have learned to selectively ignore anything that looks like an ad such as banners, animation and pop ups.
(2) It is suggested that users prefer websites which they feel in control of as they know what to expect when they visit it. These expectations are formed from experience of using other websites. A website can avoid losing users by staying consistent and applying the current design norms.
Using Twitter I searched for the terms JavaScript and Responsive Web Design from the articles above and found the following information:
JavaScript
In this page Javascript is described as a front end programming language responsible for the behaviour of a website; how HTML and CSS move around and animate a web page. In a short video it is explained that JavaScript is written between the script tag along with frameworks which are listed.
Responsive Web Design
In this article the objective of Responsive Web Design is described as designing a website which will enhance the user experience by catering for all device sizes. A responsive web design uses percentage based layouts in a grid system in which grids can stack as browser width narrows.
I am now following three new pages on twitter!
Web Design Ledger
This is a publication written by webdesigners. I chose this page because of the range of content which is updated regularly including tips and tools for web design, web design news, interviews, design trends and examples of good web design. And we have used an article posted by this page in the our first lab exercise!
HTML5 Hub
The profile is described as a community of web developers. It focuses specifically on HTML5. Although it does not post regularly and has a smaller following, the twitter page has posted several links that could be useful in developing my skills as a beginner.
Webdesigner Depot
Similar to the Web Design Ledger this is a blog which posts on all aspects of web design and includes tutorials. It has a large following on Twitter and over 28.1k tweets so there is plenty of content to explore! The articles will be a useful resource in learning about web development in practice.
Analysing the UI
Q1. The following websites were analysed with regard to a user with a visual impairment:
https://www.blogger.com/
This website is not easy to navigate. When logged in it is not clear how the website is organised, how to find your way around and access the different areas of the website. It is finicky and takes some practice to use it. It could be improved by simply including structured text navigation area on the left hand side.
http://edition.cnn.com/
The website is accessible to a visual impaired person in that the text is large, bold and contrasting black with the white background. However there are a lot of images displayed which a visually impaired user might not be able to see therefore should include text headings. The dynamic navigation areas at the top of the page are easy to follow but also include pictures.
http://www.amazon.co.uk/
The home page is quite cluttered but the shop by department navigation is clearly labelled. Although the navigation lists are long and might create difficulty for a visual impaired person, the links are described very specifically which is helpful if using a screen reader.
http://www.surveymonkey.com/s/LYJMBHK
Q3. The above evaluation questionnaire made me consider different factors such as the language, consistency, feedback, exits, help section, search function, page load time and currency.
Q4.The CNN and AMAZON websites were analysed using the validator
http://validator.w3.org/mobile/
The CNN result was 0% mobile friendly;
It failed in several areas. The failures categorized as critical and severe were:
The total size of the page (1.6MB) exceeds 20 kilobytes (Primary document: 78.3KB, Images: 93.4KB, Style sheets: 1.4MB)
The certificate is invalid.
-The size of the document's markup (78.3KB) exceeds 10 kilobytes
The CSS style sheet is not syntactically valid CSS
I could not find a website that rated higher than 60%. I tried several and Facebook was the only website that gave a result other than 0%.
http://www.amazon.co.uk/ did not return a result after several attempts, the webpage showed a message that the server returned an empty or invalid response.
Amazon.com however was rated at 36%;
The page size limit is given as a critical error: The total size of the page (207.7KB) exceeds 20 kilobytes and one severe error the CSS style sheet is not syntactically valid CSS.
Q5.The evaluation reports positive web accessibility for both in Features such as Alternative text, Structural Elements such as headings, lists and tables and HTML5 and ARIA.
The parts of the webpage which hinder accessibility are reported as Errors, Missing alternative text, linked image missing alternative text, missing form label, document language missing, empty button and empty link. There are also Alerts and Very Low Contrast Errors reported.
The accessibility errors are in the same areas for both websites but Amazon carries a higher frequency of errors with an additional error of missing alternative text. As this is a comparison between a News versus a Shopping website, the differing content type, size and style of each website could influence the differences in the type and frequency of accessibility errors.