Creating Open Education Resources for Diverse Learners

Who “diverse” actually includes

Learners differ in many ways at once. They differ in age, first language, reading level, disability, access to devices and internet, cultural reference points, and how much they already know about the subject. A single open resource will never fit everyone perfectly, but a few early decisions make it usable by far more people than a resource written for an imagined average reader.

Open licensing adds a useful twist. Because others may adapt your work, you do not have to solve every need yourself. Your job is to make the resource sturdy enough to adapt: clear structure, editable formats and plain permissions. Outcomes still vary from learner to learner, and no design guarantees that everyone will succeed.

Start with the learner, not the content

Before drafting, write a short description of two or three realistic readers. For example, a hypothetical adult returning to study after a long break, a teenager reading in a second language, and a learner who uses a screen reader. These are invented sketches for planning, not data about real groups, but they force useful questions. What does each person need to already know? What might block them? What would they use to open the file?

Then write the learning goals in plain terms. Clear learning objectives help every reader, and they also help anyone who later translates or adapts the work, because they show what the material is meant to achieve.

Language and reading level

Plain language is the single most broadly helpful choice. Prefer short sentences, common words and one idea per paragraph. Define a technical term the first time it appears and use it consistently afterwards. Avoid idioms, sports metaphors and jokes that depend on one culture; they are often the first thing to confuse second-language learners and machine translation alike.

Be careful with examples. Names, currencies, units, holidays and household scenes all carry assumptions. Use a mix, and consider writing examples so that a local reader can swap them easily.

If you expect translation, keep text out of images where possible, leave space for languages that run longer than English, and avoid embedding sentences in screenshots. Text that can be selected can be translated; text baked into a picture usually cannot.

Accessibility from the start

Accessibility is cheaper to build in than to retrofit. The core habits are well established:

• Use real headings in order, so screen readers and navigation tools can jump through the page.
• Write meaningful alternative text for images that carry information, and mark purely decorative images so they can be skipped.
• Provide captions and, ideally, a transcript for audio and video.
• Do not rely on color alone to convey meaning, and keep text contrast high. The widely used web guidelines set a minimum contrast ratio of 4.5 to 1 for normal body text at their AA level.
• Use descriptive link text rather than “click here”.

The broader principles are often grouped under universal design, the idea that features helping one group, such as captions, usually help many others, such as people in noisy rooms. For the technical details of what is expected online, see the published web accessibility standards, and for your own legal obligations consult official sources, since requirements differ by place.

Offering alternative formats is also valuable. A resource available as a web page, a downloadable document and a plain-text version lets readers pick what suits their device, bandwidth and assistive tools.

Prior knowledge and pacing

Learners arrive with uneven backgrounds. Some ways to handle this:

• State prerequisites at the top, and point to where a reader can brush up.
• Break material into short sections that can be read in any reasonable order where the subject allows it.
• Use worked examples before asking for independent practice, and gradually reduce the support provided.
• Watch cognitive load: too many new ideas on one page overwhelms newcomers, while too little challenge bores experienced readers. Optional “go further” sections handle both.
• Add short self-check questions with answers, so people can judge their own progress without needing a teacher.

The research on how best to sequence teaching is mixed in places, so treat these as sensible defaults and not guarantees. If you can, test the draft with a few real people from your target groups and watch where they get stuck.

Technology and access

Not every learner has fast internet or a recent device. Think about file size, whether the resource works on a phone, and whether it can be downloaded once and read offline. Prefer open, widely supported formats such as HTML, plain text, PDF with tagged structure, or EPUB, over formats that need particular paid software. A design that works for offline-ready resources serves learners with limited data as well as those traveling or in places with unreliable connections.

Licensing and attribution

A resource for diverse learners is only useful if others can legally adapt it. Choose an open license deliberately, state it clearly on the first page, and keep a record of every third-party item you include. Images, fonts and audio are common problem areas: a picture found online is not automatically free to reuse. Basic copyright and licensing questions are worth settling before you build, because replacing a restricted image later is tedious. This is general information, not legal advice.

A pre-publication checklist

Run through these questions before releasing the work:

1. Can someone with a different first language follow the text, and could it be translated easily?
2. Does every image have suitable alternative text, and does every video have captions?
3. Can the content be read with only a keyboard and a screen reader, or on a small phone screen?
4. Are prerequisites and learning goals stated up front?
5. Is there at least one way to check understanding without a teacher?
6. Is the license visible, and is every third-party item credited and permitted?
7. Is there an editable source file so others can adapt it?
8. Has at least one person outside your own circle tried it?

No resource passes every question perfectly on its first release. Publish with a clear way for readers to report problems, and treat revision as a normal part of the work.