Information on access to ENAV website
ENAV has produced its own website (http://www.enav.it) in compliance with the 22 requirements of the “Stanca Law” (Law N. 4 of 9 January 2004) issued in Ministry Decree of 8 July 2005 published in Official Gazette G.U. 8 August 2005 N.183.
There follows the final report on the technical assessment conducted.
|1||Production of pages and objects on these pages with technology defined by formal published grammars, utilising the most recent versions available when these are supported by the user programs. Use of elements and attributions in compliance with the specifications, respecting the semantic aspect||yes|
|2||The use of frames is not allowed in the creation of new websites..||n/a|
|3||Provide an alternative text equivalent for every non-text object on a page, and ensure that when the non-text content of an object changes dynamically, that the equivalent contents provided are also changed. The equivalent text alternative of a non-text object must be suited to the function provided by the original object in the specific context.||yes|
|4||Ensure that all the information elements and functions are also available in the absence of the particular colour used to display them on the page.||yes|
|5||Avoid any flashing or moving objects and text having a flash frequency which might trigger disturbances related to photosensitive epilepsy, disturbances in concentration, or which may cause the malfunctioning of the supporting technology utilised. Should information requirements in any case make their use necessary, users must be warned of the possible risk before the objects are displayed, with methods being made available to avoid such elements.||yes|
|6||Ensure that the information contents (foreground) and the background are always distinguishable, with the use of sufficient contrast (in the case of text) or different sound levels(in case of speech with background music). Text in the image form should generally be avoided, but if indispensible, it must be produced with the same criteria of distinction stated above.||yes|
Use, client side rather than server side image sensitive maps, except when the sensitive zones cannot be defined in one of the default geometrical forms shown in the DTD adopted.
|8||If server side map images are used, supply the alternative text links necessary for obtaining all the information or services available by interacting directly with the map||n/a|
For the data tables, use elements (markers) and the attributes contained in the DTD adopted to describe the contents and identify the headings of lines and columns.
|10||For the data tables, use elements (markers) and the attributes contained in the DTD adopted to associate the data cells and the heading cells having two or more logic levels of heading for lines or columns.||yes|
|11||Use style sheets to check the presentation of contents and organise the pages in such a way that they can also be read when the style sheets are disenabled or not supported.||yes|
|12||The presentation and the text contents of a page must be designed to adapt to the window size of the browser utilised by the user without any overlapping of the objects or loss of information that would make the contents incomprehensible, even in case of resizing, enlargement or reduction of the display area and/or of the characters with respect to the default values of these parameters.||yes|
|13||If the tables are used for layout purposes: ensure that the contents of the table are also comprehensible when it is read in linear form, using the elements and attributes of a table in compliance with the semantic value defined in the specifications of the marker language utilised.||n/a|
|14||In the forms, explicitly associate labels and their controls, positioning them in such a way to ensure use by those utilising supporting technology for filling in the fields.||yes|
|15||Ensure that the pages are usable when scripts, applets or other program objects are disenabled or not supported.||yes|
|16||Ensure that event managers activating scripts, applets or other programming objects or which have their own specific interface, are independent from a specific input device.||yes|
|17||Ensure that the functions and information conveyed by programming objects, objects using technology not defined in the formal published grammars, scripts and applets are directly accessible.||yes|
|18||If a film or multimedia presentation is indispensible for completeness of the information or service provided, provide a synchronized equivalent text alternative in the form of subtitles and/or voice description, or provide a summary simple label for each video or multimedia element, taking into account the level of importance and the difficulties of implementation in the case of real time displays.||yes|
|19||Ensure clarity in the destination each link with significant texts even if read independently from the context or associated with alternative links having similar explanatory value. Provide mechanisms for avoiding the repetitive reading of sequences of links common to several pages.||yes|
|20||If there is a default time by which certain actions must be taken by the user in order to utilise the service provided by a page, the user must be explicitly informed with indication of the maximum possible time and providing eventual alternatives for utilising the service.||n/a|
|21||The links on a page must be designed for selection and activation via keyboard, keyboard emulation technology or selection systems other then the mouse.||yes|
|22||At the time of initial application, for existing websites, for any page that does not comply with these requirements must be provided with a link to a page complying with them, containing equivalent information and functions and updated at the same rate as the original page, avoiding the creation of pages with text only. The link to the accessible page must be shown clearly at the start of the non-accessible page.||n/a|