⚠️ This is a work in progress article.
At Ascenda, we built a suite of products that bring effortless rewards technology for financial services. One critical requirement is making the application accessible to all users. This blog will document the everyday use cases and solutions for accessibility in Angular that I have encountered along the way.
What is accessibility?
Broadly speaking, when we say a site is accessible, we mean that the site’s content is available, and its functionality can be operated, by literally
anyone.
While working with accessibility or a11y in short, you will hear a lot about Web Content Accessibility Guidelines (WCAG), a set of guidelines that define how to make web content accessible. However, WCAG can also be a bit overwhelming. To help mitigate this, the WebAIM (Web Accessibility in Mind) group has distilled the WCAG guidelines into an easy-to-follow checklist, targeted specifically for web content.
The WebAIM checklist can give you a short, high-level summary of what you need to implement, while also linking to the underlying WCAG specification if you need an expanded definition.
Compliances Levels
At Ascenda’s core fintech platform, many stakeholders are involved in making the application accessible, including product people, developers, designers…
