FT-05: On a screen
<!-- Generated from field-tests/suite.json by tools/field_tests.py. Edit the JSON, not this file. -->
Category: Screen · Time: about 10 minutes · Run it and see results: https://openckey.org/tests/test?id=FT-05
What it checks
A CKey shown on a phone or computer screen reads, including at low brightness and in light-on-dark colours.
Why
Many codes are read off another screen: a ticket in a wallet app, a slide, a monitor. Screens add moiré, refresh banding and glare that paper does not.
Test codes
Print or open the sheet at https://openckey.org/tests/sheet?id=FT-05. It is drawn by the CKey web SDK from the values below.
| Code | Size | Version | Level | Layout | Style | Holds |
|---|---|---|---|---|---|---|
| A | 2.0 in | smallest that fits | M | standard | plain | https://openckey.org/t/FT05-A |
| B | 2.0 in | smallest that fits | M | standard | dark | https://openckey.org/t/FT05-B |
Set up
- Open this test's sheet on a second device: another phone, a tablet or a computer.
- Make each code about 2 inches (5 cm) wide on that screen.
Steps
- Try code A (black on white) at full brightness, then at the lowest comfortable brightness.
- Try code B (light on dark) at full brightness.
- Try code A on a computer monitor at arm's length.
- Allow up to 5 seconds each and record whether it read.
What to record
- Read within 5 seconds, boolean, required. For each of: A, full brightness, A, low brightness, B, full brightness, A, monitor.
Every report also records the device, operating system, reader and its version, and the printer or screen.
How to grade it
- Pass: Every case read.
- Partial: Code A at full brightness read, but another case did not.
- Fail: Code A at full brightness did not read.
Report a result
- On openckey.org: https://openckey.org/tests/test?id=FT-05, with optional photos.
- On GitHub: open a field-test report and choose FT-05.
Both are published together at https://openckey.org/tests and as JSON at https://openckey.org/api/field/results.