Accessibility
Objectives of this website
This site was created with the aim of fulfilling all the requirements of the Technical Verification of Law 4/2004 (the "Stanca" law).
The following are 22 of the Technical Verification control points, specifying the means by which they were soddifatti accessibility requirements and verification techniques adopted.
Go to the Technical Control page on accessibility published (Annex A).
List of the requirements and related compliance
requirement 1
Statement: create pages and objects thereon using technology defined by formal grammars published in the most recent versions available when supported by user programs. Use elements and attributes in accordance with the specifications, respecting the semantic aspect. In particular, the markers languages HTML (HypertText Markup Language) and XHTML (eXtensible HyperText Markup Language):
for all new sites, use at least version 4.01 of HTML or version 1.0 of XHTML, in any case, with Strict DTD (Document Type Definition - Definition of the Strict type of document) type;
for existing sites, in the first application, if you can not comply with point a) the use of the language version, shown above with Transitional DTD, but with the following caveats:
avoid using, within the markup language in which the page is coded, elements and attributes to define the presentation features of the page (for example, characteristics of the text, text colors and background, etc. ), using instead CSS style sheets (Cascading Style Sheets) to achieve the same visual effect;
avoid generating new windows; Where this is not possible, explicitly warn the user of the change of focus;
plan to switch the entire site to the Strict DTD version of the language used, informing the Prime Minister's Office - Department for Innovation and Technology, and the National Centre for Computing in Public Administration.
Method for achieving the: the site is made through the web platform Futura Web Platform, which automatically generates XHTML 1.0 Strict pages.
Test technique: all the pages have been validated with the W3C Validator.
requirement 2
Statement: it is not allowed to use frames in the creation of new sites. In the first application, for existing Web sites with frames it is allowed to use HTML 4.01 or XHTML 1.0 with frameset DTD, but with the following caveats:
avoid using, within the markup language in which the page is coded, elements and attributes to define the presentation features of the page (for example, characteristics of the text, text colors and background, etc. ), using instead CSS style sheets (Cascading Style Sheets) to achieve the same visual effect;
making sure that every frame has a meaningful title to facilitate identification and navigation; if necessary, also describe the purpose of the frames and their relationship;
plan the transition to XHTML, at least version 1.0 with Strict DTD entire site, informing the Presidency of the Council of Ministers - the Prime Minister's Office - Department for Innovation and Technology, and the National Centre for Computing in Public Administration.
Method for achieving the: with Futura Web Platform Web Platform you can not carry over Frame based sites: the result is that each site based on Futura Web Platform Web Platform responds to the requirement 2.
requirement 3
Statement: provide a text equivalent for every non-text object on a screen and to ensure that when non-text content of an object dynamically changes are also updated its equivalents; the text equivalent of a non-text object must be proportionate to the function performed by the object in the specific context.
Method for achieving the: with the web platform Futura Web Platform you can not carry on frame-based sites: the result is that each site based on Futura Web Platform Web Platform responds to the requirement 2.
requirement 4
Statement: ensure that all the information and all functions are available even in the absence of the particular color used to present the page.
Method for achieving the: Futura Web Platform through the web pages of the platform elements are customized both in terms of graphics that code; for example, in the current page navigation menu it is identified both with a different color, both with the use of the tag "STRONG" in place of "A" tag. In addition the site authors have avoided phrases like "watching the red / click on the blue box" button, because they would be meaningless for the blind and persons with disabilities in color perception.
Test technique: sample examination of the site pages.
requirement 5
Statement: Avoid objects or text blinking or moving whose frequency might cause photosensitive epilepsy or concentration disorders, or can cause the malfunctioning of assistive technologies; if informative requirements require their use, alert the user to the risk before presenting them and provide methods that allow to avoid such objects.
Method for achieving the: has been taught to the authors of content to avoid moving images and Flash animations unless absolutely necessary and never "flashing."
Test technique: sample examination of the site pages.
requirement 6
Terms: Ensure that can be clearly distinguished the information content (foreground) and the background (background), using sufficient contrast (in the case of text) or different sound levels (in the case of speech with background music); Avoid presenting text as images; if not possible, apply the same criteria mentioned above.
Methodology of achievement of 'objective: In this site the appearance of pictures and objects that compose them (titles, paragraphs, etc.) is centrally defined through CSS. In this way, while allowing maximum flexibility of layout, make sure the graphic consistency of the whole site.
Test technique: the graphics used on this website has been verified by applying the W3C color contrast formula through the CSSJuicyStudio validation tool. We were also conducted random checks on some pages of the site.
requirement 7
Terms: Use sensitive image maps on the client side rather than server side, except in the case where sensitive regions can not be defined with one of the predefined geometric forms indicated in the DTD.
Method for achieving the: image maps can only be submitted by the site owners and not by users with Futura Web Platform. This site administrators have chosen not to use image maps, so requisite 7 does not apply.
requirement 8
Statement: in case of using server side image maps, provide alternative text links needed to obtain all the information or services by directly incorporating the map.
Method for achieving the: image maps can only be submitted by the site owners and not by users with Futura Web Platform. This site administrators have chosen not to use image maps, so requisite 8 does not apply.
requirement 9
Instruction: for data tables use the elements (markers) and attributes provided by the DTD in use to describe content and identify row and column headers.
Method for achieving the: the editor of Futura Web Platform supports data tables at a logical level (X rows by Y columns) and allows you to specify the row and / or column automatically generating tags "TH" instead of "TD" tags for header cells. For each data table, you can specify the summary ( "SUMMARY" attribute). E 'can be imported with a single copying and pasting entire data tables from Word, Excel, WordPerfect or other Office Automation Software: Futura Web Platform recognizes the number of rows and columns and paste cell values by removing any formatting attributes so as to format the data for the sole use of centralized CSS.
Test technique: Validation of the code of all the pages with the W3C pages and sample examination of some pages containing tables.
requirement 10
Instruction: for data tables use the elements (markers) and attributes provided by the DTD in use to associate data cells and header cells that have two or more logical levels of row or column headers.
Method for achieving the: the editor of Futura Web Platform does not support tables having more than one logic level. If it is indispensable to use them you can import pages or portions of XHTML pages containing tables accessible to more logical levels. This site has chosen not to use tables to more logical levels.
Test technique: Validation of the code of all the pages with the W3C pages and sample examination of some pages containing tables.
requirement 11
Instruction: use style sheets to control content presentation and page layout so they can be read even when the style sheets are disabled or not supported.
Method for achieving the: layout of this site is done using style sheets and without the use of tables. With Futura Web Platform general frames, always made in XHTML 1.0 Strict, can be paged CSS, or tables. The content of the page, directly generated by the engine Futura Web Platform, is always free of layout tables.
Futura Web Platform always uses the most appropriate tags for each situation: "H1" for titles, "H2" for subtitles, "P" for paragraphs, "OL" for lists, "STRONG / EM" for lgli effects bold / italic text: in this way, even disabling the pages of style sheets can be read without problems and retain in full the information and logical-structural content.
Test technique: Validation of the code of all the pages with the W3C pages and sample examination of some pages using laAccessibility Toolbar to disable style sheets.
requirement 12
Proposition: the layout and text content of a page must be adaptable to the size of the browser window used by the user without any overlapping of objects or loss of information which might make comprehension difficult, even in the case of resizing, enlargement or reduction of ' display area or characters from the default values of these parameters.
Method for achieving the: the pages of this site are adapted to different resolutions (liquid layout) and all texts can be enlarged or reduced with the browser commands. Whole impainazione is based on CSS. Futura Web Platform is able to recognize the browser that connects to the site and to serve CSS portions differentiated for each one, in order to compensate for any defects in pagination related to individual programs: unlike CSS Hack techniques (such as the famous " Tantek Çelik hack ") used in static sites, each line of CSS served by Futura Web Platform complies with the specifications and perfectly valid.
Test technique: a sample survey of over through browser pages (in the test group are Internet Explorer 5, 5.5, 6, 7, FireFox 1.5 and 2; Mozilla 1.7, Netscape 8.1, Opera 8.5 and 9, Safari and Firefox 1.5 and 2 for Mac OS X Tiger; FireFox 1.5 and 2 for Linux), video resolutions (800 by 600 pixels and up) and different character sizes (from Internet Explorer 6 "normal" to "very large").
requirement 13
Statement: In the case of using tables for layout purposes, ensure that the content of the table is also comprehensible when linearized and use the elements and attributes of a table respect the semantic value defined in the specification of the markup language used.
Method for achieving the: Futura Web Platform with the general frames of the pages can be realized with tables or CSS. The content of the pages, generated by the engine Futura Web Platform, is always free of layout tables. This site has decided not to use layout tables.
Test technique: Sample test of the pages through the Lynx text browser and through the JAWS screen reader.
requirement 14
Proposition: the forms (form), explicitly associate labels with their controls, positioning them so as to facilitate compilation of fields by those who use the technologies "assistive".
Method for achieving the: is possible to realize also very complex forms without the need to know any programming language. Visual editor of Futura Web Platform put the basic objects of the form (such as text fields, dropdown menu, etc.) and being Futura Web publishing platform automatically generates the code, properly associating labels to each form field.
Test technique: the form of the compilation with mouse and keyboard, with the Lynx text browser and the JAWS screen reader.
requirement 15
Proposition: to ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported; where that is not possible to provide a textual explanation of the functionality and provide an equivalent textual alternative, in a similar way as indicated in Requirement 3.
Method for achieving the: based sites Futura Web Platform work without the use of Java or Flash as all interactive functions use server-side code.
They may be used only two JavaScript optional. The first is used in case you want to insert the default values of form fields (as required by the WCAG 1.0 point to 10.4) in order to remove the default values when you enter the field.
If Javascript is not supported, you should simply delete the defaults manually.
The second script is used to open links in new windows, circumventing the limitation of the language XHTML 1.0 Strict, which abolished the "TARGET" attribute.
In this case, if the author of the contents choose to open the destination of the link in a new window, JavaScript provides to alert the user, appending the warning to "TITLE" field of the link (as required by WCAG 1.0 to the point 10.1).
If Javascript is not supported, the link does not open in a new window and you do not queue the alert.
Test technique: Also disabiltando missing JavaScript features are absolutely marginal and do not affect the use of the site, so that you do not have any alternative text.
requirement 16
Proposition: to ensure that managers of events that activate scripts, applets or other programming objects or possessing its own interface, independent of a specific input device.
Method for achieving the: as explained in point (Requirement 15) the only two scripts used on the site have been verified with the main browsers and the main assistive technologies.
Test technique: gerifica the script with mouse and keyboard with browsers (Explorer, Mozilla, Opera, Netscape, Safari, Lynx) and the JAWS screen reader.
requirement 17
Statement: ensuring that functionality and the information conveyed by programming objects, objects that use technologies not defined by formal published grammars, scripts and applets directly accessible.
Method for achieving the: as already explained in paragraph (Requirement 15) the only two scripts used by Futura Web Platform were also verified with assistive technologies. In any case, you can disable these scripts without loss of functionality.
Verification technique: inspection of the sample pages using scripts.
requirement 18
Statement: if a movie or multimedia presentations are indispensable for the completeness of the information or service, provide a text equivalent, synchronized in the form of sub-titles or descriptions, or provide a summary or simple label for each video or multimedia elements, taking into account the level of importance and difficulty of implementation in the case of real time transmissions.
Method for achieving the: slide-media objects provide an extended text field where you can enter the description of the media themselves, also the authors of the contents have been trained to the inclusion of explanatory and coherent descriptions.
Verification technique: using a new analytical tool offered by Futura Web Platform were examined, through a single summary report, all media content to verify the significance of the associated textual descriptions.
requirement 19
Statement: make clear the destination of the hyperlink (link) with meaningful texts even if read out of context, or associate alternative texts to the links that in turn explain the works and providing mechanisms to avoid the repeated reading of sequences of links common multipage.
Method for achieving the: to avoid reading of repetitive sequences of links have been included in the general frames suitable jump links to content (skip links).
For creating meaningful links if read out of context it has been appropriately authors content format.
Are some hotkeys also been used ( "ACCESSKEY"), tested with major browsers, in order to avoid overlapping with the keyboard commands of the same browser.
Test technique: through Bobby Validation Software 5.0 (on the net today replaced by his successor WebXact) we verified the hyperlinks.
The jump link (skip links) were tested on sample through the JAWS screen reader.
The significance of the link outside the context has been verified through a new analytical tool offered by Futura Web Platform that brings, through a single summary report, all the input links on each page.
requirement 20
Statement: in the event that for the use of the service provided in a predefined time interval is provided within which to perform certain actions, you need to explicitly warn the user, indicating the maximum permitted time and alternatives to use the same service.
Method for achieving the: Futura Web Platform includes no time limit functions. If you integrate into a site based on Futura Web Platform applications requiring a certain amount of time for the performance of certain actions the leaders of the integration should take care to include an appropriate notice. In this website there is no time limit functions.
requirement 21
Statement: make selected and activated through keyboard commands or keyboard emulation technology or pointer systems other than through the mouse the links on a page; to facilitate the selection and activation of links on a page, you need to ensure that the vertical distance of lists of links and the horizontal spacing between consecutive links is at least 0.5 em, the horizontal and vertical distances between buttons on a form is at least 0.5 em and that the size of the buttons in a form are such as to make clearly visible the label contained therein.
Method for achieving the: all generated links, whether internal link to the content of each page or links pertaining to navigation indexes are perfectly selected with each device, including the keyboard or keyboard emulation technology. The site, in fact, are not used Javascript, Java or Flash to manage links and menus, and so every link is in pure XHTML.
The spacing and positioning of links, buttons and form fields is defined centrally through cascading style sheets, making it easy to achieve the requirements dictated in the second part of the point.
Test technique: Sample test pages of the site through devices other than the mouse, control of the link sequences and form to the verification of the spacing and sizing of the objects.
requirement 22
Instruction: for the pages of existing sites that can not meet the requirements listed above (non-accessible pages), in the first application, providing the link to a page complies with these requirements, providing information and equivalent functionality to that of the non-accessible page and updated with the same frequency, avoiding the creation of text-only pages; connecting to the compliant page must be clearly displayed at the non-accessible page.
Method for achieving the: the site complies with all clauses of this Technical Control and is therefore not necessary to create alternative versions of the same pages.
Help us to improve
In this case we apologize now and please report any irregularities or difficulties encountered at info@futurasys.com to enable us to eliminate it as soon as possible.