What this review covers
Open resources are often described as more accessible than conventional ones, but the truth is more mixed. Openness in the licensing sense and accessibility in the usability sense are different qualities. A resource can have a generous license and still be unusable with a screen reader, or be well designed for accessibility and tightly licensed. This review looks at the features people commonly find in open materials and formats, what each is for, and how reliably it tends to be present.
It is a general overview rather than an audit of any specific collection, and it does not name particular products. Always check the actual resource you plan to use.
Features that come from the license
The most distinctive accessibility advantage of open resources is not a technical feature but a permission. Because many open licenses allow adaptation, a teacher, librarian or disability support service can often legally make an alternative version: enlarge the text, add captions, write image descriptions, convert to a different file type or translate. With a fully restricted resource, doing so may require explicit permission or fall under limited exceptions that differ by country.
This permission has limits. Licenses with a NoDerivatives condition may prevent edits, and the legal position on accessible copies differs between places. Check the license, and where it matters, an official or institutional source.
Text alternatives for images
Well-made open resources include text descriptions for images that carry meaning. In web pages and e-books, this is usually the alt attribute. In word-processor files it is the alt text field. Quality varies widely. Typical problems include missing descriptions, descriptions that only repeat a filename, and long descriptions of charts that omit the actual point. A good description conveys the purpose of the image in context. Complex figures benefit from a longer explanation nearby in the text.
Captions, transcripts and audio description
Video and audio are common in open material. Features to look for:
- Captions synchronized with speech, preferably checked by a person, since automatic captions can mangle names and technical terms.
- Transcripts that let readers skim, search or use a braille display.
- Audio description or narration of important visual content, which is much less common than captions.
Many open video resources have at least automatic captions; fewer have reviewed captions, and still fewer have audio description. Where a license allows, adding your own is possible but time-consuming.
Structure and navigation
Proper headings, lists, table headers and a logical reading order let assistive technology move through a document efficiently. Web-based and e-book formats built on structured markup often handle this well when the author used the right styles. Problems arise when authors only imitated headings by enlarging the font, or used tables for layout. A quick test is to try navigating by headings with a screen reader or with the document outline view in your software.
Flexible layout and presentation
Formats that reflow, meaning text rewraps to fit the screen, support enlarged text and small displays. Web pages and many e-book formats do this by default, letting readers change font size, spacing, colors and sometimes typeface. Fixed-layout formats keep pages looking identical but make enlargement awkward, forcing sideways scrolling. This is relevant to dyslexia support and low-vision users, who commonly adjust presentation, though preferences differ between individuals.
Format comparison
| Format | Common strengths | Common weaknesses |
|---|---|---|
| Web page | Reflows, easy to restyle, works with many tools | Quality depends on code; interactive items vary |
| E-book (reflowable) | Adjustable text, portable | Support for images and math varies |
| Tagged PDF | Fixed look, widely readable | Often untagged; hard to reflow |
| Word-processor file | Editable, has built-in checks | Needs proper styles to work well |
| Slides | Familiar to teachers | Often image-heavy with poor order |
| Video | Rich explanation | Needs captions, transcripts, descriptions |
No format guarantees accessibility; each can be done well or badly.
Standards and statements
Many projects aim for the Web Content Accessibility Guidelines, an international set of recommendations with levels of conformance. A resource that mentions conformance to a recognized level, and says what was tested, is usually a good sign, though such claims are not always independently verified. An accessibility statement describing known issues and how to report them is also useful, and its absence is common among smaller projects. The principles of universal design, creating things usable by as many people as possible without special adaptation, underlie much of this thinking.
Mathematics, code and interactive content
These remain harder areas. Equations as images are unreadable to screen readers unless accompanied by text, while equations in structured markup can often be read aloud or navigated. Code samples in plain text are usually fine. Simulations and interactive exercises vary widely and may not work by keyboard. Check whether an equivalent static explanation is provided.
A quick evaluation
When reviewing a resource, a few minutes of testing is usually enough to learn a lot:
- Can you use it with only a keyboard?
- Do images have meaningful text descriptions?
- Do videos have accurate captions and a transcript?
- Does the text enlarge to about twice its size without breaking?
- Is there an accessibility statement or contact point?
If a resource falls short but is otherwise right, remember that the license may let you fix it, and sharing the improved version helps the next user. No review can replace asking learners who use assistive technology what works for them.