The Inadvertent Accessible Content Architect
Skip other details (including permanent urls, DOI, citation information)
This work is protected by copyright and may be linked to without seeking permission. Permission must be received for subsequent distribution in print or electronically. Please contact firstname.lastname@example.org for more information. :
For more information, read Michigan Publishing's access and usage policy.
Building internal specifications for EPUB and HTML while working on industry standards groups forces one to ask what the purpose of each tag and attribute is, especially when working on aspirational specifications. Often, the only immediate application is Accessibility. While I can imagine other implementations of magical specifications, it will take the publishing industry using them in force and a little help from user agents and reading systems to see these ideas in play. This forces a hyper-awareness of content structure, apart from just a description of content, apart from style, leading us to become inadvertent champions of accessibility. Along the way, I have discovered, that, as the accessible community has been telling us all along, this makes sense. Building accessible content is actually a better way to approach content architecture.
Download Slides (PDF)