Priority 1 Checklist for the pages under efolyoirat.oszk.hu
1.1 Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content).
This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects,
ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video.
Our site does not use the aforementioned elements with the occasional exception of images, used only in the case of organisation identities.
2.1 Ensure that all information conveyed with color is also available without color, for example from context or markup.
Our layour works the same with colors disabled. [
View illustration]
4.1 Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions).
The language changes in out interface are always indicated with text.
6.1 Organize documents so they may be read without style sheets. For example, when an HTML document is rendered without associated style sheets, it must still be possible to read the document.
Our pages render well and remain usable with the style sheets disabled [
View illustration]
6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes.
We do not use dynamic content (in the WCAG 1.0 sense of the word.)
7.1 Until user agents allow users to control flickering, avoid causing the screen to flicker.
There is no regular flickering in our layout.
14.1 Use the clearest and simplest language appropriate for a site's content.
In the creation of the new layout we revised our navigation structure, recurring elements and documentation to more comprehensive, compact versions.
1.2 Provide redundant text links for each active region of a server-side image map.
We do not use server-side image maps.
9.1 Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape.
We do not use server-side image maps.
5.1 For data tables, identify row and column headers.
We do not use table elements at the moment in our interface. Tables may occur in our documentation where they are properly marked up.
5.2 For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells.
We do not use table elements at the moment in our interface. Tables may occur in our documentation where they are properly marked up.
12.1 Title each frame to facilitate frame identification and navigation.
Our layout does not use frames.
6.3 Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page.
We do not use applets, scripts and programmatic objects.
1.3 Until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation.
We do not use multimedia presentations in our sites.
1.4 For any time-based multimedia presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation.
We do not use multimedia presentations in our sites.
11.4 If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) page.
Our pages fulfill prority 1 level of accessibility. Also they can be used as an alternative of the non-accessible version of the site with the same content.
