According to an audit made over Accessibility, violations exist over survey as follows:

Affected modules: Survey Example

• Ensure keyboard focus is indicated visually

There is no indication of keyboard focus for each set of radio buttons. This can cause confusion for keyboard only users as they try to complete the survey, and are unsure which question/set of radio buttons keyboard focus is set to.

Providing a visual indication of focus ensures that keyboard only users whom view the screen can determine exactly what action will occur based on what element has focus. This is particularly important for keyboard only users, as they cannot simply click to place focus or activate an element.

Developers should ensure that well-defined visual indication of keyboard focus is provided for all actionable elements on a page.

• Ensure headers and cells are properly associated

The "In this online unit" column header, which spans multiple columns, is only given a scope attribute of "col" which states that it only spans one column. This is technically incorrect and can result in undefined behavior for screen-reader users.
Every data cell in a complex data table must be properly associated with the column and row header cells that label it.

<th scope="col" colspan="7">

In this online unit...

</th>

• Revise the scope attribute to refer to "colgroup"
• Add a <colgroup colspan="7"></colgroup> element just after the opening of the <table> element.

<table class="surveytable" id="..." width="90%" cellspacing="1" cellpadding="4" border="0">

<tbody>

<colgroup colspan="7"></colgroup>

<tr class="smalltext">

<th scope="row">Responses</th>

<th scope="col" class="hresponse">Not yet answered</th>

...

</tr>

<tr>

<th scope="colgroup" colspan="7">In this online unit...</th>

</tr>

...

</table>