Modelo estadístico

WCAG 2.0 Rating (A, AA) http://www.Facebook.com/ Fail http://www.Facebook.com/?sk=welcome Fail http://www.Facebook.com/?sk=welcome#!/profile.php?id=100003644343730 Fail http://www.Facebook.com/?sk=welcome#!/profile.php?id=100003644343730&s k=friends Fail http://www.Facebook.com/?sk=welcome#!/profile.php?id=100001670616318 Fail http://www.Facebook.com/?sk=welcome#!/messages/100001670616318 Fail

The global error statistics on Facebook were as follows:

• The Wave Toolbar which shows the global number of accessibility errors showed there were 41 errors on five of the Facebook webpages viewed and only 9 errors on Facebook’s home page. The Wave Toolbar also shows accessibility errors, alerts and features as outlined in the methodology chapter (automated tools) in detail. The main accessibility issues here were as follows: There was no use of alternative text on images or links. For example the mark up used was “”, which would result in a screen reader reading out the file name such as cat.jpeg rather then a “picture of a cat”. Wave also showed on the home

page under the “signing up” section the labels are missing or not labelled correctly on gender, date of birth. The Wave Toolbar also showed that few links had alternate text to say what they connected to for those using a screen reader and for the few links that did have alternative text this was not

meaningfully labelled in alternative text. The Wave Tool also warns if JavaScript used and it on Facebook which would limit what kind of screen reader can be used. On a positive note the Wave Toolbar showed that Facebook uses access keys 1-9 to allow navigation with a keyboard which is useful for somebody not using a mouse to access the website or someone who memories the short-cuts. Unfortunately the links are not linked to meaningful webpages and are not in order.

• Fangs, a screen reader emulator was used to gauge the number of links, frames and headings on a webpage which would impact on how much visual scanning a person might have to do or how many links they would have to have read out to them via a screen-reader. The average number of links on 5 of the 6 pages ranges from over 100 hundred to 200 with 39 Links on the home page. No headings were used on the home page with an average of 7-29 on the rest of the webpages. Primarily H4, 5, 6 were used on the headings. As there is no

definitive order on headings it would make a search of the website content via a screen-reader impossible. Facebook uses frames on all of its webpages with 2 most of its webpages except the home page which has one frame and the

Logged in page which has 3. This again impacts on how a screen-reader interprets codes as it splits it into different screens in which to navigate.

• The W3 HTML Validator was used to check the HTML code was adequate and valid in different browsers. For example if a person was using an older browser they might find a website harder to access and a screen reader would have more difficulty interpreting the code. An average of 40 XHTML errors were found when checking the HTML against HTML 1.0 mobile profile on all 6 of the Facebook pages used in the audit. On a positive note The W3 CSS

Validator was used to check the CSS code was valid. For example all styling

for webpages is done in the CSS rather then the HTML in case the person is using something like the WAVE toolbar to change the style of the web page to make it more accessible. An average of 3 CSS errors was found on all 6 pages when checking against CSS 2.1.

Citizens Information Website

I selected 4 pages from the Citizens Information website based on the expectation that these would be the main pages visited by users and through following the MeAc(2010) Guidelines for accessibility audits. One of the urls met the conformance levels for WCAG 2.0 for AA and the rest of the URLs failed the A, AA and AAA- conformance rating.

The global error statistics on the website were as follows:

• ••

• The HTML Validator found only 2 HTML errors on the Citizens Information

website on the Home page and Household Charge pages while checking against HTML 4.0 (transitional) which is a the type of HTML code declared in doctype and therefore would impact on how the web browser interprets the code. The main issue being that there was no character encoding declared at document level. The W3 HTML Validator also found issues in that there are links to PDF documents which are inaccessible to screen readers without modification. There were 3 HTML errors found on the How To Use the

Website page and 76 HTML errors with 6 warnings on the What’s New page.

The W3 CSS Validator was used to check that the CSS code was valid, three

of the four webpages had 52 CSS (2.1) errors with 194 CSS errors on the

What’s New page.

• ••

• The Wave Toolbar which shows the global number of accessibility errors on

the Citizens Information website, where there was an average of 1 accessibility errors on all 4 pages viewed. This was a positive result.

• ••

• The Wave Toolbar also picked up some accessibility issues which were as

follows: on the Home Page were as follows: the title social welfare had an incorrectly ordered heading (it was not a H1 or H2 heading as you would expect for a title of a home page) and this would impact on screen-reader navigation. The search box on all 4 webpages had no label on them and a JavaScript hover menu is used on the main navigation menu. On the What’s

New page Wave flagged a broken link for the mobile site. On the same webpage there were also empty headings on content and a broken link for the date on main text in the webpage. This would impact on a sighted user not be able to use the link and the empty headings would make navigation via

A-Checker Conformance Level with WCAG 2.0 Guidelines