Accessibility isn’t anything new, but for years has been viewed as an afterthought by many organisations when it should be a continuous commitment. However, we’re now seeing accessible services shift to the forefront, and it’s something many of us at Code care passionately about.
In line with Accessibility Awareness Day, Code has started a series of skillshare sessions to help educate on accessibility issues in digital, and principles to follow when designing and building digital products. Our long-term goals include creating an accessibility style guide and digital accessibility and policy standards. With the help of an accessibility champions network, made of multi-disciplinary Computerlovers, Code is working toward making meaningful change.
Why is accessibility important?
Barriers that are intentionally or unintentionally created can impact the lives of users with disabilities. Imagine not being able to make a journey to the shops or having to give out your details to somebody because you could not access their website?
Accessibility issues can have an economic impact as well. Statistics show £17.1 billion in annual lost revenue due to 70% of shoppers facing e-commerce issues.
Improving a product’s accessibility can also have a positive impact on other key areas, such as SEO and overall readability. For example, considering descriptive alt text not only makes your imagery more accessible to those with visual impairments but can also boost your search visibility. Screen readers are a useful tool for this, there are both screen readers for Windows and Mac.
To help highlight all necessary aspects to take into consideration when making accessible and useable digital products, WCAG has divided success criteria into four categories – otherwise known as POUR:
Everyone must be able to consume your content in a way they can understand (sight, hearing, touch, transformability). E.g. captions and transcripts.
Everyone must be able to use their input requirements to access your content (input methods, interaction methods, user controls over timings and limits). E.g. Being able to navigate a site via keyboard alone.
Everyone must understand your content (meaning, language, alternative content, functionality, consistency). E.g. Not using jargon and acronyms where possible.
Your site or service cannot be broken by assistive tech (technologies and specifications). Are you using semantic and valid HTML?
As of September 2020, public sector websites must meet the international WCAG 2.1 AA accessibility standards. They must also publish an accurate statement, detailing how accessible their website is and identify any failures with a plan of when they are to be fixed.
Making services accessible is enforcing the right to complete tasks independently and securely. Following the Equality Act in 2010, companies are imposed by law to ensure users with disabilities can access their services, including those online. Accessibility is a right, not a privilege.
Which groups are there to consider?
There are several groups to consider in addition to those with long-term disabilities.
Over 65s are growing faster than any other age group and often struggle with digital services.
Those with temporary impairments can make up a large user group who require accessible services as well (for example, someone who has recently broken their writing hand or someone trying to use their device on a busy train might need larger tap targets).
Accessibility should be taken into consideration in all services a company provides. This includes how your presentations are laid out, which text documents and which Software you use both internally and externally. There are tools you can use to help, for example, best practices for creating accessible friendly spreadsheets.
Want to learn more? Accessibility needs all of us, and a great way to participate is by continuously learning and sharing your knowledge.