Troubleshooting Accessibility Violations

The following table describes some accessibility problems that you might encounter when using Siebel Business Applications and provides suggestions for troubleshooting them.

This table describes how to troubleshoot some accessibility violations that you might encounter.

Problem Cause Solution

Some fields and controls in a Form applet are grouped together under a Form section. This group relationship, however, can only be identified visually – that is, the JAWS screen reader does not announce or identify Form sections.

For example, the Service Request Form applet has three Form sections: SR Information, Status and Ownership, and Summary. To vision-impaired end users, however, it is not obvious that these Form sections exist.

If using the old grid-based Web templates, then Form sections will not be announced by the JAWS screen reader.

Do the following:

  1. Move to Responsive Web templates where you can configure group headings for Form sections.

  2. Use the HTML <FieldSet> tag to group relevant fields and controls together.

Where multiple sections in a Form applet have the same field name (for example, "Address"), the JAWS screen reader announces the field name as-is (that is, "Address"), without identifying which particular Form section the field belongs to. This is confusing for users.

If using the old grid-based Web templates, then identifying which field belongs to which section in a Form applet is confusing for (vision-impaired) users because Form sections are not announced by the JAWS screen reader.

Do the following:

  1. Move to using Responsive Web templates instead of using Grid-based Web templates.

  2. Configure a unique name for all fields and controls under each section in the Form applet.

    For example, instead of configuring just "Address" for all sections in a Form applet, configure "Account Address" for the Account section, configure "Contact Address" for the Contact section, and so on.