News & Events
Here you will find the latest news as well as upcoming and previous events.
If your organization is interested in training on the latest techniques for accessible format and inclusive publishing practices please contact us to discuss how we can assist you with your requirements. Read More
Liblouis is a free and open-source braille translation system that powers screen readers such as NVDA, JAWS to work with refreshable braille display in various languages, as well as a variety of conversion tools including the DAISY Pipeline. To facilitate accurate translation Liblouis has dedicated braille tables for each language that it supports.
If a language is supported by Liblouis, then it is possible to read create a braille version of a document in that language for use on a refreshable braille display such as an Orbit Reader, or embossed on braille paper.
Liblouis currently supports 79 languages, and many of those languages have braille tables for grade 1 and grade 2 (uncontracted and contracted) braille. You can find the list below.
Considering the importance of Liblouis in supporting braille usage on refreshable braille displays and for the production of braille books, the DAISY Consortium is seeking assistance in compiling a list of languages that are not yet supported in Liblouis and in which accessible books are currently published. We are also seeking feedback on languages that are currently supported, but in which the braille translation may not be correct.
Once we have identified these gaps we will be able to plan for filling them by adding braille tables of identified languages. If you are aware of any language in which accessible books are published and braille translation tables are not available or currently adequate please let us know:
- Chinese Mandarin
- Chinese Cantonese
- Unified English Braille
EPUB 3 has widely been adopted by the commercial publishing community as the chosen format for digital books, and is being increasingly utilized for accessible format delivery by educators and specialist libraries. The new version of the standard, EPUB 3.3, the related EPUB 1.1 accessibility specification and the updated version of EPUBCheck is imminent and we asked EPUB 3.3 editor and DAISY developer Matt Garrish; ‘What does this mean for accessible publishing?’
What is EPUB ?
The EPUB specification is a distribution and interchange format standard for digital publications and documents. There are huge opportunities for accessibility within the EPUB standard and indeed for born accessible publications. At DAISY we have some overview information to help you familiarize yourself with the standard itself and its component parts. In addition, the W3C maintain an overview document that provides a general introduction to the state of the format as of this revision.
Can We Expect Major Changes For Accessibility?
Neither the EPUB 3.3 nor the Accessibility 1.1 revisions represent major changes. Most of our efforts are focused on taking the work we’ve already done and moving the documents through the W3C process to make formal recommended specifications of them (i.e., to be fully recognized by W3C membership). EPUB 3.2 was published by the W3C publishing community group, so those documents did not have any formal standing (they didn’t have to go through W3C membership votes, they didn’t have to show independent implementations, etc.). So, EPUB 3.3 will formalize the standard.
So, EPUB 3.3 Doesn’t Look That Much Different?
Actually, EPUB 3.3 does not look at all like EPUB 3.2 from a document structure perspective. EPUB 3.2 was made up of five specifications (not including Accessibility 1.1 which is a separate specification):
- EPUB 3.2
- EPUB Packages 3.2
- EPUB Content Documents 3.2
- EPUB Open Container Format (OCF) 3.2
- EPUB Media Overlays 3.2
The authoring requirements from these specifications have now been merged into a single specification called EPUB 3.3, which is available in draft form right now at: https://www.w3.org/TR/epub-33/
EPUB 3.3 Splits Authoring From Reading Systems
The reading system requirements have now been split out into a new specification called, appropriately enough, EPUB Reading Systems 3.3 which is also a working draft: https://www.w3.org/TR/epub-rs-33/
Separating authoring and reading systems also has the side benefit of having fewer documents to take through the W3C process and better isolation when it comes to showing how the specifications can be implemented.
What Stage of the Process Have You Reached?
We’re just getting ready to wrap up the working draft stage and move to a candidate recommendation (the links above won’t change when we do). What this means is that our focus will change from revising the technical details of the specifications to showing that the specifications can be implemented by authors and reading systems. There is a testing task force working on creating tests for all the normative requirements and then during the candidate recommendation stage we’ll be looking for implementations to prove the tests.
How Does This Affect the EPUB Accessibility 1.1 Specification?
The Accessibility 1.1 revision is very similar to EPUB 3.3 in that there are not a lot of major changes from 1.0. The new version incorporates the text improvements that were made to EPUB 1.0 as part of making it an ISO standard (ISO/IEC 23761:2021), but those changes were editorial in nature (i.e., the IDPF and ISO specifications read differently, but have the same base requirements).
The most significant change that people will need to be aware of is that we’re now allowing conformance to adapt to the latest versions of WCAG 2 as they become recommendations (the Accessibility 1.0 specification only allowed conformance to WCAG 2.0). You still have to minimally meet WCAG 2.0 Level A to meet the base requirements of our specification, but publishers are now encouraged to conform to the latest recommended version of WCAG 2 (which is 2.1 right now, but 2.2 is coming). Level AA conformance is also recommended. This means that there is now a new conformance identifier that publishers will have to use in the metadata that adapts to what WCAG version and level you have met. The details are explained here: https://www.w3.org/TR/epub-a11y-11/#sec-conf-reporting-pub.
Other minor tweaks include the separation of the page navigation and media overlay objectives into separate sections to make them easier to read, but they aren’t different from the 1.0 specification.
Will EPUBCheck be Updated to Support EPUB 3.3?
The next version of EPUBCheck, the free command-line EPUB checking tool, will provide complete support for checking conformance to the EPUB 3.3 standard. The Public Beta version is due out shortly.