OzWiki relaunch!

We are pleased to announce that we’re re-launching OzWiki, our database of web accessibility errors, examples and solutions.

This new version of OzWiki continues to provide the same great informative content as the old, building on over fifteen years of experience in the web accessibility field. The big change is that it’s now available as a monthly subscription, automatically rebilled via PayPal. Subscriptions are available now.

(If you’d like to save some money, there’s also an annual subscription available for $350. That’s a saving of $118 a year!)

OzWiki organises errors into nineteen distinct categories.

Here are some examples of the sort of material you get with an OzWiki subscription:

Map/Complex image next to a link with the same target location does not have an empty ALT attribute

CategoryImages
TopicImproper use
WCAG SC 1.1.1: Non-text Content

All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed:

  • Controls, Input: If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to WCAG 2.0 guideline 4.1 for additional requirements for controls and content that accepts user input.)
  • Time-Based Media: If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content. (Refer to WCAG 2.0 guideline 1.2 for additional requirements for media.)
  • Test: If non-text content is a test or exercise that would be invalid if presented in text, then text alternatives at least provide descriptive identification of the non-text content.
  • Sensory: If non-text content is primarily intended to create a specific sensory experience, then text alternatives at least provide descriptive identification of the non-text content.
  • CAPTCHA: If the purpose of non-text content is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities.
  • Decoration, Formatting, Invisible: If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by assistive technology.

http://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html

See more errors for this SC

LevelA
Technique(s)

H2: Combining adjacent image and text links for the same resource

ImpactLow

Error

When a linked image is adjacent to text that links to the same page, the ALT attribute of the image should be empty. This is not the case with some linked images on the site.

Incorrect Example(s)

Screenshot:Thumbnail photograph of a person standing in front of wall with a Turning Point logo. Article title and summary are to the right of the thumbnail.
Code:
<a id="content_1_centre_2_rptResults_ctl00_lnkItemImg" href="/Publications/Video-Gallery/Drinking-cultures-and-social-occasions---Turning-Point-report-launch.aspx"><img title="" id="content_1_centre_2_rptResults_ctl00_imgItem" src="/%7E/media/ResourceCentre/video/turning-point_th.ashx" style="border-width: 0px;"></a>

Solution

Images next to a link should have an empty ALT attribute. Ensure that only one link encompasses both the image and the link.

Date fields are not coded using LABEL FOR and ID and grouped with the FIELDSET element

CategoryForm
TopicFieldsets
WCAG SC 3.3.2: Labels or Instructions

Labels or instructions are provided when content requires user input.

http://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-cues.html

See more errors for this SC

LevelA
Technique(s)

H91: Using HTML form controls and links

ImpactHigh

Error

The Date fields do not have unique coded field labels.

Incorrect Example(s)

Screenshot:Date fields need to have unique coded field labels indicating, month, day, year, etc.
Code:
<td align="left" valign="top"><input id="CardMonth" name="cardexpirymonth" size="2" maxlength="2" value="" type="Text" align="CENTER"> / <input id="CardYear" name="cardexpiryyear" size="2" maxlength="2" value="" type="Text" align="CENTER">   month/yeartd>
Screenshot:Form with the words 'Expiration Date', with 2 drop-down boxes. One states '06' and the other '2016'

Solution

Ensure field labels are included for the Date fields using LABEL FOR and ID.

Visual order of columns does not match order of content with style sheets disabled

CategoryStyle Sheets
TopicSequence
WCAG SC 1.3.2: Meaningful Sequence

When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.

http://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-sequence.html

See more errors for this SC

LevelA
Technique(s)

C27: Making the DOM order match the visual order

G57: Ordering the content in a meaningful sequence

ImpactHigh

Error

With style sheets disabled, the right hand related information column occurs prior to the content in the  page.

Incorrect Example(s)

Screenshot (CSS on):Site with banner across the top, content in the centre and Related information in the right column
Screenshot (CSS off):Banner is shown first, followed by the Related information followed by the content of the site

Solution

Ensure that the layout of the page (with style sheets on) matches the source order of the page (with style sheets off).

Users of the previous version can continue using that for the time being and will be migrated across over the next few days.

Leave a Reply

Your email address will not be published.