Your options for obtaining an accessible hub

September 8, 2020 Rahim Lalani

Uberflip has created Front End V2 to help customers meet web accessibility requirements. The new version supports all the functionality you know and love with Uberflip (CTAs, Uberflip Site Engager, recommendation panel, and more). As well, our team used the opportunity to make a number of under-the-hood improvements that will increase performance and enhance the user experience overall.

Key benefits of Front End V2

  • Accessible: Meets WCAG 2.0 Level AAA accessibility requirements out of the box
  • Faster: Significantly improved page speeds and performance
  • Better SEO: Implements modern SEO best practices to help pages rank higher in search engine results
  • Easier to customize: Simplified coding structure for more user-friendly customization

Performance of Front End V2

We ran a Google Chrome audit of the new Front End V2 and the results speak for themselves!

Moving to Front End V2

Any Uberflip customer with an existing Front End V1 hub can choose to transition it to a Front End V2 hub to take advantage of the improvements. In addition, if you are legally required to make your web properties accessible, you can make your Uberflip hubs compliant by moving them to Front End V2. 

Uberflip offers two options to accomplish this.

Option 1: Let Uberflip take care of everything

We have the technical skills and human resources to help you move to Front End V2. This paid solution includes one-on-one consultation, project scoping, design, review, quality assurance, and delivery.

We recommend this option for customers who don’t have access to web development resources and want to take a hands-off approach.

Option 2 - DIY

We’ve prepared a handbook to help your team understand the Uberflip Hub Front End, how to customize it, and the steps involved in moving to Front End V2. 

Hub Front End V2 is very different from its predecessor, so a simple one-to-one migration is not possible. It requires rewriting all styles and customizations according to the new framework. This means that the transition is not an immediate or "one-click" process. We recommend planning and resourcing this accordingly.

Here are a few things to keep in mind with the DIY option:  

Skill level required

  • Prior experience developing website front ends

  • Strong understanding of HTML and CSS

  • Knowledge of Javascript to support advanced customizations


  • Choosing the DIY option will limit our ability to support you

  • We will not be able to troubleshoot your code because it won’t be accessible to us. Our awesome support team can only do so much!


To explore which option is right for you, please speak with your Uberflip CSM.


About the Author

Rahim Lalani

Rahim is the Product Marketing Manager at Uberflip. He loves understanding the market, crafting messaging, and enabling internal teams for success.

Follow on Linkedin More Content by Rahim Lalani
Previous Article
Five essential sales enablement strategies for remote working
Five essential sales enablement strategies for remote working

With more businesses operating remotely than ever before, ensuring your sales team has everything they need...

Next Article
Ten best practices for writing accessible web content in Uberflip
Ten best practices for writing accessible web content in Uberflip


Want Exclusive Marketing Tips, A/B Test Results and Inspiration?

Subscribe to Our Monthly Newsletter!

First Name
Last Name
Job Title
I agree to receive marketing emails from Uberflip.
By checking this box, you provide us consent to email you educational content, and information on our products and services. You may unsubscribe at any time.
I am an EU Citizen
By registering, you confirm that you agree to the storing and processing of your personal data by Uberflip as described in the Privacy Policy. By registering I confirm that I have read and agree to the Privacy Policy.
You did it! ;)
Error - something went wrong!