Yesterday, Tim McConnell posted a very interesting article stating what to expect from SharePoint 2010 in terms of Accessibility. Since Accessibility is a topic which is very related to compliance, I’ve decided to run a few tests against a Validation Tool to get a more objective picture.
Considering that we are still evaluating a “Release Candidate” version, the results are promising.
Fact Sheet
- Sharepoint Test Bench
- Sharepoint 2010 RC installation
- Using default “Publishing Site Template” Homepage,
- Added a calendar and a list web part
- V4.master applied instead of nightandday.master applied by default.
- Enabled Anonymous access
- Validation Tool
- Using TotalValidator v6.3.0
- Parameters:
- HTML Validation: none
- Accessibility: (see table)
- Check for broken links: no
Results
| US Section 508 | Passed! |
| WCAG v1 A | Passed! |
| WCAG v1 AA | 4 errors E821 - 1 instance E833 - 3 instances |
| WCAG v1 AAA | (idem) |
| WCAG v2 A | 6 errors E871 – 3 instances E872 – 1 instance E886 – 1 instance E892 – 1 instance |
| WCAG V2 AA | (idem) |
| WCAG V2 AAA | (idem) |
Full Report
Total errors found:
6 (WCAG v2 A: 6)
Page Layout
The line numbers refer to lines in the original source.
Any with a line number of '0' are implicit tags added by Total Validator:
39 E872 [WCAG v2 3.2.2 (A)] The submit button is missing:
<form name="aspnetForm" method="post" action="default.aspx" id="aspnetForm">
134 E871 [WCAG v2 1.1.1 (A)] Link text is missing:
<a id="HiddenAnchor" href="javascript:;" style="display:none;">
158 E871 [WCAG v2 1.1.1 (A)] Link text is missing:
<a href="#" tabindex="-1" style="display:none">
158 E871 [WCAG v2 1.1.1 (A)] Link text is missing:
<a href="#" tabindex="-1" style="display:none">
259 E886 [WCAG v2 1.1.1 (A)] Do not use the 'alt' attribute here:
<input name="ctl00$PlaceHolderSearchArea$ctl01$S3031AEBB_InputKeywords" type="text" value="Search this
site..." maxlength="200" id="ctl00_PlaceHolderSearchArea_ctl01_S3031AEBB_InputKeywords" accesskey="S"
title="Search..." class="ms-sbplain" alt="Search..." onkeypress="javascript: return
S3031AEBB_OSBEK(event);" onfocus="if (document.getElementById('ctl00_PlaceHolderSearchArea_ctl01_ctl04').value
=='0') {this.value=''; if (this.className == 's4-searchbox-QueryPrompt') this.className = ''; else
this.className = this.className.replace(' s4-searchbox-QueryPrompt','');
document.getElementById('ctl00_PlaceHolderSearchArea_ctl01_ctl04').value=1;}" onblur="if (this.value =='')
{this.value='Search this site...'; if (this.className.indexOf('s4-searchbox-QueryPrompt') == -1)
this.className += this.className?' s4-searchbox-QueryPrompt':'s4-searchbox-QueryPrompt';
document.getElementById('ctl00_PlaceHolderSearchArea_ctl01_ctl04').value = '0'} else
{document.getElementById('ctl00_PlaceHolderSearchArea_ctl01_ctl04').value='1';}" style="width:170px;" />
402 E892 [WCAG v2 1.3.1 (A)] Use CSS for presentation effects, use <em> or <strong> for emphasis:
<menu class="ms-SrvMenuUI">
More Information
WCAG v2 A Errors
- E871 - 3 instance(s): Describe the purpose of a link by providing descriptive text as the content of the <a> element. The description lets a user distinguish this link from other links in the Web page and helps the user determine whether to follow the link. The URI of the destination is generally not sufficiently descriptive. See http://www.w3.org/TR/WCAG20-TECHS/H30.html (displayed in new window)
- E872 - 1 instance(s): You must provide a mechanism that allows users to explicitly request changes of context. The intended use of a submit button is to generate an HTTP request that submits data entered in a form, so it is an appropriate control to use for causing a change of context. See http://www.w3.org/TR/WCAG20-TECHS/H32.html (displayed in new window)
- E886 - 1 instance(s): Although HTML may allow the 'alt' attribute here, it should only be used on image submit buttons. User agent support for this attribute on other types of form controls is not well defined. Other mechanisms are available to label these controls. See http://www.w3.org/TR/WCAG20-TECHS/H36.html (displayed in new window)
- E892 - 1 instance(s): Tags that are being used purely to create a visual presentation effect should not be used. You should use CSS to control layout and presentation so that users and their aids may control it. See http://www.w3.org/TR/WCAG20-TECHS/G140.html (displayed in new window)
1 comment:
This is quite promising. Have you found anything since this test in march?
Post a Comment