It is possible for a syllabus to look perfectly organized on screen and still be confusing to assistive technology. A lot of that confusion comes down to reading order, which is the sequence in which a screen reader or other assistive technology encounters content. Ideally, that sequence should match the logical order in which a student is meant to receive the information.
Why Reading Order Breaks
Reading order problems often appear when a document relies on floating text boxes, side-by-side elements, decorative layout tricks, or copied content that was positioned visually rather than structurally. A human eye may understand the intended order instantly. Software may not. When that happens, the content can become scrambled, even though nothing looks obviously wrong on the page.
Real Example
Suppose your syllabus shows Course Description first, then a floating text box with office hours, and then Grading Policy below it. Visually, the layout may feel clean and intuitive. But a screen reader might encounter Course Description, then Grading Policy, then Office Hours, because the floating text box sits differently in the document structure than it appears on screen. That kind of mismatch can make a document feel much more confusing than the author intended.
Why It Matters
Reading order affects comprehension, not just technical compliance. A student should not have to reconstruct the intended sequence of course policies because the file presents information in a scrambled way. This is one of the easiest accessibility issues to miss if you only ever experience the document visually.
Workflow
Start by checking whether the document uses text boxes, floating objects, or unusual layout elements. Simplify the layout where possible and keep important content in the normal document flow instead of positioning it manually around the page. Then run accessibility checks and use AdaDocumentMaker to catch structural issues that may not be obvious from visual inspection alone.
FAQ
What is reading order?
It is the sequence assistive technology uses to present document content.
Can layout choices affect it?
Yes. Visual layout tricks often create structural confusion.
Do text boxes cause problems?
They can, especially when they contain important course information.
How do I reduce risk?
Keep the structure simple and rely on ordinary document flow whenever possible.
A Practical Place to Start
If your syllabus uses text boxes, complex layouts, or floating objects and you are unsure whether reading order is logical, upload it to AdaDocumentMaker and review the report before distribution.