1. Contenuto della pagina
  2. Menu principale di navigazione
  3. Menu di sezione
  1. Form di ricerca
  2. Mappa del sito
  3. Menu delle utilità
    1. Guide to the Site
  4. Grafiche alternative
    1. Dimensione carattere: normale
    2. Dimensione carattere: grande
    3. Versione ad alto contrasto
  1. Italiano
  2. English
  1. Aggiungi ai preferiti
  2. Invia questa pagina per email
  3. Printer friendly version of the page

Contenuto della pagina

Declaration of Accessibility

Objectives of this website

This site has been set up with the objective of satisfying all the requisites of the Technical Verification of Law 2/2004 (known as the Stanca Law).

Herein below we set out the 22 checkpoints of the Technical Verification, with an indication of the modalities with which the requisites of accessibility have been met and the verification techniques adopted. 

Go to page Technical Verification on published accessibility  (Enclosure A).

For ease of consultation,  we attach a further summary page of the results of the self-verification.

 

List of requisites and relative conformity

Requisite 1

 Instruction: set up pages and objects in the pages using technologies having formal grammar published in most recent available versions when supported by user programs. Use elements and attributes in ways which conform to the specifications, with respect for the semantic element. In particular, for HTML HypertText Markup Language and XHTML (eXtensible HyperText Markup Language):

 
  • for all new sites use at least version 4.01 of HTML or preferably version 1.0 of XHTML, in any case with DTD (Document Type Definition) of the Strict type;
  • for existing sites, in a first application, in a case in which it has not been possible to satisfy point a), use may be made of the above-indicated languages with DTD Transitional, but with the following specifications:
    1. avoid using, in the marker language the page is written in, elements and attributes for defining the characteristics of presentation of the page (for example, characteristics of text characters, text colours having the same colour as the background, etc.) using instead CSS style sheets (Cascading Style Sheets) to obtain the same graphic effect;
    2. avoid generating new windows; where this is not possible, advise the user explicitly of the change in focus;
    3. plan the transition of the whole site to the version with DTD Strict of the language used, communicating same to the Government Department for innovation and technologies and also to the National Centre for Information Technology of the civil service.
 

Methods for Attaining the Objective: the site is realised through the CMS or FlexCMP accessible sites, which automatically generates XHTML 1.0 Strict pages.

Verification technique: all the pages have been validated using the W3C Validator.

 

Requisite 2

Instruction: frames may not be used in realising new sites. In a first application, for existing Web sites already realised using frames, use is permitted of HTML 4.01 or XHTML 1.0 with DTD frameset, but with the following specifications:

 
  • avoid using, in the marker language the page is written in, elements and attributes for defining the characteristics of presentation of the page (for example, characteristics of text characters, text colours having the same colour as the background, etc.) using instead CSS style sheets (Cascading Style Sheets) to obtain the same graphic effect
  • make sure that each frame has a meaningful title in order to facilitate identification and navigation thereof; if necessary, also describe the aim of the frames and their interrelationship;
  • plan the transition to XHTML, at least version 1.0 with DTD Strict of the whole site to the version of the language used, communicating same to the Government Cabinet, Government Department for innovation and technologies and also to the National Centre for Information Technology of the civil service.
 

Verification technique: with CMS for FlexCMP accessible sites, it is not possible to produce sites based on Frame: consequently each site based on FlexCMP responds to Requisite 2.

 

Requisite 3

Instruction: provide an equivalent textual alternative for each non-textual object present in a page and ensure that when the non-textual content of an object dynamically changes, the relative predisposed equivalent contents are also updated; the equivalent textual alternative of a non-textual object must be made commensurate to the function exerted by the original object in the specific context. 

Methods for Attaining the Objective: with CMS for FlexCMP accessible sites, it is not possible to produce sites based on Frame: consequently each site based on FlexCMP responds to Requisite 2.

 

Requisite 4

Instruction: ensure that all the informative elements and all the functions are available even in the absence of the particular colour used for presenting them on the page.

Methods for Attaining the Objective: with CMS FlexCMP the elements of the pages are customised both in graphics and codes; for example in the navigating menus the current page is identified both in a different colour and with the use of the "STRONG" tag instead of the "A" tag. Also the authors of the site have avoided expressions such as "look at the red box, or click on the blue button", as these would be meaningless to the non-sighted or persons having colour disabilities.

Verification technique: inspection of site page samples.

 

Requisite 5

Instruction: avoid flashing or moving objects and writing whose intermittence frequencies might cause photosensitive epileptic disturbances or disturbance to concentration, or which might cause malfunctioning of the assistant technologies used; should information needs require their use, advise the user of the possible risk before commencing them and predisposed methods which enable them to be avoided. 

Methods for Attaining the Objective: the authors have been advised to avoid animated images and flashes if not strictly necessary, and in any case these should not flash.

Verification technique: inspection of site page samples.

 

Requisite 6

Instruction: Ensure that the informative content (foreground) is always distinguishable from the background or is at different sound levels (in a case of spoken information with a musical background); avoid presenting text in image form; where it is not possible to follow these guidelines, use the same distinguishing criteria as indicated herein above.

Methods for Attaining the Objective: in this site the appearance of the pages and the objects making it up (titles, paragraphs etc.) are centrally defined through the CSS. In this way, though maximum page-setting flexibility is allowed, the graphical coherence of the whole site is ensured.

Verification technique: the graphics used on this site have been verified by applying the W3C colour contrastive formula via the JuicyStudio CSS validation tool. Sample verifications have also been made on some site pages.

 

Requisite 7

Instruction: use client-side sensitive image maps rather than server-side, except in a case in which the sensitive zones cannot be defined with one of the predefined geometric forms indicated in the DTD adopted.

Methods for Attaining the Objective: with FlexCMP the image maps can be inserted only by the site administrators and not by the users. In this site the administrators have chosen not to use image maps, so requisite 7 is not applicable. 

 

Requisite 8

Instruction: where server-side image maps are used, supply alternative text connections necessary for obtaining all the obtainable information or services by interacting directly with the map.

Methods for Attaining the Objective: with FlexCMP the image maps can be inserted only by the site administrators and not by the users. In this site the administrators have chosen not to use image maps, so requisite 8 is not applicable.

 

Requisite 9

Instruction: for data tables use the elements (markers) and the attributes included on the DTD used for describing the contents and identifying the headings of lines and columns.

Methods for Attaining the Objective: the FlexCMP editor supports data tables at a logic level (X lines for Y columns) and enables specification of line headings and/or column headings by automatically generating TH tags in the place of TD tags for the heading cells. For each data table it is possible to specify the summary (SUMMARY). It is also possible, in a single copy and paste operation, to import whole data tables from Word, Excel, WordPerfect or other Office Automation software: FlexCMP recognises the number of lines and columns and pastes the values of the cells while eliminating any formatting attributes such as to format the data with the sole use of centralised CSS.

Verification technique: validation of the code of all the pages with the W3C pages and sample examination of some pages containing tables.

 

Requisite 10

Instruction: for data tables use the elements (markers) and the attributes included on the DTD used for describing the contents and identifying the headings of lines and columns.

Methods for Attaining the Objective: FlexCMP editor does not support tables having more than one logic level. If it is indispensable XHTML pages or portions of pages can be imported, containing tables that are accessible at more than one logic level. In this site it has been decided that tables with various logic levels will not be used.

Verification technique: validation of the code of all the pages with the W3C pages and sample examination of some pages containing tables.

 

Requisite 11

Instruction: use style sheets for controlling the presentation of the contents and organise the pages such that they can also be read when the style sheets are disabled or not supported. 

Methods for Attaining the Objective: The impagination of the site is done using style sheets and without the use of tables.  With FlexCMP the general frames, done in XHTML 1.0 Strict, can be impaginated with CSS or with tables. The page contents, generated directly by the FlexCMP motor, is without impagination tables.
FlexCMP uses the most appropriate tags for each situation: "H1" for the tiles, "H2" for the subtitles, "P" for the paragraphs, "OL" for the lists, "STRONG/EM" for the block /italics in the text: thus even with the style sheets disabled the pages can be read easily and they completely conserve the information and logical- structural content.

Verification technique: validation of the code of all the pages with the W3C pages and sample examination of some pages containing tables using the Accessibility Toolbar for disabling the style sheets.

 

Requisite 12

Instruction: the presentation and textual contents of a page must be adaptable to the size of the browser window used by the user without superposing objects or losing information which would make the page incomprehensible, even where there is a re-sizing or reduction of the viewable area, or an enlargement or reduction of the viewing area or characters with respect to the predefined values of the parameters.

Methods for Attaining the Objective: the pages of this site are adaptable to the different resolutions (liquid impagination) and all the text can be enlarged or reduced with the browser commands. All the impagination is based on CSS. FlexCMP can recognise the browser connected to the site and serves portions of differentiated CSS for each, with the aim of compensating any defects of impagination connected with the single programs. Differently to CSS Hack techniques (such as the famous "Tantek Çelik hack") used in static sites, each line of CSS served by FlexCMP conforms to the specifications and is perfectly valid.

Verification technique: sample examination of several pages via the browser (the test group comprises Internet Explorer 5, 5.5, 6, 7; FireFox 1.5 e 2; Mozilla 1.7; Netscape 8.1; Opera 8.5 e 9; Safari e FireFox 1.5 e 2 per MacOS X Tiger; FireFox 1.5 and 2 per Linux), video resolution (from 800 by 600 pixel on) and different font sizes (from normal to very large in Internet Explorer 6).

 

Requisite 13

Instruction: In a case of use of tables for impagination, guarantee that the table contents are comprehensible even when the contents are read in linear form and use the elements and attributes of a table with respect for the semantic value defined in the used marker language specification. 

Methods for Attaining the Objective: with FlexCMP the general frames of the pages can be realised with tables or CSS. The contents of the page, generated by the FlexCMP motor, are always without impagination tables. For this site it has been decided not to use impagination tables.

Verification technique: inspection of site page samples using the Lynx text browser and the JAWS screen reader.

 

Requisite 14

Instruction: in forms, explicitly associate labels to controls by positioning them such that the compilation of the fields on the part of the user of the assistive technologies is facilitated.

Methods for Attaining the Objective: even very complex forms can be realised without any need for knowing any programming language. Base objects of the form are entered in the visual editor of FlexCMP (such as text fields, drop menus, etc) and during the stage of publication FlexCMP automatically generates the code, correctly associating the labels to each field of the form. 

Verification technique: verification of the form compilation with mouse and keyboard, with the Lynx text browser and with the JAWS screen reader.

 

Requisite 15

Instruction: guarantee that the pages are usable when  scripts, applets, or other programming objects are disabled or not supported; where this is not possible provide a textual explanation of the function performed and guarantee an equivalent textual alternative, as indicated in Requisite 3.

Methods for Attaining the Objective: sites based on FlexCMP function without the use of Java or Flash since all the interactive functions use server-side code. Only two optional Javascripts  can be used. The first is used if it is desired to enter the predefined values in the form fields (as required by WCAG 1.0 at point 10.4) with the aim of eliminating default values when entering the field.
If Javascript is not supported the default values must be manually removed.
The second script is used for opening the links in new windows, avoiding the limitation of XHTML 1.0 strict, which has removed the "TARGET" attribute.
In this case, if the author of the contents chooses to open the link destination in a new window, Javascript warns the user, including the warning in the "TITLE" field of the link (as required by the WCAG 1.0 at point 10.1).
If Javascript is not supported the link does not open in a new window and the warning is not added.

Verification technique: even with Javascript disabled the lacking functions are absolutely marginal and do not prevent use of the site, as no textual alternative is required.

 

Requisite 16

Instruction: guarantee that event managers activating scripts, applets or other programming objects, or who possess a specific interface of their own, are independent of a specific input device.
Methods for Attaining the Objective: as explained in the preceding point (Requisite 15), the only two scripts used in the site have been verified with the main browser and the main assistive technologies.

Verification technique: verifies scripts with mouse and keyboard with browsers (Explorer, Mozilla, Opera, Netscape, Safari, Lynx) and with the JAWS screen reader.

Requisite 17

Instruction: guarantee that the functions and information carried by means of programming objects using technologies not defined by formal published grammars, scripts and applets are directly accessible.

Methods for Attaining the Objective: as already illustrated in the preceding point (Requisite 15) the only two scripts used by FlexCMP have also been verified with the assistive techniques. In any case, the scripts can be disabled without loss of functionality.

Verification technique: inspection of site page samples.

 

Requisite 18

Instruction: if a film or multimedia presentation are indispensable for the completeness of the information or the service provided, an equivalent textual alternative should be provided, synchronised by sub-titling or vocal description, or there should be provided a summary or a simple label for each video or multimedia element, taking account of the importance and difficulty of realisation in a case of transmissions in real-time.

Methods for Attaining the Objective: multimedia objects which can be entered include an extended textual field in which the description of the multimedia contents themselves can be entered. The authors of the contents have been formed on entering the explanatory and coherent descriptions.

Verification technique: a new analytical tool provided by FlexCMP has enabled examination, via a single summary report, of all the multimedia contents in order to verify the significance of the associated textual descriptions.

 

Requisite 19

Instruction: make the destination of each link clear with meaningful texts even if read independently of the context, or associated to the links alternatives which have like explanatory characteristics, as well as providing mechanisms which enable repetitive writing of sequences of connections common to several pages to be avoided.

Methods for Attaining the Objective: to avoid reading of sequences of repetitive links, special skip links have been entered in the general framework.
For the creation of meaningful links if read out of context, the authors of the contents have been formed.
Some rapid-selection keys have also been used ("ACCESSKEY"), verified with the main browsers, with the aim of preventing superposing with the browser keyboard commands.

Verification technique: using Bobby 5.0 validation software (now substituted on-line by the successor program WebXact) we have verified hypertextual links. The skip links have been sample-verified using the JAWS screen reader. The meaningfulness of the links out of context has been verified using a new analytical tool supplied by FlexCMP which in a single summarising report gives all the links entered in each page.

 

Requisite 20

Instruction: if a predefined time interval is set for using a service supplied in a page, within which interval certain actions have to be performed, the user has to be explicitly warned with an indication of the maximum time allowed and the alternatives for using the service.

Methods for Attaining the Objective: FlexCMP includes no time functionality. If applications are integrated in a site base on FlexCMP which include a predetermined time interval for performing certain actions the persons responsible for the integration must take care to enter a special warning. In this site there are no time functionalities.

 

Requisite 21

Instruction: make the links on a page selectable and activatable via keyboard or keyboard-replacement technologies different from a mouse; to facilitate selection and activation of the links on a page it is necessary to guarantee that the vertical distance of link lists and the horizontal spacing between consecutive links is at least 0.5 em, and the horizontal and vertical distance between the buttons in a form is at least 0.5 em and that the dimensions of the buttons in a form are such as to make the label contained therein clearly legible.

Methods for Attaining the Objective: all the links generated, whether internal in the contents area or belonging to navigation indices are perfectly selectable with any device, including keyboards or keyboard-replacement technologies. The site does not use Javascript, Java or Flash for managing links and menus and thus every link is in pure XHTML.
The spacing and positioning of the ink, buttons and form fields is defined centrally via CSS style sheets, which simplifies the attaining of the requisites dictated in the second part of the point.

Verification technique: sample verification of the site pages via devices not including the mouse, control of the link sequences and the forms in order to verify the spacing and sizing of the objects.

 

Requisite 22

Instruction: for existing site pages which cannot respect the above-listed requisites (pages not accessible) when first applied, supply a link to a page which can respond to the requisites, bearing information and functionalities equivalent to the non-accessible page and updated with the same frequency, thus avoiding creation of text-only pages; the link to the conforming page must be made evident at the start of the non-accessible page.

Methods for Attaining the Objective: the site conforms to all the points of the present Technical Verification and it is therefore not necessary to realise alternative versions of the pages themselves.

 

Help us improve our service

Though we have taken great pains in setting up our site, with numerous tests made, we cannot in all certainty be sure that one or more pages, unbeknown to us, may still be inaccessible to some user categories.

If this is the case we apologise and invite you to inform us of any irregularities or difficulties encountered  so that we can eliminate them as soon as possible. 

 

Technical enclosures for printing off

Menu di sezione

Enter in the Market
  1. Valida il codice XHTML della pagina corrente - collegamento al sito, in lingua inglese, del W3C
  2. Valida il codice CSS - collegamento al sito esterno, in lingua inglese, del W3C
  3. Vai alla dichiarazione di accessibilità

Realizzato con il CMS per siti accessibili FlexCMP ©