Tag replacement
Formatting that assistive technology misreads is swapped for tags it understands; layout tables are rebuilt with <div> and <span>.
Loading the case study
Patent · US 9,268,753 B2 · Apollo Education Group
A system that reads a document the way a screen reader would, finds what will be misread, and automatically produces an accessibility-enabled version alongside the original.
Co-inventor, with Heidi Jungel
Oct 24, 2011 · Feb 23, 2016
Apollo Education Group (later The University of Phoenix)
01 — The problem
<table>
<tr>
<td><b>Name *</b></td>
<td><input></td>
</tr>
</table>“Table with 2 columns and 1 row. Name star. Edit text.”
<div class="row">
<label for="name">Name</label>
<input id="name"
aria-required="true">
</div>“Name, required, edit text.”
02 — How it works
The system first analyzes a document for tags and patterns known to trip up specific assistive technologies, from layout tables to formatting applied without CSS to controls that can’t be reached by keyboard. It builds an element-based model of the page, then produces a second, accessibility-enabled version, either by modifying the original or generating a new one. The server stores both and returns whichever a request calls for.
03 — What gets added
Formatting that assistive technology misreads is swapped for tags it understands; layout tables are rebuilt with <div> and <span>.
Elements get classes, styled through generated CSS, and ids so they can be referenced, such as a heading id built from its text.
aria-required, aria-labelledby, aria-describedby, aria-live, aria-atomic and aria-relevant are added where the page needs them.
Links without a title get one generated automatically.
Design-only images get alt="" so a screen reader skips them instead of reading the file name.
Labels, fieldsets, legends and landmarks are added so the page can be navigated by keyboard.
Shortcuts such as Esc to close a pop-up window.
The system can produce a draft for a person to review and correct before it ships.
04 — What’s claimed
The independent claims describe a server that keeps a first version of a document, generates an accessibility-enabled version with features the first lacked for a particular assistive technology, stores it, and answers each request with either version. A parallel claim covers the same steps as instructions on computer-readable media.
The dependent claims narrow it to tag replacement, parsing into a DOM-style tree, generated style sheets, modifying versus copying the original, adding labels and identifiers, keyboard navigation between elements, applying the process across a whole site, and running it in the browser or on request.
05 — Why it still matters
The idea underneath the patent is the one I still design by: accessibility belongs in the system, applied automatically and consistently, with people reviewing the result, rather than retrofitted page by page. It is the same thinking behind WCAG 2.1 AA being built into every Radial component.
Source: US 9,268,753 B2 on Google Patents. Google lists the patent as active with an adjusted expiry of April 13, 2034; that status is Google’s assumption, not a legal finding.