{"id":1019,"date":"2023-08-23T04:01:00","date_gmt":"2023-08-23T04:01:00","guid":{"rendered":"https:\/\/lblearning.com.au\/?p=1019"},"modified":"2023-09-07T04:45:20","modified_gmt":"2023-09-07T04:45:20","slug":"designing-accessible-learning-5-tips","status":"publish","type":"post","link":"https:\/\/lblearning.com.au\/designing-accessible-learning-5-tips\/","title":{"rendered":"Designing accessible learning: 5 tips from Lyndal"},"content":{"rendered":"

[et_pb_section][et_pb_row][et_pb_column type=”4_4″][et_pb_text]<\/p>\r\n\r\n

Top 5 tips for designing accessible digital learning<\/h2>\r\n\r\n\r\n\r\n

It\u2019s easy to make assumptions about what learners need based on our own perspective. We are learners too. We know what we like and need when it comes to learning, but we don\u2019t know everything. We can\u2019t<\/p>\r\n\r\n\r\n\r\n

Other learners have different needs to ours. Other learners have different perspectives. One learning experience could be great for us, while others experience roadblocks or confusion. We can only find out what others experience when we do some investigating beyond our own perspective. We need to dig deeper than our own backyard.<\/p>\r\n\r\n\r\n\r\n

Other learners have needs different to mine. Other learners have different perspectives and abilities too. A learning experience might be trouble-free for me, but others could experience roadblocks, confusion or disengagement from the same event. I can only find out what others experience when I do some investigating beyond my own perspective. I need to dig deeper than my own backyard.<\/p>\r\n

Here are some fundamental tips for designing digital learning with accessibility in mind.<\/p>\r\n\r\n\r\n\r\n

Tip 1: Real user experience testing<\/h2>\r\n\r\n\r\n\r\n

User experience testing for learning is about engaging users to do some testing of the learning designs to obtain feedback. Feedback will help to inform improvements to the design and ultimately make the final product a better experience for learners. Ideally user testing happens before a learning event is rolled out and during the design process.<\/p>\r\n\r\n\r\n\r\n

User experience testing takes time. Sometimes when timeframes are short it can be tempting to omit or modify testing, but this often happens at the expense of good results.<\/p>\r\n\r\n\r\n\r\n\r\n\r\n

\"Close<\/figure>\r\n

One common way of performing user testing within short timeframes is to ask people in the office or at home to do it. While this might seem like a great solution to save time, unless those people adequately represent the diversity of your target audience the results will rarely give you the range of perspectives you need.<\/p>\r\n\r\n\r\n\r\n\r\n\r\n

Real user testing incorporates testing for Web Content Accessibility Guidelines (WCAG)<\/a><\/span> compliance. It also includes inviting feedback from a diverse range of learners, testing across different devices, browsers, platforms and access points and considering the environment\/s, motivation\/s and influences of the entire experience.<\/p>\r\n\r\n\r\n\r\n

When time and effort is spent on real user experience testing the results speak for themselves. Rework is minimised. Outcomes are more readily achieved. Learner engagement is improved. Client confidence is high. Performance expectations are met.<\/p>\r\n\r\n\r\n\r\n

User experience testing can be seen as an investment rather than an expense. It is too valuable to ignore.<\/p>\r\n\r\n\r\n\r\n

Tip 2: Design with all users in mind (from the outset)<\/h2>\r\n\r\n\r\n\r\n
\r\n

\u201cIf you need to create an accessible version of something there is a problem with the original design\u201d.<\/p>\r\n<\/blockquote>\r\n\r\n\r\n\r\n

Sometimes learning needs to be “retrofitted” for accessibility when the product is found to be inaccessible. This takes time and effort and may lead us to question how effective user testing was (refer to Tip 1). But occasionally designs are intentionally created with both a “normal” version and an accessible version.<\/figure>\r\n

 <\/p>\r\n

\"Close<\/figure>\r\n\r\n\r\n\r\n\r\n\r\n

I can’t think of a single situation where there would be an advantage to creating two versions of one design. It is double handling. Duplication creates version control nightmares. It brings attention to individual differences unnecessarily. It is short sighted. Perhaps I am being too harsh, but a point needs to be made here.<\/p>\r\n\r\n\r\n\r\n

Aiming for accessibility from the outset is sensible. When we meet WCAG guidelines we know a range of users will benefit. When we perform user testing and design to the specific needs of learners there is less chance of having to spend more time and money later. No-one benefits when learner needs can’t be met. No-one enjoys explaining to a learner that they can’t access what others can. And no-one enjoys recreating a learning design after it is completed (or engaging a contractor) to fix something that has gone wrong.<\/p>\r\n\r\n\r\n\r\n

When learner needs are not met from the outset it is embarrassing and potentially reputation damaging too. That is often a cost not considered until it is too late.<\/p>\r\n\r\n\r\n\r\n

Of course, there could be a small number of legitimate reasons why alternative versions are needed post roll out, but the principle of designing for accessibility from the outset is a good one and at the very least minimises (if not avoids) unnecessary rework.<\/p>\r\n\r\n\r\n\r\n

Tip 3: Describe all images<\/h2>\r\n\r\n\r\n\r\n

Use alternative text (alt text) to describe all digital images.<\/p>\r\n\r\n\r\n\r\n

If an image is used for anything other than pure decoration it should be described in words. This is different to providing a caption below an image.<\/p>\r\n\r\n\r\n\r\n

\"A<\/figure>\r\n\r\n\r\n\r\n

Descriptions of digital images provide context for assistive technology users. There are many reasons why people use assistive technology such as screen readers. Common reasons are vision impairment, neurodiversity, and personal preference.<\/p>\r\n\r\n\r\n\r\n

When an image is not described in alt text the dimensions of the image will be read out by a screen reader regardless of whether a caption exists. That is totally unhelpful for the learner. It adds unnecessary time and effort to their experience.<\/p>\r\n\r\n\r\n\r\n

All digital creation tools have alt text capability. This includes Microsoft Office (Word, PowerPoint, Outlook, Excel) to Social Media (Facebook, LinkedIn, Instagram, X) to Authoring tools (Articulate, Captivate, Lectora) and PDFs. It is up to the user \u2013 us \u2013 to add image descriptions.<\/p>\r\n\r\n\r\n\r\n

Here are some simple rules to follow:<\/p>\r\n\r\n\r\n\r\n