11 minutes
Assistive technology, and the ordinary things that break it What the tools do, what stops them working, and how much of that is decided in the documents, decks and recordings staff make themselves.
What you’ll be able to do Identify in your own documents, pages and recordings the specific choices that stop assistive technology working, and fix the one you control today. Compare the responses to this question and explain your choice: What should the training team do? Document a next step for Assistive technology, and the ordinary things that break it: Open the last document or slide deck you sent to more than ten people. Check its headings, images, links and tables, fix what you can in it, then fix the template it came from so the next one starts right. The tools are ordinary, and so is what breaks them Assistive technology is not exotic equipment. It is a screen reader that speaks or brailles what is on the screen; magnification that enlarges part of it; a setting that raises contrast or text size; speech input that types what a person says; switch or keyboard-only control for someone who cannot use a mouse; captions and transcripts; reading support that highlights text as it reads aloud; an alternative keyboard; a communication device. Much of it is already in the phone or computer a person owns, and plenty of people use two or three of these at once, or only when a condition flares.
What stops these tools is just as ordinary, and nearly all of it is decided in documents and pages that staff make themselves. A heading made by enlarging bold text carries no structure, so a screen reader cannot use it to move through a long document, and neither can anyone skimming on a phone. A scanned page is a photograph of words with nothing underneath to read. A table drawn to line things up reads as a jumble. An image holding the only copy of a deadline, with no description, is a blank. A link that says “click here” tells a person moving link to link nothing at all. Color used as the only signal disappears for the reader who cannot see the difference.
The useful conclusion is not that this is technical work for somebody else. It is that the fix is upstream and cheap. Structure added once, in the template, in the recording routine, in the standard posting, outperforms any amount of repair afterward, and it never requires anyone to disclose a disability first.
What the tools actually do Screen reader
Speaks or brailles what is on the screen and moves through it by heading, link, table and form field. It reads structure, not appearance, so a heading style is the difference between a navigable document and an undifferentiated wall of text.
Magnification and text settings
Enlarges part of the screen, or raises text size and contrast across it. A layout that hides content, overlaps it, or forces side-to-side scrolling to read one line breaks under ordinary everyday use.
Captions and transcripts
Captions carry speech and important sound as text on a recording. A transcript makes the same content readable, searchable and usable at a person's own pace. Automatic captions are a first draft, and they are weakest on exactly the program terms a briefing depends on.
Keyboard-only and switch access
Some people navigate everything by keyboard or by a single switch. Anything that responds only to a mouse — a drag-only control, a menu that opens on hover, a button that cannot be reached by tab — is simply unavailable to them.
Speech input and reading support
Speech input types and controls by voice. Reading support reads text aloud and highlights it as it goes. Both depend on real text, and neither can do anything with a scanned image or a field whose label is not attached to it.
Communication devices
Some people speak using a device, and composing a sentence takes time. A process built around a phone call with a hold queue, or a meeting where speed decides who is heard, excludes them by pace rather than by rule.
Removes the barrier, creates it, or moves the work onto the person? Using the heading styles in the template so a long document can be moved through by heading.
Choose a category Removes the barrier Creates the barrier Moves the work onto the person Posting the slide deck as a scan of a printed copy.
Choose a category Removes the barrier Creates the barrier Moves the work onto the person Adding a line that says materials are available in other formats on request, and nothing else.
Choose a category Removes the barrier Creates the barrier Moves the work onto the person Correcting the automatic captions on a recording and posting the transcript beside it.
Choose a category Removes the barrier Creates the barrier Moves the work onto the person Marking a required field only by turning its border red.
Choose a category Removes the barrier Creates the barrier Moves the work onto the person Asking the one colleague who uses a screen reader to test every new form, on top of their own job.
Choose a category Removes the barrier Creates the barrier Moves the work onto the person Writing link text that says where the link goes instead of “click here”.
Choose a category Removes the barrier Creates the barrier Moves the work onto the person Setting a form to time out after ten minutes with no warning and no saved answers.
Choose a category Removes the barrier Creates the barrier Moves the work onto the person Check matches Reset Five things staff decide without noticing Headings A heading style tells the document that this line is a heading. Enlarged bold text only tells a sighted reader. With real headings, a screen reader can jump section to section, a long document gets a working table of contents, and anyone reading on a phone can find the part they need. This is one menu choice, and it is the single highest-value habit in the list.
Images and charts If an image carries information — a deadline, a chart, a diagram of a process — that information has to exist in text as well, either as a description attached to the image or in the paragraph beside it. A chart also needs its point written out: not only what it shows, but what it means. Decoration needs no description; information always does.
Links Many people move through a page link by link, hearing only the link text. “Click here”, “read more” and a bare web address are all dead ends out of context. Write what the link leads to, in words that make sense read on their own, and keep the same wording for the same destination across your materials.
Tables and layout A table built with real rows, columns and header cells can be read across and down. A table drawn with spacing and boxes to make a page look tidy becomes a jumble when read aloud, and it collapses on a phone. Use tables for data, headings for structure, and never a table to lay out a page.
Files and formats A scanned document is a picture of words: nothing to read, nothing to search, nothing to enlarge cleanly. Post the original file, saved with its structure intact, and say plainly in the posting what is available and in what form. If a form has to be completed and returned, check that it can be completed on a screen rather than only printed and signed.
Color and contrast Color is useful as a second signal and dangerous as the only one. Red text, a green highlight or a colored status dot means nothing to someone who cannot see the difference, and low contrast defeats a much larger group than most people expect, including anyone reading outdoors or on an old screen. Add a word, a symbol in the text, or a label beside the color.
Fix the template, not the copy What you can change You control the template, the recording routine and the standard posting your team uses every week.
What to watch for Do not repair documents one at a time after someone complains. The next one arrives in the same condition, and the person who complained gets asked to complain again.
Your next step Take the template behind your most-used document or deck, give it real headings, described images and readable link text once, and tell the team it changed.
Private reflection, kept by you and not collected anywhere: in the material my team sends out, what have we been treating as a favor granted on request that is really part of making the thing usable, and whose expertise is missing from how we decide that?
Carry this forward Assistive technology is ordinary equipment: screen readers, magnification and text settings, captions and transcripts, speech input, keyboard-only and switch access, reading support, alternative keyboards, communication devices. Much of it is built into a phone or computer a person already owns, and many people use several together, or only on bad days.
What breaks these tools is equally ordinary: a heading made by enlarging bold text, a scanned page with no text underneath, a table drawn for looks, an image carrying information with no description, a link that says “click here”, color used as the only signal, a control that works only with a mouse.
Structure is the accessible part. Heading styles, real tables, named form fields, described images and text that is actually text are what a screen reader reads, and they are also what makes a long document usable for anyone skimming it on a phone.
The repair is upstream and cheap. Fixing a template, a recording routine or a standard posting once is worth more than repairing every document made from it afterward, and none of it waits for someone to disclose a disability.
A scenario about a recorded policy briefing posted with a scanned deck, a sorting exercise separating what removes a barrier from what creates one, and a knowledge check on where the largest gain comes from in a long document.
Open the last document or slide deck you sent to more than ten people. Check its headings, images, links and tables, fix what you can in it, then fix the template it came from so the next one starts right.
Browse and download only. Course notes are not typed or saved on this page.
Reset this lesson
Previous lesson Next lesson Participation and course completion in this program do not count toward DHS-required training credits unless management, a director, or DHS leadership expressly approves an exception.
