Accessibility Checks
Conalyz Runtime runs the following checks on every screen it captures.
Touch Targets
What it checks: Interactive elements — buttons, links, checkboxes, switches, text fields — that are smaller than 48 × 48 dp.
Why it matters: Small touch targets are difficult to activate accurately, particularly for users with motor impairments or larger fingers. Both Apple and Google recommend a minimum of 44–48 dp.
WCAG criterion: 2.5.5 Target Size (AAA) / 2.5.8 Target Size Minimum (AA, WCAG 2.2)
Colour Contrast
What it checks: The contrast ratio between the foreground (text colour) and background colour for every labelled element on screen.
Why it matters: Low-contrast text is hard or impossible to read for users with low vision, colour blindness, or when viewing a screen in bright light.
Threshold: 4.5:1 — the WCAG AA requirement for normal-sized text (applied uniformly, as font size is not available from the accessibility tree).
WCAG criterion: 1.4.3 Contrast (Minimum)
Focus Traversal
What it checks:
- Interactive elements that are not reachable by keyboard navigation or switch access
- Significant mismatches between the number of focusable elements and the number of interactive elements
- Focus order that moves backwards (upward on screen) without an obvious reason
Why it matters: Users who navigate by keyboard, switch access, or external hardware depend on every interactive element being in the focus order and reachable in a logical sequence.
WCAG criterion: 2.1.1 Keyboard, 2.4.3 Focus Order
Labels
What it checks: Interactive elements — buttons, icon buttons, images used as buttons, checkboxes, switches, and text fields — that have no accessible name.
Why it matters: Screen readers announce the accessible name of an element when a user focuses it. Without a name, the element is announced as its type only (e.g. "button") — which gives the user no information about what it does.
Text fields also accept a hint (placeholder text) as a valid accessible name.
WCAG criterion: 1.1.1 Non-text Content, 4.1.2 Name, Role, Value
Vague Labels
What it checks: Interactive elements whose accessible label conveys no meaning without surrounding context — for example: "Click here", "Read more", "Submit", "OK", "Button", "Tap".
Why it matters: Screen reader users often navigate by browsing a list of all buttons or links on a page. A label of "Read more" is meaningless in that context — it does not tell the user what they will be reading more of.
WCAG criterion: 2.4.6 Headings and Labels, 2.4.9 Link Purpose (Link Only)
Disabled Elements
What it checks: Disabled interactive elements that have a label but no hint explaining why the element is disabled or how to enable it.
Why it matters: When a button is disabled, sighted users often infer the reason from surrounding context (a form with missing required fields, for example). Screen reader users may not have that context — a hint makes the reason explicit.
WCAG criterion: 4.1.2 Name, Role, Value
Slider Values
What it checks: Slider elements that have no current value announced.
Why it matters: Without a value, a screen reader can announce that a slider exists but cannot tell the user its current position. Users cannot meaningfully interact with a slider they cannot read.
WCAG criterion: 4.1.2 Name, Role, Value