|
Policy on Accessibility of Web content
Introduction
This site has been designed in compliance with the recommendations in terms of accessibility provided by the Consortium for the World Wide Web (W3C) as part of the initiative for the accessibility of the Web (WAI), following the principle of universality. The reference document for making the site accessible, it was the recommendation of the W3C published May 5 1999 on guidelines for the content of the Web (WCAG 1.0).
In the assessment of the degree of accessibility of resources, as part of this site, have been used to support applications to validation, however, great attention was paid to the analytical assessment and manual by qualified personnel in the field, following the control points shown in WCAG 1.0.
As a result of the monitoring, the site was estimated to be conforming to the first level of accessibility (single A) according to WCAG 1.0
Accessibility statement
This site was developed in accordance with the principles of accessibility and in accordance with the Law 9 January 2004, n. 4 (commonly called "Legge Stanca", OJ No. 13 dated 17 January 2004) that pertain to the sites of Public Administration.
It also followed the recommendations for accessibility provided by the Consortium for the World Wide Web (W3C) as part of the initiative for the accessibility of the Web (WAI), following the principle of universality. The reference document for making the site accessible, it was the recommendation of the W3C published May 5 1999 on guidelines for the content of the Web (WCAG 1.0) and following the checklist listed in WCAG 1.0.
Here are the 22 technical requirements of accessibility required by CNIPA, specifying the manner in which they have been fulfilled and verification techniques adopted.
Despite the attention given to the implementation of the site and the many tests we can not exclude that one or more pages are inaccessible or become in the future for certain categories of users. Accessibility is a journey, not an end point.
Requirement 1
Making pages and content items or technologies defined by formal published grammars, using the most recent versions available when supported by user programs. Use elements and attributes in accordance with the specifications, respecting the semantic aspect.
Methodology for achieving the objective: the site is achieved through the CMS PAPublishing pages that automatically generates XHTML Strict.
Technical criteria: All pages have been validated with the W3C Validator (http://validator.w3.org).
Requirement 2
It is not permitted to use the frame in the creation of new sites.
Methodology for achieving the objective: The site does not contain frames and cms does not allow the use of frames.
Requirement 3
Provide an alternative text equivalent for every non-text object in a page and ensure that when the non-text content of an object changes are dynamically updated with the associated content equivalent set. The alternative text equivalent of a text should not be taken of the original function of the object in the specific context.
Methodology for achieving the objective: Every object has this image of a field text (ALT attribute). There are no media objects.
Technical verification through the software validation Cynthia Says - Web Content Accessibility Report We have verified the presence of ALT in the field all the images. The individual content authors have verified the correctness of logic descriptions entered. Cms requires the editors of the site to support the alternate text for each image published.
Requirement 4
Ensure that all the information and all features are available even in the absence of the particular color used to present the page.
Methodology for achieving the objective: This has been done because the lack of color affects the availability of features, for example all links (removed those menu) are formatted in blue and underlined.
Technical Audit: Examination of a sample page of the site.
Requirement 5
Avoid flashing objects and written or moving the frequencies which can cause intermittent noise from photosensitive epilepsy, poor concentration or that may cause the malfunction of the assistive technologies used. If information needs require their use, however, warn the user of the possible risk before you present them and provide ways of avoiding such things.
Methodology for achieving the objective: There are no items animated gif flashing it, the CMS does not allow the use of flash will the inclusion of animated gif by the editors.
Requirement 6
Ensure that they are always distinguished the information content (foreground) and background (background), using a sufficient contrast (in the case of text) or in different levels (if spoken with music). A text in the form of an image is to be avoided, but if you can not do without it, must be made with the same criteria of distinctness above.
Methodology for achieving the 'goal: In this site the appearance of pages and objects that make up (titles, paragraphs, etc..) Is defined in a centralized manner through the CSS. This will ensure consistency of the graphics site.
Technical criteria: The graphic used here was verified by applying the formula of the contrast of color through the W3C CSS Validation JuicyStudio (# http://www.juicystudio.com/services/csstest.asp contrast). Were also conducted spot checks on certain pages of the site.
Requirement 7
Use image maps sensitive side type of client rather than server side, except in cases where the sensitive areas can not be defined with a predefined geometric shapes shown in the DTD adopted.
Methodology for achieving the objective: The site does not contain maps and cms does not allow the use of maps.
Requirement 8
If we use server-side image maps, provide alternative text links needed to get all the information or services accessible directly interacting with the map.
Methodology for achieving the objective: The site does not contain maps and cms does not allow the use of maps.
Requirement 9
For tables using the data elements (markers) and attributes provided by the DTD used for describing the contents and identify the headers of rows and columns.
Methodology for achieving the objective: The site contains data tables to a logic level (N rows by M columns) and cells in the header row and / or column are specified by tag TH instead of TD tag. All the tables have relevant summary.
Technical criteria: Validation of the code of every page with the W3C validator, control of the entire site with the software Cynthia Says - Web Content Accessibility Report and review a sample of some of the pages containing tables.
Requirement 10
For tables using the data elements (markers) and the attributes provided in the DTD taken to associate data cells and header cells that have two or more logical levels of header rows or columns.
Methodology for achieving the objective: The site does not contain data tables having more than one logic level.
Requirement 11
Use style sheets to control presentation of content and organize them so that they can be read even when the style sheets are disabled or not supported.
Methodology for achieving the objective: The layout of this site is done through style sheets and without the use of tables. Furthermore, the xhtml code is constructed in a logical and always uses the most appropriate tag for each situation: in this way also disabling stylesheets pages can be read without problems and retain in full the information content and logical structure.
Technical criteria: Validation of the code of all pages with W3C CSS Validator.
Requirement 12
The presentation and content of a page of text should be adaptable to the size of the browser window used by you without overlapping of objects or loss of information that makes the content unintelligible, even in the event of downsizing, enlargement or reduction of the viewing and / or font than the default values of these parameters.
Methodology for achieving the objective: The pages of this site are adapted to the different resolutions and all texts can be larger or smaller with the commands of the browser.
Technical Audit: Examination of a sample more pages through browsers, screen sizes and dimensions of various characters.
Requisito13
If you use tables for layout purposes: [...]
Methodology for achieving the objective: The site does not contain tables for layout purposes.
Requirement 14
In forms (form), in explicitly associate labels with their controls, positioned so that for those who use assistive technologies for the development of the fields is facilitated.
Methodology for achieving the objective: All modules of the site are constructed by combining an explicit labels to their controls
Technical verification: Verification of completion of form with mouse and keyboard, with the Lynx text browser and the screen reader Jaws.
Requirement 15
Ensure that pages are usable when scripts, applets, or other programming objects are disabled or not supported.
Methodology to achieve the even disability JavaScript functionality missing are absolutely marginal and does not affect the usage of the site, so that you do not need any alternative text.
Requirement 16
Ensure that event handlers that trigger scripts, applets or other programming or who have their own specific interface, independent of a specific input device.
Methodology for achieving the objective: There are independent controls used by an input device, and each element has a specific interface can be managed in ways independent of the device.
Requirement 17
Ensure that the 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.
Methodology for achieving the objective: Using the keyboard occurred that the features and information are available, it was verified that the images are of equivalent alternative texts and using a screen-reader has verified the presence of non - visible.
Requirement 18
If a movie or a multimedia presentation are essential to the completeness of the information provided or the service provided, to prepare an alternative synchronized text equivalent in the form of sub-titling and / or voice description, or prepare a summary or a simple label to each video or multimedia element, taking into account the level of importance and difficulty of implementation in the case of presentations in real time.
Methodology for achieving the objective: there are no movies or multimedia presentations.
Requirement 19
Makes clear the target of each link (link) with significant texts even if read independently from their context or links associated with alternative texts that have similar characteristics explanatory. Provide for mechanisms to avoid reading the repetitive sequences of links common to multiple pages.
Methodology for achieving the objective: To prevent the reading of repetitive sequences of links has been included in the code a menu that allows the general to skip to page contents. To create meaningful links if read out of context have been trained the authors of content.
Technical criteria: attraversoil software validation Cynthia Says - Web Content Accessibility Report We have verified the hyperlinks. Also has been identified clearly the destination of each link, where these have not been held there has been clear whether the title clearly identifies the destination of links. The quick navigation menu has been tested on a random basis through the screen reader Jaws.
Requirement 20
If the usage of the service provided on a page is an interval of time within which to perform certain actions, you must explicitly warn the user, indicating the maximum time providing useful and possible alternatives in order to receive the service.
Methodology for achieving the objective: there are no features in time.
Requirement 21
The links in a page must be selected and activated via keyboard commands, technology or keyboard emulation by means of pointing other than a mouse.
Methodology for achieving the objective: All the links are generated, whether they are internal links to the content of any page or link within the navigation indexes are fully selectable by each device, including keyboard or technologies in the keyboard emulation. The site does not use javascript or flash for the management of links and menus, and then each link is pure xhtml. The spacing and positioning of links, buttons and fields of the form is defined in a centralized manner through CSS style sheets, to simplify the achievement of the requirements dictated in the second part of paragraph 21.
Technical criteria: Checking in sample pages of the site through devices other than mouse, control sequences to form links and for checking the spacing and sizing of objects.
Requirement 22
In the first application, for existing sites, in every page that can not be attributed to compliance with these requirements, providing a link to a page that respects, includes information and equivalent functionality and be updated with the same frequency of the original page avoiding the creation of pages of text only. The link to the page accessed must be brought clearly to the top is not accessible.
Methodology for achieving the objective: The site meets all the points of this verification technique and is not necessary to create alternate versions of the pages themselves.
Issued by the competent CNIPA
Compliance with standards
The pages of the site were conducted in accordance to the following standards and specifications of the W3C:
DTD XHTML 1.0 Strict
CSS (style definition of the attributes of the site)
Compliance be verified through the appropriate link located at the bottom (footer) of the site.
Navigation aids
In all the pages of the site, is present in the same position (above) the horizontal menu "You are in:" that indicates the user's location within the site structure and the title of the page where you are. The indication is hypertext, and with a simple click on the text of the navigation menu you can reach the levels above.
In the navigation menu vertical, the active layer appears in a different color so you can easily recognize.
Within articles is also available the "Print" button that opens a printable version of the page where are listed the essential elements of the document.
Access keys (access keys) * in preparation
To simplify the navigation of the page are included shortcut keys (AccessKey) which are run in native mode by the operator and CMS indices that allow you to quickly jump to navigation menu:
* [Alt + H] Home page
* [Alt + N] News
* [Alt + C] Contacts
* [H + S] Search Site
* [H + I] Site Map (index)
* [H + E] Events
* [Alt + F] FAQ (questions and answers)
* [M + H] Administration
* [H + A] Increase font FONT
* [Alt + D] Decrease font FONT
* [H + Z] contrast
* [H + X] Restore defaults
* [H + P] Main content of page (skip the navigation bar)
Texts
Were not used in the page markers to define the characteristics of the text or background but has used the CSS style sheets for graphic effects. In addition, the pages are organized so that they can be read even when the style sheets are disabled or not supported.
This site is not used frame and have been avoided or written flashing objects that may cause the merger or to assistive technology.
E 'stato encountered a sufficient color contrast between text and background and was found equal to a function in the absence of color used.
Using data tables were used to identify markers for the headers of rows and columns with tag TH instead of TD tag for the cell header. In the rare case of layout tables has been verified that the contents of the table is also understandable when read in a linearized.
Links (link)
All connections are made by recognizable textual elements as underlined or highlighted. Were also provided with a description of the destination of the connection through the attribute TITLE.
Images
For every non-text object has been given an alternative text (ALT attribute) commensurate with the original function of the object in the specific context.
Forms (form)
The online forms were constructed in an explicit way by associating labels with their controls, positioned so as to facilitate filling of fields who use assistive technologies.
Occur with different browsers (programs used to explore the resources of the Web)
The pages of this website have been verified with the following browsers:
Linux operating system - resolution 800 X 600 and 1024 X 768:
1.5.0.7 and Firefox 2
Konqueror 3.5.3
Opera 8.5.0
Macintosh operating system OSX 10.3 - 800 X 600 and 1024 X 768:
1.5.0.7 and Firefox 2
Opera - Safari
Windows 2000 Professional - Resolution 800 X 600 and 1024 X 768:
Explorer 5.0
Explorer 5.
Explorer 6.0
Explorer 7.0
1.5.0.9 and Firefox 2
Mozilla 1.6
Windows XP - 800 X 600 resolution and 1024 X 768:
Explorer 6.0
1.5.0.9 and Firefox 2
All texts can zoom in or out by using the appropriate feature of your browser or connection (A +, A-) posts in upper right * in preparation
In this site there are no features associated with intervals of time within which to perform certain actions.
Accessibility is becoming a
Accessibility is a process that continues over time. Making a site accessible means to work for its development and its improvement by removing the obstacles that are encountered along the way. For this reason, the Portal of Villa Monastero is constantly evolving in order to constantly improve accessibility.
The instruments used to check the formal correctness of the code of the website does not automatically guarantee the usability and accessbilità, so it is always necessary to control a human being.
Despite the attention given to the implementation of the site and the many tests you can not exclude with certainty that some pages are still without our knowledge inaccessible to some users. In this case we apologize right now and please report any irregularities found in order to enable us to eliminate it as soon as possible.
Write to signal errors of accessibility, in the "Contact" you will find the addresses to contact us.
|
