The Alexa Traffic Rank gives a statement about the popularity of the tested website.
"The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users (reach). As a first step, Alexa computes the reach and number of page views for all sites on the Web on a daily basis.The main Alexa traffic rank is based on the geometric mean of these two quantities averaged over time (so that the rank of a site reflects both the number of users who visit that site as well as the number of pages on the site viewed by those users)."
Source and further information: www.alexa.com.
There are either no data available regarding a traffic ranking for the tested web site, or the ranking needs definite improvement.
HTML is a mark-up language used to create websites, and is independent of platforms.
"HTML is not a programming language, since HTML does not allow to, say, control a robot, set a variable or programme a game." (Quelle)
The display of invalid or incorrect documents depends on the software reading them (browser, roboter, screenreader, etc; see above). However, the display will vary greatly depending on the software, and this can lead to errors, often without the knowledge of the website manager, since it is impossible to test the website against all updates of all the software.
Non validated HTML source text can cause high costs, especially if it causes the software to look for an error or if the functionality and therefore the user experience is impacted.
Further information:
The validity of the HTML source text can be checked with a so-called 'validator'.
Examples:
Further information
http://blog.antikoerperchen.de/beitrag/28/validierung-wozu-warum-valider-html-code-wichtig-ist.html
Acronyms:
HTML: HyperText Markup Language
The tested website appears to use XHTML, but the source text contains errors. Use the Qualidator SiteAnalyzer to find the errors on your site. Please note that it is not sufficient to validate the homepage only. To optimise access it is necessary that all pages are validated, so that display errors in various browsers can be avoided.
Marking previously visited hyperlinks helps users to identify which pages of the website have previously been read. In other words, according to Nielsen the navigation interface should answer three essential questions: "Where am I?", "Where have I been?" and "Where can I go?"
Source and further information:
"Prioritizing Web Usability" by Jakob Nielsen/Hoa Loranger and "Designing Web Usability" by Jakob Nielsen
The tested website does not support fully this type of marking.
Internet users expect hyperlinks to be either coulour coded or underlined. Therefore, the tag "underline" should not be used for non hyperlinked text. Using the tag "underline" for non hyperlinked text confuses the user, making it more difficult to recognise genuine hyperlinks.
Source and further information:
"Prioritizing Web Usability" by Jakob Nielsen and Hora Loranger
http://www.usability.ch/Alt_nav/Alertbox/NJ_20040510.htm
The tested website uses an "underline" tag for non hyperlinked text.
Not all visually impaired people make use of technical support to navigate on the internet. The feature to increase fonts is an important element to ensure that all information of the website can be read by all users. Even people who are not visually impaired need to increase the font sometimes. At the same time, an increasing number of older people surf the web; they too need a feature to increase the font. To this purpose, it is important to define the font size not in pixel, but in percentage or "em".
Source and further information:
"Prioritizing Web Usability" by Jakob Nielsen/Hoa Loranger
The font on the tested website cannot be increased and defined with the automated browser feature "Text Size".
Separating design and structure of the website carries great advantages. The sharper the distinction, the more independent the two areas are. A lack of such a distinction is also called a "spaghetti mark-up" or a "tag-soup" (from the term "HTML tag").
Nowadays it is easy to save colours, type fonts, design images and to a large extent even the layout of the website in CSS files (CSS = Cascading Style Sheet).
Further information:
http://www.style-sheets.de/guide/grundlagen/warum_css
http://www.vorsprungdurchwebstandards.de/theory/retro-coding/
Hint for IT technicians: "Code" does not refer to javascript, but to HTML source.
The tested website contains spaghetti mark-up; morevover, it is not or not fully defined in CSS Format.
This test result is available for registered users and Premium Members.
More than two thirds of the test results will be available to you once registration has been successfully completed.
To have full access to the test results, and to be notified about changes in quality of the observed website, please register and upgrade to Premium Membership.
Register now free of charge
A potential warning has been identified.
Blinking and moving text should be avoided. website users would like to read at their own pace and usually they class moving text as unimportant ads. Static text can be read quicker by users and does force them to wait for returning text. Furthermore, problems may arise when printing the page.
Source and further information: "Prioritizing Web Usability" by Jakob Nielsen/Hoa Loranger, as well as hints on http://www.barrierefreies-webdesign.de/
Blinking or moving text was found on the tested website.
The logical connection between definition and form field is missing if the form fields lack an explicit title.
This means that in the instance of a linear form, it is not apparent which definition belongs to which fiels. This is why the element LABEL was introduced with the attribute for, allowing the explicit definition for form fields.
Using the element LABEL allows Screen-Readerusers in particular to view the definition of the form field directly in the form field itself.
Source:
http://www.barrierefreies-webdesign.de/knowhow/formulare/label.html. Further information can be found in the W3C accessibility guidelines (12.4 Associate labels explicitly with their controls, Guideline 12, Accessibility Guidelines for Web Content 1.0, W3C recommendations 5th May 1999http://www.w3c.de/Trans/WAI/webinhalt.html) und http://de.selfhtml.org/html/formulare/strukturieren.htm.
Form fields on the tested website do not contain correct labels.
This test result is available for registered users and Premium Members.
More than two thirds of the test results will be available to you once registration has been successfully completed.
To have full access to the test results, and to be notified about changes in quality of the observed website, please register and upgrade to Premium Membership.
Register now free of charge
A potential warning has been identified.