The Web Content Accessibility Guidelines (WCAG) 2.0 are internationally recognized standards developed by the W3C to ensure digital products are accessible to people with disabilities.
Signeasy aligns with these principles to provide an inclusive experience for all users, including those using assistive technologies such as screen readers and keyboard navigation.
WCAG 2.0 is built on four key principles:
Information and user interface components must be presented in ways users can perceive.
Text alternatives for non-text content
Sufficient color contrast
Content adaptable for screen readers
Users must be able to navigate and interact with the interface.
Full keyboard accessibility
Clear navigation and focus indicators
No reliance on time-based interactions
Content and functionality must be easy to understand.
Clear labels and instructions
Consistent navigation patterns
Helpful and descriptive error messages
Content must work reliably across a wide range of technologies.
Compatibility with assistive tools (e.g., screen readers)
Use of semantic structure and standards
Cross-browser and cross-device support
WCAG 2.0 defines three levels of compliance:
Level A – Minimum accessibility requirements
Level AA – Standard level for most digital products
Level AAA – Highest level of accessibility
Signeasy aims to meet WCAG 2.0 Level AA, which is the most widely adopted standard for SaaS products.
Signature and input fields are clearly labelled
Keyboard navigation is supported for signing workflows
Documents can be accessed using screen readers where supported
All fields include descriptive labels
Error messages clearly indicate required actions
Logical tab order ensures smooth navigation
Core actions (uploading, sending, signing) are accessible via keyboard
Visible focus indicators help users track navigation
Consistent layout and structure improve usability
UI elements meet recommended contrast ratios
Information is not conveyed by color alone
Compatible with VoiceOver (iOS) and TalkBack (Android)
Touch targets are appropriately sized
Core actions do not rely solely on gestures
Accessible email templates with proper structure
Clearly labelled links and actions
While Signeasy supports accessibility best practices, accessibility may also depend on:
The structure and tagging of uploaded documents (e.g., PDFs)
Third-party integrations
User-specific assistive technology settings
To ensure the best accessible experience:
Upload properly structured (tagged) PDFs when possible
Use clear and descriptive field labels when sending documents
Test workflows with keyboard navigation if accessibility is critical