ITALIANO 
Below we have listed the 22 control points on the draft Technical Checklist, with information about the procedures used to meet the accessibility requirements and about the test techniques adopted.
Requirement 1
Proposition: Create pages and objects contained in them, with technologies, defined by formal published grammars, using the most up-to-date versions available, when they are supported by user programmes. Use elements and attributes in a manner that complies with specifications, by respecting their semantic aspect.
In particular for languages with HTML (HypertText Markup Language) and XHTML (eXtensible HyperText Markup Language) markups:
For all newly-created sites, use at least the 4.01 version of HTML or the 1.0 version of XHTML, together with DTD (Document Type Definition) of the Strict type.
Method for achieving the aim: The site is created using an instrument that automatically generates XHTML 1.0 Strict pages.
Test technique: All the pages have been validated with the Validator W3C (Validator W3C).
Requirement 2
Proposition: You are not allowed to use frames in the creation of new sites During initial application, for existing sites already created with frames, you can use HTML 4.01 or XHTML 1.0 with DTD frameset, and with the following instructions plan the transition to XHTML, at least in the 1.0 version with DTD Strict of the entire site. The transition plan must be presented to the Office of the President of the Italian Council of Ministers – Innovation and Technologies Department.
Method for achieving the aim: The instrument used in constructing the site does not allow site pages, containing Frame or iFrame, to be created.
Requirement 3
Proposition: Supply an equivalent textual alternative for every non-textual object existing on a page, and make sure, that when the non-textual content of an object changes dynamically, its equivalents are also updated. The equivalent textual alternative of a non-textual object must be of an appropriate size for the function, performed by the object in the specific context.
Method for achieving the aim: Every existing image object has a textual field (ALT attribute). Multimedial objects have a text field where you can insert the transcript of the multimedial content (of a film, or an audio file or anything else).
Test technique: Using Watchfire WebXACT and Validator W3C validation software we have verified the existence of the ALT field in all images. The individual content authors have verified the logical correctness of the inserted descriptions.
Requirement 4
Proposition: Make sure that all the information and all the functionalities transmitted in colour are available even without the use of colour.
Method for achieving the aim: The elements in the pages are personalised both in graphical terms and in code. In addition, the site authors have avoided using sentences that are meaningless for the visually-handicapped and for people with impaired colour perception.
Test technique: Sample testing of site pages.
Back to top
Requirement 5
Proposition: Avoid flashing or moving objects and messages, whose function frequencies may provoke problems with photosensitive epilepsy or problems with concentration or that might cause the failure of assistive technologies. When information needs, nevertheless, require their use, the site visitor must be warned of the risk, and methods must be prepared that allow such objects to be avoided.
Method for achieving the aim: A decision was taken to avoid the use of animated images and flash animations, unless absolutely necessary and, nevertheless never in “flashing” versions.
Test technique: Sample testing of site pages.
Back to top
Requirement 6
Proposition: Make sure that the foreground (information content) and the background are easily distinguishable, by using sufficient contrast when text is used or by a difference in sound level when the spoken voice is accompanied by background music. Text in the form of an image is not generally recommended but if it cannot be avoided, then it must be created with the same criteria of easy distinguishability as mentioned above, bearing in mind that the contrast and size of characters, inside an image, cannot be modified by the user.
Method for achieving the aim: The appearance of the pages in this site, and of the objects that make up the pages (titles, paragraphs, etc.) is defined in a centralised manner using CSS. In this way, though leaving maximum flexibility in layout for each single page, you can guarantee graphical consistency throughout the site.
Test technique: The graphics used in this site have been tested by applying the W3C colour contrast formula. The created pages were then checked using Colour Contrast Analyzer 1.1.
Requirement 7
Proposition: Use map images that are sensitive on the client side rather than on the server side, except in the case that the sensitive zones cannot be defined with a valid geometric shape.
Method for achieving the aim: In constructing the portal, a decision was made not to use server side image maps.
Requirement 8
Proposition: If server side image maps are used, supply the necessary alternative text connections in order to obtain all the information or services that can be reached by interacting with the map.
Method for achieving the aim: In constructing the portal, a decision was made not to use server side image maps.
Back to top
Requirement 9
Proposition: Use elements (markers) and attributes to describe the contents and to identify line and column headings inside data tables.
Method for achieving the aim: The inserted tables and the instrument allow and facilitate the use of TH (column headings) SUMMARY (table notes) and CAPTION (table titles) tags, in accordance with the W3C recommended standard.
Test technique: Validation of the code in all the pages, using the W3C validator, and checking of the entire site using Watchfire WebXACT software and sample testing of a few pages containing tables.
Requirement 10
Proposition: Use elements (markers) to associate data cells and heading cells in data tables, which have two or more logic levels in line or column headings.
Method for achieving the aim: A decision was taken not to use tables, on this site, with more than one logic level.
Test technique: Validation of the code in all the pages, using the W3C Validator , and checking of the entire site using Watchfire WebXACT software and sample testing of a few pages containing tables.
Back to top
Requirement 11
Proposition: Use style sheets to check on the presentation of contents and organise pages so that they can also be read when the style sheets are disabled or not supported.
Method for achieving the aim: The layout of the site has been created using style sheets and without the use of tables.
In constructing the templates, and therefore, in constructing the pages, the most appropriate tags for each situation must always be used: H1 for headings, H2 and H3 for sub-headings, P for paragraphs, OL or UL for lists, STRONG and EM for text styles; in this way, even if the style sheets are disabled, the pages can be read without difficulty and totally maintain their information content and structural logic.
Test technique: Validation of the code in all the pages, using the W3C validator, and checking of the entire site using Watchfire WebXACT software and sample testing by navigating the site and disabling the CSS or using a text browser.
Requirement 12
Proposition: The presentation and textual contents of a page must be adaptable to the interface, used by the user, without superimposition of the existing objects, or loss of information, such as to make the page contents incomprehensible; this includes the re-organization, enlargement or reduction in the size of the display area and/or of the characters, compared to the default values of such parameters.
Method for achieving the aim: The pages on this site adapt to different solutions (liquid layout) and all the texts can be enlarged or reduced using the browser commands. The total layout is based on CSS.
Since the code of the site and the CSS are correct and have been validated and tested on different operating systems and browsers, it was not necessary to make use of CSS Hack or CrossBrowser systems.
Test technique: Sample testing of a number of pages using browsers, operating systems, video resolutions and different character sizes.
Back to top
Requirement 13
Proposition: When tables are used for layout purposes, make sure that their content is comprehensible when they are read in linear fashion.
Method for achieving the aim: A decision was taken not to use layout tables on this site.
Test technique: Sample testing of pages on the site using the text browser, Lynx, and the screen reader, JAWS.
Requirement 14
Proposition: In forms, associate labels with their checks, by positioning them in such a way as to facilitate the filling in of fields by those who use assistant technologies.
Method for achieving the aim: It is possible to create extremely complex forms without needing to know any programming language.
Test technique: Testing of form filling, using mouse and keyboard and the text browser, Lynx, and the screen reader, Jaws.
Back to top
Requirement 15
Proposition: Make sure that pages are useable when scripts, applets or other programming objects are disabled or not supported. If this is not possible, guarantee the equivalent textual alternative as indicated in requirement No. 3.
Method for achieving the aim: The pages have been constructed using the non-intrusive Javascript principle, by keeping the (HTML) structure, (CSS) presentation and (Javascript) interactivity levels separate. The effects and functionalities supplied by JS, in fact, are only applied when Javascript support is present in the browser, but without sacrificing the fruition of the contents, if such support is not available.
Test technique: Even when javascript is disabled, the missing functionalities are absolutely marginal and do not jeopardize the fruition of the site and a textual alternative is not even necessary.
Requirement 16
Proposition: Make sure that managers of events that activate scripts or applets or other programming objects, or who, nevertheless, possess a specific interface of their own, are not dependent on a specific input device.
Method for achieving the aim: As explained in the previous point (Requirement 15), the only two scripts used on the site have been verified with the principal browsers and the principal assistive technologies.
Test technique: Test the scripts using mouse and keyboard, and browsers (Explorer, Mozilla, Opera, Netscape, Safari, Lynx) and the screen reader JAWS.
Requirement 17
Proposition: Make sure that the functionalities and information transmitted using programming objects, objects that use technologies, not defined by formal published grammars, and scripts and applets are directly accessible or compatible with assistive technologies.
Method for achieving the aim: As already illustrated in a previous point (Requirement 15), the scripts used have also been verified with assistive technologies. In any case, it is possible to disable these scripts without losing any functionalities.
Test technique: Sample testing of pages that use scripts.
Requirement 18
Proposition: If a film or timed, multimedial presentation are imperative for the information supplied or the service delivered, it is necessary to synchronize the equivalent textual alternative in the form of subtitles or vocal description, or associate a summary to it or a simple label, according to the level of importance and difficulties to be created in the case of real-time presentations.
Method for achieving the aim: The multimedial objects, that can be inserted, envisage an extended textual field where the description of the multimedial contents themselves can be entered, and the content authors have been trained to input explanatory and coherent descriptions.
Test technique: The individual content authors have verified the existence and logical correctness of the inserted descriptions. Check sample pages.
Requirement 19
Proposition: Make the destination of each hypertextual link absolutely clear, with texts that are meaningful, even if read out of context, or associate alternative texts to the links, which would also clearly explain the destination of the link. Prepare procedures that would make it possible to avoid repetitive reading of link sequences that are common to several pages.
Method for achieving the aim: To avoid reading repetitive link sequences, special skiplinks have been inserted in the general frames. The content authors have been specially trained in the creation of links that are meaningful if read out of context. Some rapid Accesskeys have also been used and verified with the principal browsers, in order to avoid superimpositions with the keyboard commands in the browsers themselves.
Test technique: using the Watchfire WebXACT validation software, we have checked out the hypertext links. Skiplink samples have also been checked out using screen reader.
Requirement 20
Proposition: If the fruition of a supplied service in a page requires a specific period of time for certain actions to be performed, the user needs to be advised of this, and also be given the information on the maximum time required and any alternative ways of using the service.
Method for achieving the aim: No time-based functionalities are envisaged.
Requirement 21
Proposition: Make sure that the links on the page can be selected and activated using keyboard commands or keyboard emulation technology or using pointing systems that are not mouse-based. In particular:
* the vertical distance (line-spacing) in lists of links must be at least 1 em;
* the horizontal and vertical distances between buttons on a form must be at least 1 em;
* the size of buttons in a form must be such as to make the labels inside them clearly readable, by using, for example, the internal margin (padding) between the label and the edges of the button;
* The same principles, as for form buttons, are applied to sensitive images, remembering that, in this case, the defined dimensions cannot be modified.
Method for achieving the aim: All generated links, including those within the content area on each page, or links, belonging to navigation indices can be selected with ease with every device, including the keyboard or keyboard emulation technologies. In fact, javascript, java and flash are not used on the site for the management of links and menus and, therefore, every link is in pure XHTML. The spacing and positioning of links, buttons and form fields is defined centrally, using CSS style sheets, thereby simplifying the achievement of the requirements, dictated by the second part of point 21.
Test technique: Sample testing of site pages using devices other than a mouse and checks on the link sequences and forms to verify the spacing and size of objects.
Requirement 22
Proposition: During the initial application, it will be necessary for pages on existing sites, that cannot be made to comply with these requirements, to be provided with a link to pages that meet the requirements, contain equivalent information and functionalities, and are updated with the same frequency as the original pages, thereby avoiding the creation of pages that are just text. The links to accessible pages must be shown as a clear choice at the start of each inaccessible page.
Method for achieving the aim: The site complies with all the points included in this Technical Checklist and, therefore, it is not necessary to create alternative versions of the pages.