Use of the eaa-microenterprise property

  • This topic has 1 reply, 2 voices, and was last updated 1 week, 3 days ago by APLN Moderator.
Viewing 2 posts - 1 through 2 (of 2 total)
Use of the eaa-microenterprise property thread
Author Posts

The small publisher that I work with is exempt from the EAA legislation, but they are trying to make all their epub books conform to  the EAA  requirements.  Using ACE and ACE Smart gives the meta properties to include in the opf file, and that is now built into the work flow.

But the question has now come up if we should also include this item in the opf file:

<meta property=”a11y:exemption”>eaa-microenterprise</meta>

because the publisher is not CGA  certified.


APLN Moderator

Hi Jim,

This is a very interesting question!

I don’t believe a publisher has to be GCA certified to produce accessible ebooks. In this case, you would not include certification metadata in the OPF, but include all other applicable accessibility metadata, such as accessibility features, access modes, hazards, accessibility summary, etc. In the ONIX for the ebook, it can be noted which EPUB spec the book conforms to and the codes for the accessibility features the book includes.

If any ebooks from this publisher aren’t accessible, then you can add the following metadata in the OPF:

<meta property="dcterms:conformsTo">none</meta>
<meta property="a11y:exemption">eaa-microenterprise</meta>

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.

Want to join the discussion?

a wooden table with a white keyboard on top, and a persons hand writing on a piece of paper

View our current resources