#18: Italian Government Accessibility Requirements

Contents

1. Definitions
2. Motivation
3. Assumptions
4. Proposal
5. Implementation
6. Deliverables
7. Risks
8. Progress log
9. Participants

Proposed by

TFF

Proposal type

User interface, Architecture, Login/Registration

Assigned to release

• draft2gether 1.0 (Unreleased)

State

being-discussed

Definitions

!!! - a "must have" feature

!! - a requested feature

! - a less desired feature

? - desired feature, but can be discussed for smaller changes

?? - a feature open for discussion

??? - a feature fully open for discussion in behaviour, ui, architecture...

CF - Criticality Factor. It is the multiplier number for each feature, to be used when calculating penalties on deliverables, in case of bugs or delivery missing. The higher, the most critical the feature is.

Motivation

Read the Accessibility Documentation provided by the Italian Goverment for further information.

Assumptions

Proposal

• Comply with The Stanca Act (read law text here) - ?? CF 3
  
• Pass "Technical Check", implementing all 22 technical requirements (see "Implementation" below) - ?? CF 3
• Pass "Subjective Check (part 1) and (part 2)", considering all subjective criterias specified in The Stanca Act (see "Implementation" below) - ?? CF 3
  

Implementation

Technical Requirements from "The Stanca Act"

Requirement 1
Statement: Build pages and objects contained in them using technologies defined by formal published grammars, using the most recent versions available when these are supported by user programs. Use elements and attributes in a way that conforms to the specifications and respects their semantic aspect.

More specifically, for HyperText Markup Language (HTML) and eXtensible HyperText Markup Language (XHTML):

• a) for all new Web sites, use at least version 4.01 of HTML or version 1.0 of XHTML, both with strict Document Type Definition (DTD);
• b) for existing Web sites, in the event that it should not possible to comply with point a) on initial application the version of the languages referred to above may be used with Transitional DTD with the following precautions:

• 1. avoid the use of elements and attributes to define the presentation features of the page (such as font, foreground and background colours, etc). Use Cascading Style Sheets (CSS) in their place;
• 2. avoid generating new windows; where this is not possible, alert users explicitly to the change of focus;
• 3. plan the transition of the entire site to the Strict DTD version of the language used. The transition plan must be submitted to the Prime Minister’s Office – Department for Innovation and Technologies.

Requirement 2
Statement: Frames are not allowed in the development of new Web sites. On first application, for existing Web sites already developed using frames, the use of HTML 4.01 or XHTML 1.0 with DTD frameset is allowed with the following precautions:

• avoid the use of elements and attributes to define presentational features of the page (such as font, foreground and background colours, etc). Use Cascading Style Sheets (CSS) in their place;
• ensure that each frame has a meaningful title to facilitate identification and navigation. If necessary, also describe the purpose of the frames and how they interact with each other;
• plan the transition of the entire Web site to XHTML at least in version 1.0 with Strict DTD. The transition plan must be submitted to the Prime Minister’s Office – Department for Innovation and Technologies.

Requirement 3
Statement: Provide a text equivalent for every non-text object on a page and ensure that when the non-text content of an object changes dynamically its equivalents are also updated. The text equivalent of a non-text object must be able to perform the function performed by the object in that specific context.

Requirement 4
Statement: Ensure that all the information and functionalities conveyed with colour are available also without colour.

Requirement 5
Statement: Avoid blinking or moving objects and scripts whose frequency might trigger photosensitive epileptic disturbances, difficulties with concentration or malfunctioning of assistive technologies. When these must be used for informational purposes, alert users to the risk and provide methods that allow to avoid such objects.

Requirement 6
Statement: Ensure that the foreground and background can be clearly distinguished by providing sufficient contrast in the case of text or different sound levels in the case of speech with musical background. Text in image form is generally not recommended but, if it cannot be avoided, it must be produced following the same criteria mentioned above.

Requirement 7
Statement: Use client-side rather than server-side image maps, except where sensitive regions cannot be defined with one of the valid geometric shape defined by the DTD in use.

Requirement 8
Statement: If server-side image maps are used, provide the alternative text links needed to obtain all the information or services that can be obtained through interaction with the map.

Requirement 9
Statement: Use elements (markup) and attributes provided by the DTD in use to describe content and identify row and column headers in data tables.

Requirement 10
Statement: Use elements (markup) provided by the DTD in use to associate data cells and header cells in data tables that have two or more logical levels of row or column headers.

Requirement 11
Statement: Use style-sheets to control content presentation and page layout to ensure readability even when the style-sheets are turned off or not supported.

Requirement 12
Statement: The layout and text content of a page must be adaptable to the user interface without any overlapping of objects or loss of information with consequent impaired comprehensibility, including in the case of resizing, increasing or reducing the display area and/or characters with respect to their default parameters.

Requirement 13
Statement: When tables are used for layout:

• ensure that they are comprehensible when linearized;
• when using the elements and attributes of tables respect the semantic value defined in the specifications of the markup language used.

Requirement 14
Statement: In forms, associate labels explicitly with their controls, positioning them in such a way as to facilitate field compilation and completion of the form by those using assistive technologies.

Requirement 15
Statement: Ensure that pages are usable when scripts, applets, or other programming objects are turned off or not supported. If this is not possible:

• provide an explanation of the functionality provided;
• provide a text equivalent as indicated in Requirement 3.

Requirement 16
Statement: For scripts, applets, and other programming objects or any element that has its own interface, ensure that event handlers are input device-independent.

Requirement 17
Statement:Ensure that functionality and the information conveyed by programming elements such as scripts and applets that use technologies not defined by formal published grammars are directly accessible or compatible with assistive technologies

Requirement 18
Statement: When films or multimedia presentations are indispensable to the information or service, provide an equivalent synchronised textual alternative in form of caption and/or auditory description. Otherwise provide a summary or a simple label for every video and multimedia element depending on the importance and production difficulties in the case of real-time presentations.

Requirement 19
Statement: Clearly identify the target of each link using text that is meaningful even when read out of context or associate alternative texts to the links that in turn explain the target. Provide mechanisms to enable users to skip repetitive navigation links found on more than one page.

Requirement 20
Statement: When a timed response is required to use a service delivered through a web page, the user should be alerted, informed of the maximum time available and given alternative methods where applicable to use the service.

Requirement 21
Statement: Ensure that links can be selected and activated through keyboard commands or keyboard emulation technology or pointer systems other than the mouse. To ease the selection and activation of links using these assistive technologies one must also ensure that:

• the vertical distance in lists of links and the horizontal spacing between consecutive links should be at least 1 em;
• the horizontal and vertical distances between buttons on a form should be at least 1 em;
• the buttons in a form should be big enough to ensure that their labels can be clearly read, for example by using the padding or margin between the label and the outline of the button;

Requirement 22
Statement: On first application, for existing sites, in any page that cannot be brought into line with the requirements, provide a link to a page that is compliant, contains equivalent information and functionalities, and is updated with the same frequency as the original page. The creation of text-only pages should be avoided. The link to the accessible page must be presented clearly as an option at the start of the non-accessible page.

Subjective Criterias from "The Stanca Act"

• perception: the information and commands required to perform the activity must be available and perceivable at all times;
• understandability: the information and commands required to perform activities must be easy to understand and use;
• operability: the information and commands should enable users to make immediate choices as to the best action to take to achieve the desired objective;
• consistency: the same symbols, messages and actions must have the same meaning throughout the environment;
• health and safety: indicates the features the environment must have to safeguard and promote users’ physical and psychological well-being;
• security: indicates the features the environment must have to ensure that transactions and data are reliable and handled with suitable levels of security and confidentiality;
• transparency: the environment must convey its status and the effects of the actions carried out. Users must be provided with the information needed to evaluate the dynamics of the environment correctly;
• learnability: indicates the features the environment must have to enable users to learn to use it quickly and with the least effort possible;
• help and documentation: help functions should be provided as online guidance and documentation concerning the functioning of the environment. The help information must be easy to find and focused on users’ tasks;
• error tolerance: the environment must prevent errors. If any errors do occur, appropriate messages must be provided that clearly indicate the problem and the actions needed to correct it;
• attractiveness: indicates the features the environment must have to attract and hold users’ interest;
• flexibility: the environment must take individual preferences and contexts into account.

Deliverables

Risks

Progress log

Participants