{"id":13261,"date":"2022-10-17T16:39:52","date_gmt":"2022-10-17T15:39:52","guid":{"rendered":"https:\/\/www.sage.com\/en-gb\/blog\/?p=13261"},"modified":"2026-01-16T12:54:52","modified_gmt":"2026-01-16T12:54:52","slug":"our-accessibility-roadmap-implementing-best-practise-at-sage","status":"publish","type":"post","link":"https:\/\/www.sage.com\/en-gb\/blog\/our-accessibility-roadmap-implementing-best-practise-at-sage\/","title":{"rendered":"Our accessibility roadmap: implementing best practise at Sage"},"content":{"rendered":"
\n\t
\n\t\t
\n\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\tAccessibility<\/a>\t\t\t\t\t\t<\/div>\n\t\t\t\t\n\t\t\t\t
\n\t\t\t\t\t

\n\t\t\t\t\t\tOur accessibility roadmap: implementing best practise at Sage\t\t\t\t\t<\/h1>\n\t\t\t\t<\/div>\n\n\t\t\t\t\t\t\t\t\t

\n\t\t\t\t\t\t\t\t\t\t\t<\/p>\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\n\t\t\t<\/div>\n\n\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t<\/div>\n\t\t

\n\t\t
\n\t\t\t
\n\t
\n\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t\t\n\t\t
\n\t\t\t\n\t\t\t\t\"\"\t\t\t\tAndy Varley<\/span>\n\t\t\t<\/a>\n\n\t\t\t\t\t<\/div>\n\n\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t<\/div>\n<\/div>\n\n\n\n\n\n

At Sage, it is critical to us that we implemented accessibility across all teams as part of our pledge to make all our products and services accessible by 2025.  <\/p>\n\n\n\n

The Web Content Accessibility Guidelines (WCAG) 2.1 provide useful information on what to consider when making experiences more accessible. However, as part of our work to introduce accessibility best practise to our business, our team at Sage wanted to make the guidelines easier to use. <\/p>\n\n\n\n

This involved breaking the guidelines down into a more digestible format that our colleagues would not only understand better, but also be able to implement them directly into their teams and processes. <\/p>\n\n\n\n

Read on to find out how we did this by introducing accessibility best practices into our Sage ways of working\u2026 <\/p>\n\n\n\n

Making accessible guidelines more accessible<\/strong><\/h2>\n\n\n\n

There\u2019s no easy way to put this\u2026 the WCAG guidelines are hard to understand.  <\/p>\n\n\n\n

They\u2019re complex, long, and written in a way that, if you\u2019re not a subject specialist, you\u2019re going to struggle to understand what most of it means. It\u2019s complicated.  <\/p>\n\n\n\n

At Sage, we are always looking for ways to break down barriers, so it was crucial for us to find a way to allow colleagues to effectively understand and use these day-to-day when developing our products and services.   <\/p>\n\n\n\n

Categorising disabilities and developing personas<\/strong><\/h2>\n\n\n\n

 After looking into various approaches of how to break down the guidelines for ease, we decided to group the guidelines to focus on the disabilities that they assist. This gave us around 12 different categories that covered most of the WCAG guidelines.  <\/p>\n\n\n\n

Discussions with Sage colleagues and our User Researcher for the Design System Team led to the suggestion of creating some personas alongside this work. This would help us better visualise who we are trying to support using the 12 different categories.  <\/p>\n\n\n\n

We also developed five accessibility personas which you can read about<\/a> on our accessibility hub.   <\/p>\n\n\n\n

The personas: Mary, Manuel, Anne, Ayesha, and David include a mixture of disabilities and accessibility challenges. Each persona covers a certain part of the WCAG guidelines. <\/p>\n\n\n\n

Once this was in place, we tackled how to implement this into our relevant teams and products at Sage.  <\/p>\n\n\n\n

This involved expanding on each of the personas and showing which parts of the WCAG guidelines applied to each persona. To help us prioritise, we calculated the estimated number of users affected in each category.<\/p>\n\n\n\n

Applying these tools to create accessibility roadmaps <\/strong> <\/h2>\n\n\n\n

The below image is an example of the roadmap we have created for the Mary persona. This shows how we broke this down into various WCAG success criteria that was relevant for this persona.  <\/p>\n\n\n\n

\"An<\/figure>\n\n\n\n

We then review our products and services against this persona to ensure we are meeting each area of criteria. Once we have tackled the pain points for each persona, we can confidently say that our products and services will be more accessible to users who live with that disability or challenge. <\/p>\n\n\n\n

While we cannot categorically ensure that every point on this roadmap is relevant for every person who has Dyslexia, Dyscalculia, or is colour blind, we have worked to group these in an effective way so that we\u2019re can support as many of their accessibility needs as possible. <\/p>\n\n\n\n

Adaptability is the key to accessibility<\/strong> <\/h2>\n\n\n\n

There are no \u2018one size fits all\u2019 solutions when it comes to accessibility so best practise involves being adaptable. This ensures that our team at Sage can create products and services that are accessible to all, no matter their level of ability. <\/p>\n\n\n\n

It was important from the start to have a clear path of how we are going to become a more accessible business. Having a clear approach to this when it comes to designing and developing our products and services, is critical to our journey. <\/p>\n\n\n\n

We still have a lot of work to do around accessibility at Sage but with the right people and commitment, we will be able to achieve our goal. <\/p>\n\n\n\n

Find out more about the work we are doing as a business to improve accessibility for our customers, colleagues, and partners. Visit our accessibility hub<\/a> for additional information about the accessibility of our products, colleague training, and our design system.\u00a0\u00a0<\/p>\n\n

\n\t
\n\t\t
\n\t\t\t
\n\t\t\t\t

Browse more topics from this article<\/h3>\n\t\t\t<\/div>\n\t\t\t
\n\t\t\t\t