Correctly implement the criteria of the BITV – Accessibility Information Technology Regulation

3. October 2019
Peggy

In order to design and programme IT solutions barrier-free for all concerned, the criteria of the BITV are available as helpful tools.

BITV is called Barriers Information Technology Regulation and is a bit dry as legislation and regulations, but extremely important. We are trying to work this out in a somewhat simplified way, because these criteria must be met if one wishes to call oneself 'barrier-free'. certified as such. Everything else is only "barrier-poor" – also beautiful, but not enough. So if you want to venture into accessible websites, you will find help here – through information or gladly through active participation by us. Our IT solution for a better work-life balance is just about to be certified. Therefore, we use this example to show what the state of play of the project is and how we have solved one doer other.

Principle of perceptibility

1.1.1.1 Old texts for non-text content
Layout graphics have empty alt attributes.
FamJob Page: Design = OK | HTML = OK | WPF = OK | Apps = OK

1.1.1.2 Old texts for controls
Graphical controls have useful alternative texts.
Design = OK | HTML = OK | WPF = OK | Apps = OK

1.1.1.3 Old texts for graphics
Informative graphics and images have useful text alternatives. Objects such as video and audio files as well as applets have at least short descriptive text alternatives.
Design = OK | HTML = OK | WPF = OK | Apps = OK

1.1.1.4 Old texts at Captchas
Design = OK | HTML = — | WPF = — | Apps = —

1.2.1 Old media for recorded audio and video files
Audio files and silent video files have equivalent media alternatives.
Design = OK | HTML = OK | WPF = OK | Apps = OK

1.2.2 Extended subtitles
Recorded videos have synchronous subtitles.
Design = OK | HTML = OK | WPF = OK | Apps = OK

1.2.3 Audio descriptor or full-text alternative
Videos are provided with audio description or full-text alternative.
Design = OK | HTML = OK | WPF = OK | Apps = OK

1.2.4 Live subtitles
Live broadcasts have synchronous subtitles.
Design = OK | HTML = OK | WPF = OK | Apps = OK

1.2.5 Audio Description
Videos are provided with audio description.
Design = OK | HTML = OK | WPF = OK | Apps = OK

1.3.1.1 Headings – Information presentation
Page contents are accessed by headings.
Design = OK | HTML = OK | WPF = OK | Apps = OK

1.3.1.2 Lists – Information Presentation
Lists (including menus) are visually recognizable as such and are labeled with the intended HTML structure elements.
Design = OK | HTML = OK | WPF = OK | Apps = OK

1.3.1.3 Quotes – Information Presentation
Quotes written as separate sections are awarded with blockquote.
Design = OK | HTML = OK | WPF = — | Apps = —

1.3.1.4 Outline – Information presentation
Paragraphs and text highlights are distinguished with suitable structural elements.
Design = OK | HTML = OK | WPF = OK | Apps = OK

1.3.1.5 Tables – Information Presentation
Data tables are properly constructed and excellent.
Design = OK | HTML = OK | WPF = — | Apps = —

1.3.1.5 Table Cells – Information Presentation
In complex data tables, the reference of headings and content (via scope or via id and headers) is defined, mappings of headings in simple data tables are correct.
Design = OK | HTML = OK | WPF = — | Apps = —

1.3.1.6 No tables for layout – information presentation
Mark-up intended for data tables is not used for layout tables.
Design = OK | HTML = OK | WPF = — | Apps = —

1.3.1.7 Label Form – Information Presentation
Labels of form fields are correctly linked.
Design = OK | HTML = OK | WPF = OK | Apps = OK

1.3.2 Meaningful Order – Capture Content
Page content is in a meaningful order regardless of appearance.
Design = OK | HTML = OK | WPF = OK | Apps = OK

1.3.3 Without sensory features – Capture content
The perception of colors, shapes, position of elements or sounds is not necessary for the operation or understanding of the content.
Design = OK | HTML = OK | WPF = OK | Apps = OK

1.4.1 Useless colours
The perception of colors is not necessary for the operation or understanding of the contents.
Design = OK | HTML = OK | WPF = OK | Apps = OK

1.4.2 Audio control / sound can be switched off
Automatically played sound elements last no longer than three seconds, can be turned off or controlled down regardless of the system volume.
Design = — | HTML = — | WPF = — | Apps = —

1.4.3 Contrast
Colors are appropriately high-contrast.
Design = OK | HTML = OK | WPF = OK | Apps = OK

1.4.4 Adjustable text size (text can be increased to 200%)
Text can be modified by up to 200 percent without losing content or functionality.
Design = OK | HTML = OK | WPF = NO | Apps = NO

1.4.5 Waiver of font graphics
Font graphics are not used.
Design = OK | HTML = OK | WPF = OK | Apps = OK

Principle of usability

2.1.1 Keyboard usability
Even without a mouse, all essential functions and contents can be used.
Design = OK | HTML = OK | WPF = OK | Apps = OK

2.1.2 No keyboard trap
The content does not result in a keyboard trap.
Design = OK | HTML = OK | WPF = OK | Apps = NO

2.2.1 Time limits customizable
Time limits are not available, can be switched off or extended.
Design = OK | HTML = OK | WPF = OK | Apps = OK

2.2.2 (OK) Stop, stop, hide animations
Moving or flashing content is not present, stops after 5 seconds at the latest, or there is a way to stop, stop or hide the movement/flashing.
Design = OK | HTML = OK | WPF = OK | Apps = OK

2.3.1 Refraining from flickering and flashing
Web pages do not contain flickering.
Design = OK | HTML = OK | WPF = OK | Apps = OK

2.4.1 Areas skipable / Bypass member groups
Page areas are accessible by headings, jump links or WAI ARIA document landmarks, frames and iframes have useful titles.
Design = OK | HTML = OK | WPF = OK | Apps = NO

2.4.2 Website titles / useful document titles
Document titles are unique, they denote site and page content.
Design = OK | HTML = NO | WPF = — | Apps = —

2.4.3 Conclusive order of keyboard operation / focus order
Links, form elements, and objects are controlled in a conclusive order using the Tab key. Displayed content and dynamically inserted or modified content appear in a meaningful place in the focus order.
Design = OK | HTML = OK | WPF = OK | Apps = —

2.4.4 Meaningful link texts / Purpose of a link (in context)
Link texts are meaningful through the link text itself or via the programmatically iemanating context.
Design = OK | HTML = OK | WPF = OK | Apps = OK

2.4.5 Alternative access routes
There are two different access routes to the contents of the offer.
Design = OK | HTML = OK | WPF = OK | Apps = OK

2.4.6 Meaningful headings and descriptions
Headings and labels are clear and meaningful.
Design = OK | HTML = OK | WPF = OK | Apps = OK

2.4.7 Current position of focus clear / Visible focus
The keyboard focus is clearly visible.
Design = OK | HTML = OK | WPF = OK | Apps = NO

2.4.8 Location / position in the website clear
The website shows the visitor where he or she is at the moment.
Design = OK | HTML = OK | WPF = OK | Apps = OK

Principle of comprehensibility

3.1.1 Main language indicated
The main language of the website(s) is specified.
Design = OK | HTML = OK | WPF = OK | Apps = OK

3.1.2 Other words and sections awarded
Languages and sections in other languages are labeled with the lang attribute.
Design = OK | HTML = OK | WPF = OK | Apps = OK

3.2.1 No unexpected context change in focus
Focus does not cause an unexpected context change.
Design = OK | HTML = OK | WPF = OK | Apps = OK

3.2.2 No unexpected context change when entering
Input does not result in an unexpected context change.
Design = OK | HTML = OK | WPF = OK | Apps = OK

3.2.3 Consistent navigation
Navigation mechanisms are uniform.
Design = OK | HTML = OK | WPF = OK | Apps = OK

3.2.4 Consistent designation
Navigation mechanisms and functions are uniformly named.
Design = OK | HTML = OK | WPF = OK | Apps = OK

3.3.1 Error detection
If an input error is automatically detected, the incorrect element is displayed and the error is described in text form.
Design = OK | HTML = — | WPF = — | Apps = —

3.3.2 Labeling form elements
Labels of form fields precede the input fields.
Design = OK | HTML = OK | WPF = OK | Apps = OK

3.3.3 Help with errors
If an input error is automatically detected, the error is described in text form. Where appropriate, correction proposals are made.
Design = OK | HTML = — | WPF = — | Apps = —

3.3.4 Avoidance of errors by means of help
Mandatory data entries can be undone or checked and corrected before submission.
Design = OK | HTML = — | WPF = — | Apps = —

Principle robustness

4.1.1 Correct syntax
The test result of the W3C HTML validator is positive.
Design = — | HTML = OK | WPF = — | Apps = —

4.1.2 >>> Name, role, value available
Interactive controls such as links and buttons have programmatically iemanating names and roles.
Design = — | HTML = OK | WPF = OK | Apps = OK

Unterstützung bei BITV-Umsetzung

Wir helfen Ihnen gerne bei der korrekten Umsetzung der BITV - ob als inklusives Design, in einem Pretest, als Beratung oder in der UI-Entwicklung.