Developer Checklist
The following checklists are intended to guide developers on the implementation of success criterion for the source order. The checklists should be used during the development phase to ensure WCAG 2.0 compliance of the source order on the site and should form part of the unit testing phase undergone by developers when updating or creating new content or functionality.
Areas of importance to be reviewed for source order accessibility are also covered specifically in the relevant category factsheet:
- Navigation; Content; Coding; Tables, Forms and interactive site features (e.g. Interactive Maps, Slideshow, Image Gallery etc).
Level A
Coding
SCO_A1i
DetailsHas the appropriate formatting been used (i.e. for text layout whitespace is not used to format text to into a column layout)?
<table><tr><td>Web Content Accessibility Guidelines covers a wide range of issues and recommendations for making Web content more accessible.</td><td>This document contains principles, guidelines, success criteria, benefits and examples that define and explain the requirements for making Web-based information and applications accessible.</td></tr></table>
<p>Web Content Accessibility Guidelines covers This document contains principles, guidelines,<br>a wide range of issues and recommendations success criteria, benefits and examples that<br>for making Web content more accessible. define and explain the requirements for making<br> Web-based information and applications accessible.</p>
SCO_A1ii
DetailsHas the appropriate formatting been used (i.e. for tabular content whitespace is not used to format text to look like a table)?
<table Summary="Minimum and maximum temperatures for Australian state capital cities" Caption="Temperature comparison by city"><tr><th>City</th><th>Min</th><th>Max</th></tr><tr><td>Melbourne</td><td>10</td><td>16</td></tr><tr><td>Sydney</td><td>15</td><td>21</td></tr></table>
<p>City Min Max Melbourne 10 16 Sydney 15 21</p>
Sequence
SCO_A2
DetailsDoes the visual order of columns match the order of the content with style sheets disabled?
- CSS On:
-
- CSS Off:
-
- CSS On:
-
- CSS Off:
-
SCO_A3
DetailsDoes the visual order of the site feature (i.e. navigation, form etc.) match the order of the content with style sheets disabled?
- CSS On:
-
- CSS Off:
-
- CSS On:
-
- CSS Off:
-
SCO_A4i
DetailsAre the visual and source order in the correct reading sequence in the content?
- Visual/Reading order:
-
- Source order (CSS Off):
-
- Visual/Reading order:
-
- Source order (CSS Off):
-
SCO_A4ii
DetailsAre the visual and source order in the correct reading sequence in the form?
- Visual/reading order:
-
- Source order (CSS Off):
-
- Visual/reading order:
-
- Source order (CSS Off):
-
SCO_A5
DetailsIs the keyboard focus order meaningful – does the tab order preserve meaning and operability (i.e. the TABINDEX
attribute has not been used as this may interfere with built-in logical tab order)?
TABINDEX
is not used.<input name="query" value="" size="50" class="QSInput" id="query" tabindex="3" type="text">
SCO_A6
DetailsDoes the visual and source order of the site page and/or feature match the keyboard focus order?
- Keyboard focus order:
-
- Visual/reading order:
-
- Source order (CSS Off):
-
- Keyboard focus order:
-
- Visual/reading order:
-
- Source order (CSS Off):
-
Controls
SCO_A7
DetailsIf the selection of an option causes a change in context and/or content is the change after the current focus?
SCO_A8
DetailsIf hovering over an option causes a change in context and/or content, is the change after the current focus?
- No focus on help item
-
- On focus of help item
-
Change occurs to the right
- No focus on superscript item
-
- On focus
-
Change occurs prior to the current focus
SCO_A9
DetailsIf the change in content and/or context is not instigated by the user (e.g. by selecting a button) is the user informed of the change prior to the change occurring?
