Finanteq

What makes a mobile banking partnership successful? We explore eight key areas in our latest blog post.

Read the full article: https://loom.ly/aMLecgc

September Job Alert! 🚨

If you are looking for a new carrer opportunities, we might have something for you 👀

FINANTEQ offers:
✅exceptional growth environment,
✅remote work,
✅flexible hours.
Learn more about our benefits here:
https://loom.ly/hQH9hiY

Check the position details by clicking on the link. If you have any questions, feel free to contact our recruiters 📱

Current offers:
👉 Business Systems Analyst
https://loom.ly/YeU8pz8

👉 Pega System Architect
https://loom.ly/44RQsfo

👉Junior Business Analyst
https://loom.ly/OCOWMf4

👉 Full Stack & Cloud Engineer (AWS, Terraform)
https://loom.ly/OeM_Mv4

👉 Full Stack Developer (Kotlin)
https://loom.ly/CV7muFg

Last week, we asked how you perceive WCAG in your organisation, and the responses were evenly split between “a legal requirement” and “a quality standard.”

WCAG can be all of these at the same time:
▪️ a legal requirement
▪️ a quality standard
▪️ part of the UX/UI

It all depends on the context. As accessibility guidelines, WCAG can serve as a legal benchmark that a product must meet, a quality standard that helps differentiate it from the competition, and part of the UX/UI as an extension of the design system.

How organisations approach WCAG may vary, but its business value is always there. An accessible product or piece of software can be easier for everyone to use, improve the user experience, reduce barriers to accessing services, and help reach a wider audience.

Read more about WCAG implementation:
https://www.finanteq.com/blog-posts/wcag-implementation-guide

Are you guilty of any of these WCAG implementation mistakes...?

Implementing WCAG often results in problems caused by overlooking basic accessibility principles. Many of these issues can be relatively easily eliminated if they are identified at an appropriately early stage.

Get more insights about WCAG implementation here:
https://www.finanteq.com/blog-posts/wcag-implementation-guide

Digital accessibility is a topic in which WCAG (Web Content Accessibility Guidelines) cannot be overlooked. The standard provides a foundation for planning, designing, implementing, and maintaining systems that deliver a high level of inclusivity.

The challenge lies in how to approach these guidelines in practice. How do you navigate the complex world of WCAG? Where should you start when implementing the standard in your organization? What are the most common mistakes, and how can you avoid them? Is WCAG a guideline or a requirement?

You’ll find answers to these questions — and many more — in our latest article. We invite you to give it a read:
https://www.finanteq.com/blog-posts/wcag-implementation-guide

Web Content Accessibility Guidelines (or WCAG for short) can cause a headache for anyone trying to make their product more accessible. Many organisations treat WCAG as a legal requirement, which downgrades it to an unpleasant obligation rather than a helpful rulebook.

How does your team view WCAG - a guideline or a requiremnt? Tell us in the comments 👇

With FINANTEQ’s SuperWallet, banks can now offer directly through their banking app.

SuperWallet continues to expand with new services that help banks go beyond traditional financial products. The latest addition is eSIM, allowing customers to choose a country or region, purchase a data plan for their trip, install the eSIM and monitor their usage. All within the banking app.

Customers no longer need to search for a local operator once they arrive. Their smartphone can connect to the network automatically, helping them stay connected from the moment they land.

This is one example of how banks can use their digital channels to offer relevant, everyday services while creating new opportunities for customer engagement and value-added services.

Looking to add eSIM to your banking app? Contact us at [email protected] to explore how SuperWallet can help your bank.

⛓️‍💥 https://loom.ly/Ed1k-u4

It's always because of legacy systems, right?

What drives the cost, timeline, and quality of app development? We take a closer look in our latest blog post: https://loom.ly/QYqakmE

What are the risks of ignoring accessibility? Check it out in the carousel👇