This statement applies to the Agresso Student Self Service web application.
On 26 March 2009, Web pages included in Agresso Student Self Service conform to Web Content Accessibility Guidelines 2.0 at http://www.w3.org/TR/2008/REC-WCAG20-20081211/. Level A conformance (with exceptions)
The technologies that this content relies upon: XHTML 1.0 Transitional, CSS 2.0 and Javascript
Criteria | Supporting Features | Remarks and Explanations |
---|---|---|
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 |
Fully compliant. All <img> elements that require alt attributes have these set appropriately | Most of the <img> elements are decorative only and are given blank alt attributes |
1.2.1 Audio-only and Video-only (Prerecorded) For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such |
Not applicable | There is no audio or video content |
1.2.2 Captions (Prerecorded) Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such |
Not applicable | |
1.2.3 Audio Description or Media Alternative (Prerecorded) An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such |
Not applicable | |
1.3.1 Info and Relationships Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text |
Compliant with exceptions.
|
There are exceptions in the case of using the <th> element to identify headers in data tables. Many of the data tables are generated using a third party control supplied by ComponentArt, and there is currently no way to display these controls with the headers using <th>. |
1.3.2 Meaningful Sequence When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined |
Fully compliant. | The majority of pages have simple layouts with no sequence issues. Pages with more complex layouts (e.g.where data has been split over 2 columns) have been tested with accessibility tools to ensure that the sequence is correct |
1.3.3 Sensory Characteristics Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound |
Fully compliant. | |
1.4.1 Use of Color Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element |
Fully compliant. | The application has a simple colour-scheme, and does not use colour as a method for conveying information. The mandatory flag is a red asterisk, but the asterisk character alone will indicate that the field is mandatory |
1.4.2 Audio Control If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level |
Not applicable. | No audio content. |
2.1.1 Keyboard All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints |
Fully compliant. | All pages have been tested using the keyboard as the only method of input. |
2.1.2 No Keyboard Trap If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away |
Fully compliant. No components trap the focus | All pages have been tested using the keyboard as the only method of input. |
2.2.1 Timing Adjustable For each time limit that is set by the content, at least one of the following is true
|
Fully compliant. The pages that require the user to be logged in, which will therefore timeout when the security token expires, have the ability to save progress which will allow the user to continure working. | |
2.2.2 Pause, Stop, Hide For moving, blinking, scrolling, or auto-updating information |
Not applicable | There is no blinking, scrolling or auto-updating content |
2.3.1 Three Flashes or Below Threshold Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds |
Not applicable | There is no flashing content |
2.4.1 Bypass Blocks A mechanism is available to bypass blocks of content that are repeated on multiple Web pages |
Fully compliant. The only repleated blocks of content are held in the header frame | On most pages the focus is automatically placed on the first input control of the form on opening the page. |
2.4.2 Page Titled Web pages have titles that describe topic or purpose |
Fully compliant. All pages have a descriptive <title> element | |
2.4.3 Focus Order If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability |
Fully compliant. All pages and forms have been designed with a logical sequence | |
2.4.4 Link Purpose (In Context) The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general |
Fully compliant. All links contain text that describes the purpose of the link | |
3.1.1 Language of Page The default human language of each Web page can be programmatically determined |
Fully compliant. All pages have the attribute xml:lang="en-gb" set on the html tag. | |
3.2.1 On Focus When any component receives focus, it does not initiate a change of context |
Fully compliant. No components initiate a change of context on receiving focus | |
3.2.2 On Input Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component |
Fully compliant. No components cause a change of context on changing their setting. | |
3.3.1 Error Identification If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text |
Fully compliant. All input errors are reported using alert boxes on submitting the form. The error is described in text and if a specific field is in error it is identified | |
3.3.2 Labels or Instructions Labels or instructions are provided when content requires user input |
Compliant with exceptions. All form controls have an associated descriptive label, using the 'for' and 'id' attributes. If the form control is contained as an element in a data table where the use of a label is not practical, the control is given a title attribute | There are exceptions in the case of using the title attribute to identify form controls in data tables. Many of the data tables are generated using a third party control supplied by ComponentArt, and if the control is automatically generated by the control it is not possible to set the title attribute. |
4.1.1 Parsing In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features |
Compliant with exceptions. All pages have been checked to be XHTML 1.0 Transitional compliant. | There are several cases where pages are not 100% XHTML 1.0 Transitional compliant. A third party control from Infragistics is used for inputting date information, and this control is not XHTML compliant. |
4.1.2 Name, Role, Value For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies |
Fully compliant. Only standard user interface components are used. |