Check a Page 2.0
Barrier Site Distribution
(2012 April)
The coloured boxes in the table indicate the share of pages with a given barrier for the web sites covered in the benchmarking results. Lighter blue means fewer pages contain the barrier, darker blue means more pages. Move the mouse pointer over a box to get information on the name of the test and the percentage value.
Click on the boxes to see the page details for the selected test and web site. You can also click on the column headers to get further information on the tests.
Results 1 - 22 of 22
Sorted by: Site, ascending
List of Tests
- 1
-
Use of latest W3C technologies
Check if the latest W3C technologies are being used. It is a barrier if a webpage doesn't use the latest W3C technologies because e.g. cellphones and assistance tools doesn't necessarily support them.
- 2
-
Deprecated element
Check if the webpage contains deprecated HTML elements. This is a barrier because browsers who do not support them will not show the content correctly. Deprecated HTML elements are applet, basefont, center, dir, font, isindex, menu, s, strike and u.
- 3
-
Deprecated attribute
Check if the webpage contains deprecated HTML attributes. This is a barrier because browsers who do not support them will not show the content correctly. A list of HTML attributes can be found here: http://www.w3.org/TR/WCAG10-HTML-TECHS/#index-attributes - deprecated attributes are marked with a star (*).
- 4
-
alt attribute for non-text content
Check that content which isn't text (e.g. images, audio or video) has a describing text. Describing texts for elements which are not text is needed to make the content available for search-engines and blind or vision impaired people.
- 5
-
embed element
Check that the <embed>-element isn't used. The <embed>-element is not a part of the HTML/XHTML standard and is because of this inaccessible. Even though it may work in several browsers, one cannot expect that the content is shown in a correct way.
- 6
-
title for frame or iframe
Check if the webpage contains frames without a description. Descriptions of frames are used for identification and navigation in many browsers. Because of this, lacking descriptions of frames are barriers.
- 7
-
legend for fieldset
Check if the webpage contains a <fieldset> element without a <legend> element. <fieldset> adds to the logical structure of the page, indicating that similar elements are grouped. A lacking <legend> element in a <fieldset> element leaves the grouping without a name and is because of this a barrier.
- 8
-
label for optgroup
Check if the webpage contains <optgroup> elements without a label attribute. <optgroup> is used to group alternatives in drop down menus. A <optgroup> element without a label attribute will result in a grouping without a name and is because of this a barrier.
- 9
-
id for form control element
Check if a form element lacks a text description (ID). We often understand what to fill in based on the context of a page. It is, for example, normal to have a search button to search the site right next to the text field where the search text is to be filled in. In a screen reader such a text field will be presented without a context and because of this be incomprehensible. To make sure that all form elements are comprehensible, even without context, the form elements should be described with an ID attribute. There should in addition be a label which described what the form element is used for. For example: <label for="seach">Search</label><input type="text" id="search" />
- 10
-
Corresponding label for form control element
Check if a form element lacks a text description (label). We often understand what to fill in based on the context of a page. It is, for example, normal to have a search button to search the site right next to the text field where the search text is to be filled in. In a screen reader such a text field will be presented without a context and because of this be incomprehensible. To make sure that all form elements are comprehensible, even without context, the form elements should be described with an ID attribute. There should in addition be a label which described what the form element is used for. For example: <label for="seach">Search</label><input type="text" id="search" />
- 11
-
Different link targets
Check if links with the same title point to different targets. If “title” is not used, then only the link text is checked. The link text it often dependant on context in order to make sense. For example is the link text “read more” often used on news sites. Screen readers collect all links on a page in a list which becomes useless for navigation if all links have the same text. It is therefore recommended to give meaningful names to all links, e.g., “read more about accessibility in our municipality.”
- 12
-
DOCTYPE
Check that the page has a correct document type declaration. A correctly declared doctype is needed to make sure that the document is correctly interpreted by browsers.
- 13
-
Formal (X)HTML grammar
Check that all HTML code is written in accordance with the declared document type. Correct usage of the elements defined by the declared document type is important to make sure that the content will be shown correctly.
- 14
-
Heading levels
Check that no heading levels are skipped in the hierarchy of headings. Missing heading levels will hinder many users to navigate the page in an effective way.
- 15
-
Simulation of numbered list
Check that numbered lists are represented in a correct way. So-called simulated numbered lists may look correct, but users who do not see the list normally won't recognize it as such, and therefore can not use it..
- 16
-
Mouse-specific event handler
Check if usage of the page requires a mouse. Some users cannot use a mouse, for example motion impaired people or people browsing from a cellphone. If the website is made in such a way that a mouse can be used, make sure that there's also a possibility to use a keyboard. for example: If it's possible to navigate the website's menu with a mouse it should also be possible to navigate it with a keyboard.
- 17
-
blink element
Check if <blink> elements are used on the page. These are elemnts which make parts of the page blink. This is a barrier for people with photosensitive epilepsy, reading disabilities, and vision impairment.
- 18
-
marquee element
Check if <marquee> elements are used on the page. These are elements which makes parts of the page move sideways. This is a barrier for people with photosensitive epilepsy, reading disabilities, and vision impairment.
- 19
-
Page refreshing
Check if elements that may lead to that the page refreshes automatically is used on the page. Avoid making a page refresh automatically. When a page refreshes automatically it is a barrier for both people with reading and concentration disabilities. In addition, it destroys the browser history.
- 20
-
Page redirecting
Check if there are elements on the page which may automatically redirect the user. When a page redirects a user it is a barrier for both people with reading and concentration disabilities. In addition, such a redirect will destroy the browser history such that it becomes harder to go back. It is better to, instead of using automatic redirection, inform the user that the page is outdated and link to the new one. Alternatively the redirect can be done on the server in such a way that the redirect is invisible to the user.
- 21
-
Server-side image map
Check if the page contains server side image maps. Such maps are barriers because it is impossible to give an alternative text to the different parts of the images, and because it is required that the user uses a mouse. An example of such a map is an image where you navigate with a mouse and where it behind parts of the image is hidden different links to other pages. This is a barrier both to people who can't see the image, such as people with vision impairments who use a screen reader, and to people who can't use a mouse, such as people with motion disabilities. Server side image maps should be replaced by a more accessible navigation. One such solution is a client side image map (i.e. the <map> element) which support navigation with a keyboard and alternative text for different parts of the image map.
- 22
-
Valid CSS
Check if the design of stylesheets is correct according to CSS 1.0 or CSS 2.x. A violation of the rules for style sheets may inadvertently change the apperance of the page.