BIK BITV / WCAG Test (App)
The BIK BITV / EN 301 549 Test (App) shows how accessible your mobile app is. It also determines its conformance to BITV 2.0 / EN 301 549 (clause 11 Software) and supports you in improving the app's accessibility.
The test procedure includes the use of the native screen readers VoiceOver (iOS) and TalkBack (Android) and operation with a connected keyboard.
A detailed test report identifies issues and helps you optimize your app. The BIK BITV / EN 301 549 Test (App) can also be used as evidence of conformity to EN 301 549.
The test results are available as accessible sortable HTML report and as accessible PDF/UA conformant PDF report. We also offer an issue export in the formats JIRA and GitLab. When you sample of views is considered representative, you can publsih results by linking to the online version of the test report. You can also communicate the result using our recognized BIK test mark.
We offer two versions of the BIK Test (App):
-
With the BIK BITV / EN 301 549 Test (app), we cover the requirements of the BITV, which references EN 301 549 V3.2.1. This European standard contains in clause 11 a subset of the WCAG 2.1 criteria that apply also to mobile apps. It also includes further other mandatory requirements form other clauses of the EN.
-
The WCAG2ICT Test (app) is limited to testing the WCAG requirements that are deeemed applicable to software. The basis is the WCAG2ICT document developed by the W3C. Please note that public bodies throughout the EU are obliged to comply with the European standard (EN 301 549).
Our Services
-
Detailed explanations, notes and references to best practice examples provide you with expert support for optimization.
-
The granular reporting of issues makes it easier for you to process the test results.
-
Each test is at the end quality-assured by a qualified external BIK test centre.
-
The detailed test report is available as accessible sortable online HTML report, and as an accessible, PDF/UA conformant PDF.
-
We offer an issue export for JIRA and GitLab.
-
You can use the online HTML report as proof of conformity, for example, by linking to it from your accessibility statement.
-
On request, we can create the test report entirely in English.
-
For all those who do not want the test report to refer to the German BITV regulation (e.g. because you operate abroad), we offer an optional EN 301 549 or WCAG2ICT test.
-
The exchange with the experts of our Germany-wide BIK testing network is part of the continuous evaluation process of our procedure. We also liaise with the Accessibility Guidelines Working Group (AGWG) of the W3C in which we are active as invited expert.
-
Last but not least, you benefit from our transparent test procedure and from qualified and experienced evaluators.
The Procedure
-
Use our contact form for your request.
-
We need access to the app, either in an app store or via TestFlight (iOS) or .APK file (Android) in order to define a representative sample of views and in turn work out the offer. Please provide us with the necessary information when making your request.
-
If you want to specify a reduced selection of views to be tested, please let us know when you submit your request (the test report cannot then be published).
-
Let us know which operating systems are to be tested (iOS or Android or both systems). Each will be tested independently. As Android test devices, we use Google Pixel smartphones with unmodified Android as standard (i.e. without additional manufacturer skins).
-
After you submit your request, we or one of the BIK BITV test centres qualified for app tests will contact you.
-
You will receive an offer based on a representative sample or a reduced selection of views (as applicable).
-
During testing, the results are determined manually and involve the use of the respective screen reader (VoiceOVer on iOS, TalkBack on Android). We also test operability with a connected keyboard. Where required, we test the app also on tablets.
-
Once your order is placed, the test can begin. The total duration will depend on the complexity of the test. It will also depend on the work load of the BIK test centre in charge: There may be other tests in line to be completed before yours can start. Commonly, a test will take 6-8 weeks for completion (including quality assurance).
-
Once the test has been completed, we will send you a password-protected HTML and PDF test report.
-
When you have reviewed the test report, let us know if you would like it to be published (this requires that the test is representative). We will then add the test to our list of results. For representative tests, you can include the test mark that must link to the test report.
-
If you would like a further test after issues have been remedied, please contact us again. We will then prepare another quote.
-
Representative tests can be published and you can use the BIK test mark. If you do, it must link to the online test report.
-
If the result for an app is 'conformant', we will be happy to add the site and the implementing agency to the list "Sites & Agencies". Please let us know if you would like to be listed after the project has been completed. We will need details of the implementing agency and the CMS used.
Costing
We determine the costs for an app test individually for your app. To do this, we or the test centre in charge should be able to assess the app.
There is a discountof 10% on the price of a WCAG2ICT due to the lower number of test steps.
The price of an app test results from
-
a base fee (for administrative and communication costs)
-
the number of views to be tested and
-
the complexity of the views in the sample (I, II, III or, for complex views, IV and V, see price table).
Prices of Views
Complexity | Techniques (examples) | Factor | BITV-Test | WCAG2ICT-Test |
---|---|---|---|---|
I | very simple view | x 1 | 120 Euro | 100 Euro |
II | View with more content | x 1,5 | 180 Euro | 150 Euro |
III | Simple view with different states | x 2 | 240 Euro | 200 Euro |
IV | Complex views | — | Pirce dependant on calculated effort | Pirce dependant on calculated effort |
V | Very complex views | — | Pirce dependant on calculated effort | Pirce dependant on calculated effort |
Selection of Views
The number of views to be tested results from the representative sample determined by the test centre. The aim of a representative sample is to provide coverage for all relevant functionality in the app. The selection of views happens independenty in representative tests. This means that you will only be informed of the number of views to be tested, but not of the specific views included (unless all views of the app are included).
For a limited test, the results of which are used for internal purposes only (i.e. the test report cannot be published), you can determine the selection of views (or ask the test centre to suggest a reduced sample).
Complexity Levels
Each view to be tested is assigned a complexity level depending on the content and techniques used. There are five complexity levels.
-
Level I is the base price.
-
Complexity levels II - III mean a factor 1.5 or 2 on the base price, respectively.
-
Complexity levels IV or V apply to complex apps that call up a series of states or contain processes. Here, the factor on the base price is calculated according to the estimated testing effort.
![[Translate to English:] Portrait Detlev Fischer](/fileadmin/user_upload/bilder/portraits/detlev-5.jpg)
Want to get a quote for an App Test?
Thank you for your interest in a BIK BITV / WCAG test (App). Please complete our enquiry form. We or one of our cooperating and authorised test centres will contact you as soon as possible.