Declaration of Accessibility

This site was produced in accordance with the 22 point Technical Evaluation of the Stanca Act of 4/2004 "Facilitating computer access for disabled users" (Appendix A - "Accessibility to internet-based applications: technical specifications and evaluation" Government Directive July 2005).

The 22 key accessibility requirements are listed below, along with an explanation as to how we met with each one and what methods were employed to validate this.

The pages and the objects within them shall be produced using technologies which are based on formal, published grammars. Latest versions of these shall be used when supported by user programmes. Elements and attributes shall conform to specifications and respect the semantics. As far as HTML (HypertText Markup Language) and XHTML (eXtensible HyperText Markup Language) markup languages are concerned:

The site was produced using FlexCMP, a content management system for accessible sites (www.flexcmp.com) which automatically creates XHTML Strict pages. The overall site framework (which the user can personalise) was created in Strict version XHTML 1.0.
The authors were responsible for structuring the contents in a linguistically correct way after appropriate training in accessibility.

All the site pages passed the XHTML Strict validation, using the W3C Validator. Last checked 7 February 2007.
As far as language is concerned, all the main pages in each section, as well as numerous sample pages, were checked manually. Last checked 7 February 2007.

Frames are not allowed in the development of new Web sites. If an existing website which was developed using frames is to be activated, HTML 4.01 or XHTML 1.0 with DTD frameset can be used with the following provisos:

FlexCMP, the CMS for accessible sites, cannot be used to create frame-based sites so any FlexCMP-based site will automatically conform to standard 2.

This is unnecessary as the technology used does not allow for the use of frames.

A text equivalent for every non-text element on a page shall be provided, and when the non-text content changes, its text equivalents shall also be updated. The text equivalent of a non-text element will perform the same function within the given context.

FlexCMP allows for a text equivalent ("alt" function) for every image as well as footnotes. The system uses a series of checks during editing to remind authors to insert descriptions which correspond to the informational content of the image. Similar functions are available for films, and other multimedia content.

FlexCMP has an inbuilt image and multimedia validation tool which was used to check the image descriptions inserted by the authors. Date of last check: 7 February 2007. The spider on the Bobby 5 software was used to check all the images on the site. Last checked: 7 February 2007.

Make sure that all information and all functions are available even without the color used to present them on the page.

With FlexCMP, the different aspects of the interface are differentiated by different graphics as well as codes. For example, the current entry on the navigation menu is denoted by a different color, as well as the tag "strong" and elimination of the tag "a". During training sessions in accessibility prior to activation of the site, authors were warned about using phrases like "see red box" or "choose green link" (which have no meaning for non-sighted people or people with color disability). Although the authors could be as creative as they liked with the page content, fundamental aspects of the layout and style were decided centrally and applied either to the whole site or whole sections. The objects available for page layout only include logical/semantic information, not visual.

The home page, and main pages in each section which can be accessed from there, as well as numerous sample pages, were checked manually. Date of last check: 7 February 2007.

Flashing or moving objects or writing, whose frequency could affect light-sensitive epilepsy or concentration disorders, or even cause malfunction of the assistive technologies used, shall be avoided. Should these prove necessary, the user shall be warned of possible risks beforehand, and informed how to avoid these elements.

Training courses in accessibility, alongside training in the use of FlexCMP, taught authors to avoid animated images or flash animation unless absolutely necessary (and never to use flashing with a frequency between 4 and 59Hz).

The home page and main section pages directly linked to it, as well as numerous sample pages from the site, were checked manually. Last checked: 7 February 2007.

Ensure that the foreground and background can be clearly distinguished by providing sufficient contrast ( in the case of text) or different sound levels (in the case of speech with musical background). Text in image form is generally not recommended but, if it cannot be avoided, it must be produced using the same criteria mentioned above.

In a FlexCMP- based site, the way the page and its objects looks (headings, paragraphs etc) is pre-determined by the CSS. In this way, overall graphical cohesion of the site is assured, though there is plenty of flexibility as regards the layout of the individual page. All the style sheets used for the pages and general canvases were all checked for minimum color contrast according to W3C color contrast algorithms.

We used the JuicyStudio color contrast analyser strumento di validazione CSS JuicyStudio which uses W3C algorithms on all the cascading style sheets (CSS) used. In those areas of the site where it proved impossible to specify text and background colour in the same way, we used the software freeware ColorTester instead. Last checked: 7 February 2007.

Use client-side, rather than server-side, image maps, except where sensitive regions cannot be defined with one of the valid geometric shapes provided by the DTD in use

FlexCMP only allows you to insert client-side image maps, thus avoiding the problem of accessibility associated with server-side images.

None was necessary as the technology used meant that server-side maps could not be inserted.

If server-side image maps are used, alternative text links shall be provided to access all the information or services that are available by interacting with the map.

The FlexCMP interface does not support server-side image maps so it is not possible for the end user to insert them, only the site administrator. We preferred not to insert any in this site.

NesNone necessary as the chosen technology prevented the use of server-side maps.

The elements (markup) and attributes provided by the DTD in use shall be used to describe content and identify row and column headers in data tables.

The FlexCMP editor supports data tables at a logical level (X lines by Y columns) and enables you to put row and/or column headings by automatically generating the "th" tag rather than the "td" tag for the heading boxes. You can create a summary of the contents of any data tables ("summary" function). Whole data tables can be imported from Word, Excel, WordPerfect or other Office Automation software just by cutting and pasting. FlexCMP recognises the number of columns and rows, inserts the cell values and removes any formatting attributes so the final data layout is done through CSS.

Pages with data tables were checked using the W3C validator, and checked for their language (headings and summaries present and correct, abbreviations etc.)

Elements (markup) provided by the DTD shall be used to associate data cells and header cells in data tables with two or more logical levels of row or column headers.

The FlexCMP editor does not support tables with more than one logical level. If these are necessary, xhtml pages, or sections of pages, containing tables which are accessible at more than one logical level can be imported.

No data tables were included that had multiple logic levels of headers.

Style-sheets shall be used to control content presentation and page layout to ensure readability even when the style sheets are disabled or not supported

The layout of the site was done using style sheets and without tables. The general canvases are in XHTML so can be laid out using CSS or tables, whereas the page contents are generated directly by the FlexCMP engine and so are without tables.
FlexCMP always uses the most appropriate tags in any given situation: "h1" for main headings "h2" for subheadings, "p" for paragraphs, "ol" for lists, "strong" and "em" to highlight the text. Thus, even when the style sheets are disabled, the pages can still be read without problem and their informational content and logical structure are preserved intact.

The pages were checked using the W3C validating tool, Validatore del W3C, and the style sheets were manually disabled to check that there were no problems with the pages and that they could be read easily.

The layout and text content of a page shall be adaptable to the user interface and browser window without any overlapping of objects or loss of information which might make comprehension difficult. This is also true if the display area and/or characters are made bigger or smaller compared to their default parameters.

ICSS is used for the layout and the contents are perfectly fluid. The contents area on each page is also fluid and resizeable. FlexCMP can recognise whatever browser connects to the site, and is able to dole out differentiated portions of CSS to each browser to make up for any shortfalls in their graphics potential. Unlike Hack CSS (for example the famous Tantek Çelik technique) used on static XHTML sites, every line of the FlexCMP - managed CSS conforms to the specifications and so is completely valid

All the supported browsers (see below) were used to navigate the site to see if there were any noticeable differences in terms of information and/or graphics and to make sure the layout isn't lost when the pages are resized by the user window (within the minimum limit of 800*600 pixels). We also ensured that navigation was possible when style sheets, images, script and applet were disabled and pages were linearised, even using the Lynx text browser browser testuale Lynx

Here is the list of the browsers used.

For PC Windows:

For Apple:

When tables are used for layout:
ensure that they are comprehensible when linearized;
when using the elements and attributes of tables, respect the semantic value defined in the specifications of the markup language used.

The site designer was responsible for individual page layout and this was done using portions of XHTML and CSS (canvases). Sites with tables and sites with only CSS can thus be produced. On this particular site we preferred not to use layout tables.

The pages were subsequently checked using the W3C Validator.

In forms, associate labels explicitly with their controls, positioning them in such a way as to make it easier for people using assistive technologies to fill in the fields.

Even fairly complex forms can be produced without knowing any programming language. The basic objects (like text field, drop-down menu, etc) can be inserted into the FlexCMP visual editor and when they come to be published, FlexCMP automatically generates a code for them, using correct "labels" for each corresponding element in the form. If javascript doesn't support forms, they still work perfectly, the user simply has to manually remove the predefined values.

The positioning and the attributes were checked by comparing the label codes with the corresponding commands on the form. The functionality was also checked with javascript disabled.

Ensure that pages are usable when scripts, applets, or other programming objects are disabled or not supported. If this is not possible: provide an explanation of the function provided; provide a text equivalent as indicated in Requirement 3.

The site works without javascript, java or flash because all the interactive functions use server-side codes. Only two javascript elements are used in FlexCMP: one to empty the pre-defined fields in forms (see point above) and the other to open the links in a new window, with a signal in the "title" field (because in Strict version XHTML the "target" attribute has been removed from the links)

The pages were examined manually and the available mechanisms were also checked

For scripts, applets, and other programming objects, or any element that has its own interface, event handlers shall not be dependent on a particular input device.

The only two javascript functions used, as detailed above, can both be used with either a mouse or keyboard. These scripts were tested using Jaws screen reader. Although we carried out numerous tests, should you discover any incompatibility with these two functions, you only have to modify the FlexCMP engine to solve the problem in any site produced in the same way.

Relevant pages of the site were checked manually and using the JAWS screen reader

Ensure that functionality and the information conveyed by programming elements such as scripts and applets that use technologies not defined by formal published grammars are directly accessible or compatible with assistive technologies

As we said in the previous point, the only two scripts used by FlexCMP were checked with assistive technologies too. These scripts can also be disabled without compromising the functionality.

See above.

When films or multimedia presentations are indispensable to the information or service, an equivalent synchronised textual alternative in the form of subtitling and/or auditory description shall be provided. Otherwise, provide a summary or a simple label for every video and multimedia element, bearing in mind how important each one is and how difficult real-time presentations are to produce.

Multimedia objects which can be inserted have a text field where the description of the contents should be written.

Pages containing multimedia content were checked manually.

The destination of each link shall be clearly identified using text that is meaningful, even when read out of context. Or alternative texts that similarly explain the target destination shall be provided for each link. Mechanisms to enable users to skip repetitive navigation links found on more than one page shall be provided

For this site, the descriptions of the links are the responsibility of the content authors and there is no way round this. The people responsible for the overall layout of the site can insert links where appropriate to skip to specific points on a page. The site supports rapid Access keys so the authors can link these to specific menu entries.

We checked the hypertext links using Bobby 5.0 software. Individual authors checked that the descriptions inserted were correct.

When a timed response is required to use a service delivered through a web page, the user should be alerted, informed of the maximum time available, and offered alternative ways of using the service.

FlexCMP does not use timed responses. If certain applications which use timed responses are integrated into a FlexCMP-based site, the authors who integrate them are responsible for providing prompts which alert the user.

No evaluation was necessary for this as there is no timed response on any of the pages serving the site.

Ensure that links can be selected and activated through keyboard commands or keyboard emulation technology or pointer systems other than the mouse. To ease the selection and activation of links using these assistive technologies, it shall also be ensured that:
the vertical distance in lists of links and the horizontal spacing between consecutive links should be at least 0.5 em; 
the horizontal and vertical distances between buttons on a form should be at least 0.5 em;
the buttons in a form should be big enough to ensure that their labels can be clearly read

All the links generated, whether these be within content areas on the page or those on navigation indexes, can be selected using any of the devices mentioned above. JavaScript, Java and Flash are not used on this site so every link is in XHTML. The spacing and positioning of the links, buttons and fields is defined centrally through the CSS which makes it easier to comply with point 21.

The site pages were checked manually.

Where pages on existing sites do not conform to the standards set out above (they are not accessible), on initial application, links shall be provided to pages that do conform. These pages should contain the equivalent information and functionalities as the original pages and be updated with the same frequency. The creation of text-only pages should be avoided. Any links to accessible pages shall be clearly available as an option at the start of the non-accessible pages

The site conforms to all the standards set out in this technical validation and so no alternative versions of pages needed to be produced.

Although great care went into producing this site, and numerous tests were run, we cannot guarantee that, unbeknown to us, the odd page is not accessible to particular categories of user.
Should this be the case, we apologise and ask you to report any problems you find segnalare ogni irregolarità riscontrata so we can solve them as quickly as possible.