WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: SharePoint 2010

for

From: Jason Kiss
Date: Mar 28, 2012 4:23PM

The Achieving Accessibility in SharePoint 2010 document is a good one.

Everything's relative, and SP2010 does fairly well out of the box, I
think. But I wouldn't say it is possible to make it fully compliant
with WCAG 2.0 AA without creating some additional control adapters to
customise the rendering of some structures. Other issues can be
corrected through simple changes to the template and CSS files
themselves.

I'm in the middle of taking a cursory look at a pretty much default
SP2010 install. I'm rather impressed with the degree to which ARIA is
used, and the way that modal dialogs and other intermediate
notification dialogs work. "Almost" everything is keyboard accessible,
well-labelled, and pretty darn accessible compared with earlier
versions of SharePoint. I have noticed some difference in keyboard
access between Internet Explorer 8 and Firefox 8, and difficulty using
the rich text editor in keyboard-only mode.

Some potential accessibility barriers I've noted so far include:

- some text serving visually as a heading is not marked up as a heading
- text size in PT or PX units that cannot be resized in Internet Explorer
- some form elements created with neither corresponding LABEL elements
nor TITLE attributes
- some forms containing sets of radio buttons or checkboxes that are
not wrapped in a FIELDSET with LEGEND
- some form error messages (albeit with ARIA role=3D=94alert=94) placed
following the relevant form control in the source order, and no other
indication in the control LABEL
- some layout tables for which non-empty SUMMARY attributes are provided
- some vague or ambiguous link text that does not clearly identify or
distinguish its purpose
- a few table column headers not marked up as headers
- significant use of nested tables, often three and four levels deep
- significant page weights and external file requests. For example,
the home page on the default install I'm looking at is 610 KB and
makes requests for 21 separate script files.

The degree of work and effort required to address each issue obviously
depends on the issue and the default templates installed.

Cheers,

Jason


On Thu, Mar 29, 2012 at 9:08 AM, Jennifer Sutton < <EMAIL REMOVED> > wrot=
e:
> Hello:
>
> Perhaps this will help.
>
> Achieving Accessibility in SharePoint 2010: http://t.co/e9c02IxL
>
> Jennifer
>
> At 12:40 PM 3/28/2012, Tim Harshbarger wrote:
>>What is the communities opinion on the ability to set up a
>>SharePoint site so that it fully complies with WCAG 2.0 Level AA
>>success criteria?
>>
>>>>>>>
> > >