What is a NIMAS fileset?
A NIMAS fileset is the source package a publisher submits under the National Instructional Materials Accessibility Standard. It contains a valid DTBook XML file marked up to the NIMAS DTD, a package file (OPF) with the title's metadata, and the full-resolution images referenced by the text. Accessible Media Producers convert that source into braille, large print, audio or digital text for students with print disabilities.
What source files do you need to start?
A text-based print PDF with high-resolution images, including the cover page. Before production begins our team checks that the source is genuinely text-based and suitable for conversion; scanned or image-only PDFs need a different approach, and we tell you that up front rather than after invoicing.
Do you upload titles to NIMAC, or do we?
We do. We hold vendor access to the NIMAC portal, upload the fileset on your behalf, and follow up on any validation issues until each title is duly certified.
Who writes the alt text for images?
We do. Our team drafts descriptions for the images that carry instructional meaning and sends them to you for correction or approval. Production of the fileset only starts once you have signed off on the alt text.
What is the difference between NIMAS and an accessible PDF?
NIMAS is a source format, intended to be converted into student-ready formats by an Accessible Media Producer. An accessible PDF conforming to PDF/UA (ISO 14289) is an end-user format, opened directly by the reader with assistive technology. Many publishers need both, which is why we produce them from the same set of source files.
Do you provide a VPAT or an ACR?
Yes. A VPAT is the template; an Accessibility Conformance Report is the completed document. We issue an ACR per product in the requisite VPAT format, covering WCAG 2.x Level AA, Section 508 and EN 301 549 as applicable.
Does the European Accessibility Act apply to us if we are not based in the EU?
Almost certainly, if you sell into the EU. The Act is scoped by where a product or service is offered rather than where the company is registered, so a publisher based in India, the United States or Australia selling e-books into EU retail platforms falls within it. The obligation also runs down the supply chain to distributors, retailers, reading software and metadata aggregators.
What makes an e-book compliant with the EAA?
In practice: an accessible EPUB 3 conforming to EPUB Accessibility 1.1, which applies the WCAG Level AA criteria inside a publication, plus accessibility metadata that describes it. That metadata has to exist in two places — schema.org properties in the EPUB package document, and the corresponding accessibility codes in the ONIX record sent to distributors and retailers.
Do you work beyond documents?
Yes. We audit and remediate web applications against WCAG 2.x Level AA, run user-flow and assistive-technology testing, advise on accessibility programme strategy, train client teams, and re-test on an ongoing cadence.