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.2 AA 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

• Iterative internal accessibility audits and reporting
  • Accessibility issues are collected, documented, assigned to each team and their progress is monitored and validated

• 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 User flows and Design system
  • WCAG 2.2 Level AA tag on each component that has been designed, implemented and validated for accessibility with manual and automated tests. Accessibility guidelines are included in the design and implementation documentation

• • Perceivable
    
    • Our Design Tokens are designed to match our brand and comply with accessibility rules for contrast, ratios, typography and sizes

• • Operable: focus management, keyboard navigation and screen reader support
    
    • Form components (inputs and supporting elements), dialogues, tabs, image slider, and buttons satisfy perceivable requirements and can be navigated and interacted with keyboard only and assistive technologies like screen readers
    • Transitions are simple and new areas in the pages are announced according to guidelines
    • Focus rings are clearly visible, focus traps and rowing tab indexes are clearly handled
• 
  
  • Understandable:
    • Errors and status of forms are handled as out-of-the-box ensuring all our form experiences follow consistent best practices
•  
  • User flows:
    
    • Templafy Library and Email Signature add-in experiences are fully accessible to keyboard interaction, screen reader users and has high compliance to WCAG 2.2 Level AA guidelines
    • Productivity and Check add-ins are keyboard accessible and have been tested for screen reader usage
    • Alternative text for images stored in Templafy can be configured by Templafy Admins and is used to provide our users the ability to choose the right asset in their documents and build more accessible documents

• Quality Assurance:
  • Accessibility rules implemented within eslint
  • Automated accessibility testing framework for component and end-to-end testing with Playwright and Axe Core

What's next?

• Continuous accessibility improvements in the platform through the Design system
  • Tables and Lists and Editing experiences
• Accessible user flows:
  • Focus on the Admin center experiences
  • Continuous creation of accessible new functionalities
  • Introduce VAP/ACR reports for each product