Accessibility in Templafy

Templafy’s next-gen document generation platform enables professionals to create high-performing documents, faster. We’re committed to building an inclusive ecosystem that’s accessible to every employee.

Templafy supports and stands by the international accessibility standards set by governments and public institutions.

We work towards making our platform compliant with the Web Content Accessibility Guidelines (WCAG) 2.1 and follow the Accessible Rich Internet Applications (WAI-ARIA) 1.1 and ARIA Authoring Practices Guide (APG) recommendations across all our user flows.

As we strive to create a fully accessible platform, we recognize that creating best practices and the relevant know-how takes time. Here’s an overview of our overall approach, how we’re progressing and what’s next.

• Overall approach
• Where are we?
• What's next?

Overall approach

To drive inclusivity, we use the design and implementation of the Templafy platform as our starting point. Our areas of focus include:

• An accessible foundation
  • Creating a design system with accessible components and guidelines to build out-of-the-box accessibility for generic patterns

• Accessibility as part of our quality assurance
  • Automated accessibility tests (both at a lower component level and for the overall experience)
  • Manual accessibility testing – internally with assistive technology (JAWS, NVDA screen readers) and with existing users

• Multiple localization strategies
  • 10 languages supported across the Templafy platform
  • We're committed to releasing fully translated experiences
  • Localized templates with translation data sources and smart fields
  • Working towards the localization of admin customizations

• Accessible user flows
  • Building and maintaining accessibility best practices for both end-users and Admins

• Accessible internal tools
  • Building and maintaining accessibility best practices within our internal platform administration tools

• Accessibility culture
  • Internal training for product and engineering teams in designing, building and maintaining an accessible platform.
  • Driving accessibility practices throughout the organization and with our partners.

Where are we?

• Accessible Design System components
  • WCAG 2.1 Level AA tag on each component that has been designed, implemented and validated for accessibility.

• Perceivable: accessible colors and typography
  
  • Our design system is based on a set of Design Tokens designed to match our brand and comply with accessibility rules for contrast, ratios and sizes. These ensure that our text and components can be built with the right guidelines and the right atomic elements.
  • Typography: we’re working on supporting responsive font sizes
  • All our components use colors and typography according to guidelines.

• Operable: focus management, keyboard navigation and screen reader support
  
  • Form components (inputs and supporting elements), dialogues, tabs, image slider, and buttons (in progress) satisfy perceivable requirements and can be navigated and interacted with keyboard only and screen readers
  • Transitions are simple and new areas in the pages are announced according to guidelines
  • Visible focus rings, focus traps and rowing tab indexes
• Understandable:
  • guidelines and out-of-the-box handling of errors in forms
• Quality Assurance:
  • basic accessibility rules implemented within eslint
    
    
• Accessibility in user flows:
  • Templafy Library and Engage: keyboard friendly navigation with all interactive elements accessible through keyboard

What's next?

• Improving accessibility in the platform through the Design system
  • Creating basic structures to solve layout patterns with the appropriate semantic HTML structure
  • Ensuring non text content is better tagged to announce what is useful for the interaction
    
    
• Accessible user flows:
  • Identify and create goals for each product team
  • Introduce VAP reports