Dutch Accessibility Law

From ByteWiki

The following is a translation, via Babel of the Dutch Accessibility Law

Much of it didn't translate very well, but anyone with edit rights on this wiki shoudl feel free to fix it up if and when they can. Much of it can be easily edited where the meaning is obvious, but some words haven't translated very well, so care should be taken to not alter the original meaning too much.

..........

Contents

[edit]

Decision quality realm government Internet sites

The minister of internal matter and kingdom relations,

Considering the fact that the House of Commons at motion of the members Aasted-Madsen and Fierens dd 26 April 2006 (kamerstukken II 2005/06, 29,362, no.s. 88) the wish has pronounced, government Internet sites must which be accessibly for all citizens;

Considering the fact that it is desirable that the realm government for this accessibility dovetails for this the internationally developed directives as formulated by the international World Wide web consortium (W3C);

Considering the fact that for the practical application of these international directives the Dutch web directives have been developed;

Acting in conformity with the gevoelen of the council of ministers;

[edit]

Decision:

[edit]

Article 1

The minister who it contracts ensures that Internet sites of the realm government satisfy to the web directives, as determined in the appendix to this decision.

[edit]

Article 2

  1. This decision becomes effective on 1 September 2006.
  2. Existing Internet sites of the realm government satisfy at the latest 31 December 2010 to the web directives.

This regulation will be placed with the explanation in the Dutch Government Gazette.

The minister of internal matter and kingdom relations,

[edit]

Appendix to the decision quality realm government Internet sites

[edit]

web directives


Directive Description
R-pd.1.1 Keep structure and design separated as much as possible: use HTML or XHTML for the structure of the site and CSS for the design of it.
R-pd.1.2 Construct Internet sites according to the principle of progressive enhancement.
R-pd.1.3 Make the function of the Internet site not dependent on optional technology, such as CSS and client-side script: optional technology must enhance the information on the site and complement the use of it and not obstruct access when this technology is not supported.
R-pd.2.1 Use HTML 4.01 or XHTML 1.0 according to the W3C specifications for the markup of government Internet sites.
R-pd.2.2 Do not use markup which has been marked as deprecated in the W3C specifications (retrieved).
R-pd.2.3 When adapting an existing Internet site: use only the Transitional variant of HTML 4.01 or XHTML 1.0 if the use of strict the alternative is impossible or undesirable.
R-pd.2.4 On the construction of a new Internet site: use of HTML 4.01 or XHTML 1.0 strict the alternative.
R-pd.2.5 Use no frames on government Internet sites. For this reason also do not use the Frameset variant of HTML 4.01 or XHTML 1.0.
R-pd.2.6 Use CSS Level-2.1 according to W3C the specification for formatting government Internet sites.
R-pd.2.7 If client-side scripts are used, use ECMAScript according to the specification.
R-pd.2.8 If one manipulates elements in the HTML hierarchy, use the W3C DOM according to the specification.
R-pd.2.9 Construct Internet sites according to the web content Accessibility guidelines (WCAG 1.0) of W3C.
R-pd.3.1 Write both grammatically correct and descriptive markup.
R-pd.3.2 Use markup for header rules which express the hierarchy of the information on the page.
R-pd.3.3 Lettuce in the markup no levels in the hierarchy of head rules.
R-pd.3.4 Use the P ( paragraph) element for indicating paragraphs. Do not use the br (linebreak) element for separating paragraphs.
R-pd.3.5 Use the em (emphasis) and strong element for indicating emphasis.
R-pd.3.6 Use the abbr (abbreviation) element for abbreviations if obscurity could arise concerning the meaning of it, when the abbreviations play a very important role in the text, or when the abbreviations do not occur in the Dutch dictionary.
R-pd.3.7 Use the dfn (definition) element for indicating terms, elsewhere defined in a definition list.
R-pd.3.8 Use the ins (insertion) and del (deletion) element for indicating regular modifications in the contents of a page.
R-pd.3.9 Avoid the use of the sup (super script) and under (subscript) element wherever possible.
R-pd.3.10 Use the cite element for references to persons and titles.
R-pd.3.11 Avoid the use of q ( quotation) element.
R-pd.3.12 Use the blockquote element for indicating (long) citations.
R-pd.3.13 Use ol (ordered list) and ul (unordered list) elements for indicating lists.
R-pd.3.14 Use the dl (definition list), the dt (definition term) and dd (definition data) element for indicating a list with definitions.
R-pd.3.15 Give meaningful names to id and class attributes.
R-pd.4.1 Produce unique, onveranderende(?) URLs
R-pd.4.2 Dynamically generated URL’s must refer s still to the same contents such as contents it is modified or it is added.
R-pd.4.3 Avoid the use of sessions in URLs.
R-pd.4.4 Care for doorverwijzing to the new location at moving information.
R-pd.4.5 Automatic doorverwijzing must, if possible, be carried out by the server.
R-pd.4.6 Use pleasant URLs, which is readable and recognizable.
R-pd.4.7 Readable, uitbreidbare directory set-up- structure.
R-pd.5.1 In the event that important information is offered by means of a closed standard, one must offer the same information also by means of an open standard.
R-pd.6.1 Each HTML or XHTML document must start with a valid doctype claim.
R-pd.6.2 The contents of the page in the HTML put source code on order of belangrijkheid.
R-pd.7.1 Alt (alternative) attribute must be used on every img (image) and area element and must become to provide with an effective alternative text.
R-pd.7.2 Do not use the Alt attribute for calling tool tips.
R-pd.7.3 Use none d-links on government Internet sites. The use of the longdesc (long description) attribute deserves the preference when the alternative text on alto attribute is inadequate for the term of the information in the image.
R-pd.7.4 Images which stand have placed within a link niet-lege an alternative text have visitors who do not see the image able put the link to follow.
R-pd.7.5 To maps for both the img by means of alto attribute at the use of image an effective alternative text indicates element and every area element.
R-pd.7.6 Decorative images must as much as possible CSS being placed. Informative images must HTML being placed.
R-pd.7.7 The use of CSS Image Replacement techniques which are applied on essential information is dissuaded.
R-pd.8.1 Do not describe the mechanism behind following a link.
R-pd.8.2 Write clear, descriptive text for left.
R-pd.8.3 Use minimum to text that necessary is understand where the risky naartoe lead.
R-pd.8.4 Give for unpleasant surprises for the visitor sufficient information on the destination of a link to prevent.
R-pd.8.5 At the use of client-side script in combination with a link: the script functionality makes a extension on the basis functionality of the link.
R-pd.8.6 At the use of client-side script in combination with a link: if the link leads nowhere naartoe, do not face the visitor without support for client-side script then with a nonworking link.
R-pd.8.7 At the use of client-side script in combination with a link: if necessary, use client-side script as a extension on server-side functions.
R-pd.8.8 Left must clearly distinguished to be of other text.
R-pd.8.9 Provide in a logical order with left on the page. The tabindex use attribute to deviate when from the standard tabvolgorde from left this order is not sufficient for correct use of the page by keyboard users.
R-pd.8.10 Make the tabben to left not impossible. The focus does not remove rectangle around a link or the possibility for focus on a link.
R-pd.8.11 The accesskey spare attribute. As nevertheless private this attribute, apply use it becomes left only on which by the complete site unchanged remains (for example head navigation) and restricts the sneltoetscombinaties to numbers.
R-pd.8.12 Blind person gives visitors extra possibilities long of skipping lists with left.
R-pd.8.13 Give on top of pages with many subjects a page index with left to navigate to the different subjects.
R-pd.8.14 Left on government Internet sites do not have warning automatically new windows opening.
R-pd.8.15 Open no automatic new windows, except when the location of the risky helpful information contains that necessary can be during important, not interrupt process.
R-pd.8.16 Left to e-mail addresses: e-mail address to which is it to send bulletin in a targeted way must be visible in the link text.
R-pd.8.17 Left to e-mail addresses: the URL in the href attribute of a link to a e-mail address, can only contain the mailto protocol and a e-mail address.
R-pd.8.18 Just no technical measures on the Internet site to veil robots a e-mail address for spam.
R-pd.8.19 Extremely careful for with publishing e-mail addresses of visitors of the Internet site go. Inform the visitor concerning which data are published on the site, or publish e-mail address of the visitor.
R-pd.8.20 At offering downloadbare files, inform the visitor concerning how these to download and vervolgens to use.
R-pd.8.21 Files with the correct MIME serve type.
R-pd.8.22 Open left towards downloadbare files not in an automatically new window.
R-pd.8.23 Downloadbare files do not serve on purpose unknown or an incorrectly MIME type to force the browser to a certain behaviour.
R-pd.9.1 CSS must be placed in gelinkte files and to be mixed with the HTML source code.
R-pd.9.2 Pages must usefully remain when CSS are not supported bya web browser.
R-pd.10.1 Care that communicative elements their meaning transmits not exclusively colour.
R-pd.10.2 Indicated consistently with kleurgebruik at giving meaning.
R-pd.10.3 Care for sufficient clarity contrast between text - and context colour.
R-pd.11.1 Use tables for reflecting relational information and not for layout.
R-pd.11.2 Use the th (table header) element for describing a column or file in a table with relational information.
R-pd.11.3 Only range with th ( tableheader)warrants with the thead (tablehead)group element. The rest of the table with the tbody (tablebody)groups element.
R-pd.11.4 Use the scope attribute for associating table labels (th warrants) with columns or ranging.
R-pd.11.5 Header and id use element for associating table labels (th warrants) with individual warrants in complex tables.
R-pd.11.6 By means of the abbr (abbreviation) attribute gives to abbreviations for table labels (thwarrants) when the length of the contents of the table label is as such of length that recurrence in a speechcan browser awake irritation.
R-pd.11.7 Use the caption element or heading markup for giving a head text above a table.
R-pd.11.8 At adapting an existing Internet site: use CSS for the presentation and layout of web pages and to abandon tables for layout.
R-pd.11.9 At the use of tables for layout: use no longer than one table and use as many CSS as possible for the design of this table.
R-pd.11.10 At the use of tables for layout: just no accessibilitiesmarkup .
R-pd.12.1 Use no frames on government Internet sites. This applies to both regular frames within framesets, and so-called iframes.
R-pd.13.1 The label uses element to associate text explicitly with an import field in a form.
R-pd.13.2 The tabindex use attribute to deviate when from the standard orderorder order on form fields this order is not sufficient for correct use of the form by keyboard users.
R-pd.13.3 Grouping of import fields introduces by means of the fieldset element.
R-pd.13.4 Avoid automatic doorverwijzing at interaction with forms.
R-pd.13.5 Use no client-side script or forms as the only manner to reach information on the site.
R-pd.13.6 A visitor does not face with onwerkzaam a form if optional technologies - as CSS or client-side script - are not supported by the browser.
R-pd.13.7 Indicated distant with the use of CSS for import fields and form buds.
R-pd.13.8 As a visitor must personal give details, late these then know what with those data will be done, for example in the form of a privacydeclaration.
R-pd.13.9 No longer demand of a visitor by means of a form information up to give than necessary it is for the aim of the form. Keeps forms this way short possible and limit obliges fill in of form fields.
R-pd.13.10 Indicate which fields oblige if optional is fill in.
R-pd.13.11 Provide for alternative opportunities for contact, such as address data, phone numbers or e mailadressen, if these are available.
R-pd.13.12 The visitor lets know what with the form after sending it will be done there.
R-pd.13.13 The visitor gives the possibility for filing of its response.
R-pd.13.14 Wheel the visitor after filling in and sending a form an affirmative that its bulletin has arrived at the recipient (autoreply).
R-pd.13.15 Preceding complex forms the visitor gives an impression of how the form is.
R-pd.13.16 Vantevoren, call documents which the visitor (possibly) has necessary at filling in the form.
R-pd.13.17 Forms provide with instructions for the visitor where necessary, particularly at the import fields where they matter.
R-pd.13.18 Joint no convalescence (reset) buds to a form.
R-pd.14.1 Uses no client-side script for indispensable functionality on web pages, unless the lack of support for these script becomes sufficient afgevangen by HTML alternatives and/or server-side script.
R-pd.15.1 Making a language choice serves for the visitor possible be on every page in the site.
R-pd.15.2 Left for language choice must stand at a clear and consistent place in the navigation of the site.
R-pd.15.3 Use voluit written (textual) left towards the language alternatives.
R-pd.15.4 Write left to language alternatives in their corresponding language.
R-pd.15.5 Use no associations with nationalities for language choice.
R-pd.15.6 Specify the basis language of a page in the markup.
R-pd.15.7 Indicate in the markup taalvariaties in the contents of pages.
R-pd.16.1 Specify the karakterset for web pages.
R-pd.16.2 Specify UTF-8 the karakterset.
R-pd.16.3 The karakterset also specifies headers by means of HTTP, if possible.
R-pd.16.4 (At least) the meta for specifying the karakterset and place this element this way high possible in the head section of the markup uses element.
R-pd.18.1 Use for every page an unique, descriptive title.
R-pd.18.2 Writes short, concise text, in which the most important message on top of the page is already called.
R-pd.22.1 Use language which understands the visitor: limit the use of jargon, difficult terms and abbreviations.
R-pd.22.2 Visitors give a flight route: possibilities are able go further if they get bogged down. flight routes are among other things helpful left, can use of (back) the bud, zoekfunctie, or are possible immediate are able correct of import errors.
R-pd.22.3 Late visitors not Councils: give information on how they can gone wrong repair. Take into account much-made errors.
R-pd.22.4 Makes adapted foutpagina's - for errors as coming to an end left (404 Not Found) - on which the visitor possibilities gets passed its gone to continue within the site.
R-pd.22.5 At foutmelding as a result of sending a form, the visitor returns the possibility immediately wrong in the form repair and late him not dependent is of the use of (back) the bud.
R-pd.22.6 At the implementation of a search engine on the Internet site: use malignant zoektechnologie which take into account for example game errors, similar zoektermen, and terms in plural and enkelvoud.
R-pd.22.7 Give a synoptic list of the most relevant zoekresultaten. Too many zoekresultaten cost much time to visitors to find the desired information. Visitors give possibilities of establishing zoekcriteria, or of arranging zoekresultaten.
R-pd.22.8 Visitors give the possibility of reporting errors in the site.
R-pd.22.9 Use of colours, iconen and textual explanation to attract the attention of the visitor for foutmelding and the problem to comment.
R-pd.22.10 Visitors give possibilities of finding information in alternative manners. For example by giving sitemap, zoekfuncties, or by means of a request by e-mail, letter or tel..
Retrieved from "http://www.byteclub.net/wiki/Dutch_Accessibility_Law"