We audit screen after screen
A manual review of every view: keyboard navigation, code inspection and contrast measurements according to WCAG 2.1 AA.
We want to be accessible to everyone.
We want every participant to be able to take part in a vote — regardless of sight, hearing or mobility. That is why we build both Votey applications in line with the WCAG 2.1 guidelines, and most accessibility solutions are already implemented and work every day.
ACCESSIBILITY
Accessibility is a process, not a one-off declaration.
For us, accessibility is part of the product, not an add-on. The key screens of both applications already comply with the WCAG 2.1 guidelines, and we continuously audit screens, measure contrast ratios and test the application with screen readers.
KEYBOARD
Keyboard operation
We aim for every function — from joining an event to casting a vote — to be operable without a mouse. We check every screen for keyboard traps and a logical tab order.
PROCESS
How we work on accessibility.
Four repeatable stages we go through for every screen of the application — from the audit to tests with screen readers.
STEP1
STEP2
We audit screen after screen
A manual review of every view: keyboard navigation, code inspection and contrast measurements according to WCAG 2.1 AA.
We prioritise barriers
Every detected issue is classified as critical, medium or minor and described with acceptance criteria — this makes each fix measurable and verifiable.
STEP3
STEP4
We ship the fixes
Changes reach the application in consecutive releases: from heading hierarchy and field labels, through contrast, to mechanisms for skipping repeated blocks.
We test and verify
After deployment, we re-check every fix against the audit criteria — keyboard navigation, semantics for screen readers and contrast. The screen goes back to testing until it meets all WCAG 2.1 AA requirements.
STEP1
STEP2
STEP3
STEP4
We audit screen after screen
A manual review of every view: keyboard navigation, code inspection and contrast measurements according to WCAG 2.1 AA.
We prioritise barriers
Every detected issue is classified as critical, medium or minor and described with acceptance criteria — this makes each fix measurable and verifiable.
We ship the fixes
Changes reach the application in consecutive releases: from heading hierarchy and field labels, through contrast, to mechanisms for skipping repeated blocks.
We test and verify
After deployment, we re-check every fix against the audit criteria — keyboard navigation, semantics for screen readers and contrast. The screen goes back to testing until it meets all WCAG 2.1 AA requirements.
SCENARIOS
Accessibility in practice.
Real situations of event participants for whom we remove barriers.
Example scenario:
A blind participant
Barriers
- Navigation
- audio only
- Images
- require descriptions
- Screen changes
- must be announced
What we are working on
- Field labels
- linked to inputs
- Roles and states
- communicated via ARIA
- Voting results
- announced live
Screen reader
VoiceOver
NVDA
Joins the event and votes using a screen reader — the page structure and forms are read in a logical order.
Example scenario:
A low-vision participant
Barriers
- Small text
- illegible
- Low contrast
- invisible links
- Focus
- easy to lose
What we are working on
- Text contrast
- at least 4.5:1
- 200% zoom
- no loss of content
- Focus
- visible on every element
200% zoom
Contrast
Visible focus
Zooms the interface to 200% and needs clear contrast to cast a vote independently.
Example scenario:
A participant with a motor disability
Barriers
- Mouse
- unavailable
- Complex gestures
- impossible
- Small buttons
- hard to hit
What we are working on
- Full operation
- from the keyboard
- Focus traps
- eliminated
- Touch targets
- at least 44×44 px
Keyboard
No complex gestures
Large touch targets
Handles the entire event using only the keyboard — from joining to casting a vote.
ECOSYSTEM
Two applications, one accessibility.
We work on accessibility in parallel in the participant app (PWA) and the administrator app (CRM) — removing barriers where users actually encounter them.
CRM
Admin Application
Create and configure the entire event: voting, agenda, participants, and additional services. Launch it with one click.
