2.2 Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen.
According to the analysis by JuicyStudio Color Contrast Analyser tool for Mozilla Firefox http://juicystudio.com/article/colour-contrast-analyser-firefox-extension.php our layout colors fulfill this requirement. [
See results]
3.1 When an appropriate markup language exists, use markup rather than images to convey information.
We used no graphical information in the EPA interface. Graphical content in out database is only to convey exclusively visual information, in illustration snapshots of layouts.
3.2 Create documents that validate to published formal grammars.
Our pages are currently in phtml format. They do not yet validate agains the used "XHTML 1.0 Strict" syntax due to dymanic properties that were enabled in order to exclude non-accessible interactive options. Required modifications are underway.
3.3 Use style sheets to control layout and presentation.
We rely exclusively on style sheets in determining the layout of our site.
3.4 Use relative rather than absolute units in markup language attribute values and style sheet property values.
Only relative values are used for the layout properties of relevant content elements. Pixels are used for decorative elements that do not affect the conveyed information.
3.5 Use header elements to convey document structure and use them according to specification.
Header elements are implemented whenever necessary and they are used in a consistent manner.
3.6 Mark up lists and list items properly.
All list elements are marked up according to functionality.
3.7 Mark up quotations. Do not use quotation markup for formatting effects such as indentation.
Quotation markup is not always reliable for our native language, as most browsers do not render it according to specifications. We do not use quotation markup for formatting.
6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page.
We do not use dynamic content (in the WCAG 1.0 sense of the word.)
7.2 Until user agents allow users to control blinking, avoid causing content to blink (i.e., change presentation at a regular rate, such as turning on and off).
There is no regular blinking in our layout.
7.4 Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages.
There is no regular auto-refresh in our layout.
7.5 Until user agents provide the ability to stop auto-redirect, do not use markup to redirect pages automatically. Instead, configure the server to perform redirects.
There are only server-side redirect in our sites.
10.1 Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user.
There is no pop-up windows or enforced window-changes in our layout.
11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported.
We used editing and evaluations tools that are recommended on the W3C website.
11.2 Avoid deprecated features of W3C technologies.
None of the deprecated elements were allowed in our markup. In addition to that we discouraged their use in our own recommendation regarding markup for textual content.
12.3 Divide large blocks of information into more manageable groups where natural and appropriate.
We devided our content into navigable sections with each content-type.
13.1 Clearly identify the target of each link.
We used the "title" attribute only when the target is not clarified by the context.
13.2 Provide metadata to add semantic information to pages and sites.
We placed descriptive data in the META element in the documents' HEAD.
13.3 Provide information about the general layout of a site (e.g., a site map or table of contents).
We do not use these features yet, because we need user feedback to deem their necessity for the current navigation mechanisms.
13.4 Use navigation mechanisms in a consistent manner.
Our main navigation mechanism are same in all of the pages, and the substructures are the same in the sites with the same functinality.
5.3 Do not use tables for layout unless the table makes sense when linearized. Otherwise, if the table does not make sense, provide an alternative equivalent (which may be a linearized version).
We don not use tables in our layout.
5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting.
We don not use tables in our layout.
12.2 Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone.
We don not use frames in our layout.
10.2 Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels, ensure that the label is properly positioned.
Each form object is propely labelled in context.
12.4 Associate labels explicitly with their controls.
Our LABELS are not placed yet.
6.4 For scripts and applets, ensure that event handlers are input device-independent.
The functions of are site are tested as operable in computer environments.
7.3 Until user agents allow users to freeze moving content, avoid movement in pages.
We don not use moving content.
8.1 Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies [Priority 1 if functionality is important and not presented elsewhere, otherwise Priority 2.]
We don not use scripts and applets.
9.2 Ensure that any element that has its own interface can be operated in a device-independent manner.
The functions of are site are tested as operable in computer environments.
9.3 For scripts, specify logical event handlers rather than device-dependent event handlers.
We don not use scripts.