accessibility
This site has been created in compliance with the requirements of Check 22 technology (DM 8/7/2005 - Annex A) of Law 4 / 2004 - Provisions to facilitate the access of disabled people to computing. Here are the 22 control points and an indication of how they were satisfied with accessibility requirements.
List of accessibility requirements for web sites
requirement 1
Statement: Build pages and objects within them using technologies defined by formal grammars published in the most recent versions available when supported by user programs. Use elements and attributes in accordance with the specific, respecting the semantic aspect. In particular, markup languages (HTML HypertText Markup Language) and XHTML (eXtensible HyperText Markup Language):
a) for all new sites use at least version 4.01 of HTML or XHTML preferably version 1.0, however conDTD (Document Type Definition - Document Type Definition) Strict type;
b) for existing sites, in the first application, in case you can not comply with point a) is allowed to use the version of the above languages with Transitional DTD, but with the following warnings:
1) avoid using, within the markup language in which the page is made, elements and attributes to define the presentation features of the page (for example, characteristics of the font, text color and background, etc..), but using style sheets, CSS (Cascading Style Sheets) to achieve the same visual effect;
2) avoiding the generation of new windows, where this is not possible, explicitly warn the user of the change of focus;
3) plan the transition of the entire site to the Strict DTD version of the language used and inform the Presidency of the Council of Ministers - Department for Innovation and Technologies and the National Centre for ICT in public administration.
Validation: validated site with the W3C Validator
requirement 2
Statement: It is not permitted to use the frame in the creation of new sites. In the first application to existing Web sites already made frame is allowed to use HTML 4.01 or XHTML 1.0 with DTD frameset, but with the following warnings:
a) avoid using, within the markup language in which the page is made, elements and attributes to define the presentation features of the page (for example, characteristics of the font, text color and background, etc..), but using style sheets, CSS (Cascading Style Sheets) to achieve the same visual effect;
b) ensure that every frame has a meaningful title to facilitate identification and navigation, if necessary, also describe the purpose of the frames and their relationship; +
c) planning the transition to XHTML, at least in version 1.0 Strict DTD entire site by notifying the Office of the Prime Minister's Office - Presidency of the Council of Ministers - Department for Innovation and Technologies and the National Centre for ICT in public administration.
Validation: have not been used frame
requirement 3
Statement: Provide a text equivalent for every non-text object on a page and ensure that when non-text content of an object are also updated dynamically change their content equivalent crafted, the text equivalent of a non-text object must be commensurate with the function performed by the original in the specific context.
Validation: validated site with the W3C Validator
requirement 4
Statement: Ensure that all information and all features are available even without the color used to present the page.
Validation:turning off the stylesheet all pages are visible
requirement 5
Terms: Avoid flashing objects and written or moving whose frequency is likely to cause photosensitive epileptic disorders or impaired concentration, or may cause malfunction of assistive technologies, where information needs require their use, however, warn the user of possible risk before presenting them and provide methods of preventing these elements.
Validation: there are no objects and scripts used flashing or moving
requirement 6
Statement: Ensure that the information content can be clearly distinguished (foreground) and background (background), by providing sufficient contrast (in the case of text) or different sound levels (in the case of speech with background music); avoid presenting texts the form of images, if not possible, use the same criteria mentioned above.
Validation: the contrast meets the characteristics of the utterance
requirement 7
Statement: Use image maps of client-side rather than server side, except in the case where the sensitive areas can not be defined with a predefined geometric shapes of the DTD in use.
Validation: if you use a server side map shows also the map on the client side in order to obtain the same information
requirement 8
Terms: If you use server-side image maps, provide alternative text links to get all the necessary information or services through interaction with the map.
Validation: if you use a server side map shows also the map on the client side in order to obtain the same information
requirement 9
Terms: For tables use the data elements (tags) and attributes provided by the DTD to describe the contents and identify the headers of rows and columns.
Validation: validated with the W3C Validator
requirement 10
Terms: For tables use the data elements (tags) and attributes provided in the DTD used to associate data cells and header cells that have two or more logical levels of row or column header.
Validation: validated with the W3C Validator
requirement 11
Statement: Use style sheets to control content presentation and page layout so that they can also be read when style sheets are disabled or not supported.
Validation: are used style sheets and turning them off the site is perfectly readable
requirement 12
Terms:The presentation and text content of a page must be adapted to fit the window of the user interface without any overlapping of objects or loss of information that make the content unintelligible, even when resizing, increasing or reducing the view or characters from the default values of these parameters.
Validation: the site has been tested for cross-browser and screen size
requirement 13
Terms: If you use tables for layout, ensure that the contents of the table can be understood even when it is linearized and use elements and attributes of a table while respecting the value defined in the specification of semantic markup language used.
Validation: respected
requirement 14
Terms:In forms (form), associate labels explicitly with their controls, positioning them so that both facilitated the compilation of tennis for people using assistive technologies.
Validation: respected
requirement 15
Statement: Ensure that pages are usable when scripts, applets, or other programmatic objects are disabled or not supported, if this is not possible to provide a textual explanation of the functionality and provide a text equivalent, in a similar manner as described in No requirement 3.
Validation: respected
requirement 16
Statement: Ensure that the event handlers that trigger scripts, applets or other programmatic objects or have its own interface, independent of a specific input device.
Validation: respected
requirement 17
Terms:Ensure that functionality and the information conveyed by means of programming objects, objects that use technologies not defined by formal published grammars, scripts and applets directly accessible.
Validation: respected
requirement 18
Statement: If a movie or a multimedia presentation are indispensable to the information given or the service, provide a text equivalent, which is synchronized in the form of sub-titling or auditory description, or provide a summary or a simple label for each video and multimedia element taking into account the level of importance and difficulty of implementation in the case of transmissions in real time.
Validation: respected
requirement 19
Terms:Clearly identify the destination of the hyperlink (link) with text that is meaningful even when read out of context, or associate connected to the alternative texts that have similar characteristics explanatory, and provide mechanisms that allow users to skip repetitive navigation links found on most pages.
Validation: respected
requirement 20
Statement: In the event that the use of the service provided in a page there is a range of time within which to perform certain actions, you must explicitly warn the user, indicating the maximum time allowed and the alternatives to use the service.
Validation: respected
requirement 21
Terms: Make selected and activated via keyboard commands or keyboard emulation technology or through pointing device other than the mouse links on a page;to facilitate the selection and activation of links on a page you must ensure that the vertical distance of lists of links and the horizontal spacing between consecutive links are 0.5 m, the horizontal and vertical distances between buttons on a form is at least 0.5 m and that the size of the buttons on a form are such that the label clearly visible in them.
Validation: respected
requirement 22
Statement: the pages of existing sites that can not meet the requirements listed above (pages accessed) in the first application, provide a link to a page that complies with these requirements, with detailed information and functionality equivalent to those of the page and not accessible updated with the same frequency, avoiding the creation of text-only pages, the link to the compliant must be presented clearly to the top of the page is not accessible.
Validation: All the pages follow the requirements