Deprecated: preg_match(): Passing null to parameter #2 ($subject) of type string is deprecated in /sites/aph-dev.prolificdigital.io/files/web/app/plugins/wp-oauth-server/includes/functions.php on line 726

Deprecated: preg_match(): Passing null to parameter #2 ($subject) of type string is deprecated in /sites/aph-dev.prolificdigital.io/files/web/app/plugins/wp-oauth-server/includes/functions.php on line 726

Deprecated: preg_match(): Passing null to parameter #2 ($subject) of type string is deprecated in /sites/aph-dev.prolificdigital.io/files/web/app/plugins/wp-oauth-server/includes/functions.php on line 726

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-smushit domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/aph-dev.prolificdigital.io/files/web/wp/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/aph-dev.prolificdigital.io/files/web/wp/wp-includes/functions.php on line 6121

Deprecated: Creation of dynamic property WC_Gateway_EOT::$instructions is deprecated in /sites/aph-dev.prolificdigital.io/files/web/app/plugins/woocommerce-gateway-eot/woocommerce-gateway-eot.php on line 103

Deprecated: Creation of dynamic property WP_User_Taxonomy::$tax_singular is deprecated in /sites/aph-dev.prolificdigital.io/files/web/app/plugins/wp-user-groups/wp-user-groups/includes/classes/class-user-taxonomy.php on line 98

Deprecated: Creation of dynamic property WP_User_Taxonomy::$tax_plural is deprecated in /sites/aph-dev.prolificdigital.io/files/web/app/plugins/wp-user-groups/wp-user-groups/includes/classes/class-user-taxonomy.php on line 99

Deprecated: Creation of dynamic property WP_User_Taxonomy::$tax_singular_low is deprecated in /sites/aph-dev.prolificdigital.io/files/web/app/plugins/wp-user-groups/wp-user-groups/includes/classes/class-user-taxonomy.php on line 100

Deprecated: Creation of dynamic property WP_User_Taxonomy::$tax_plural_low is deprecated in /sites/aph-dev.prolificdigital.io/files/web/app/plugins/wp-user-groups/wp-user-groups/includes/classes/class-user-taxonomy.php on line 101

Deprecated: Creation of dynamic property WP_User_Taxonomy::$tax_singular is deprecated in /sites/aph-dev.prolificdigital.io/files/web/app/plugins/wp-user-groups/wp-user-groups/includes/classes/class-user-taxonomy.php on line 98

Deprecated: Creation of dynamic property WP_User_Taxonomy::$tax_plural is deprecated in /sites/aph-dev.prolificdigital.io/files/web/app/plugins/wp-user-groups/wp-user-groups/includes/classes/class-user-taxonomy.php on line 99

Deprecated: Creation of dynamic property WP_User_Taxonomy::$tax_singular_low is deprecated in /sites/aph-dev.prolificdigital.io/files/web/app/plugins/wp-user-groups/wp-user-groups/includes/classes/class-user-taxonomy.php on line 100

Deprecated: Creation of dynamic property WP_User_Taxonomy::$tax_plural_low is deprecated in /sites/aph-dev.prolificdigital.io/files/web/app/plugins/wp-user-groups/wp-user-groups/includes/classes/class-user-taxonomy.php on line 101

Deprecated: Creation of dynamic property FacetWP_Conditional_Logic_Addon::$rulesets is deprecated in /sites/aph-dev.prolificdigital.io/files/web/app/plugins/facetwp-conditional-logic/facetwp-conditional-logic.php on line 44

Deprecated: Creation of dynamic property FacetWP_Conditional_Logic_Addon::$admin_i18n is deprecated in /sites/aph-dev.prolificdigital.io/files/web/app/plugins/facetwp-conditional-logic/facetwp-conditional-logic.php on line 46

Deprecated: Creation of dynamic property Teacher_Invite_Email::$group_id is deprecated in /sites/aph-dev.prolificdigital.io/files/web/app/themes/mightily/emails/class-teacher-invite-email.php on line 40

Deprecated: Creation of dynamic property Teacher_Invite_Email::$user_exists is deprecated in /sites/aph-dev.prolificdigital.io/files/web/app/themes/mightily/emails/class-teacher-invite-email.php on line 42

Deprecated: Creation of dynamic property EOT_Gateway_Email::$group_id is deprecated in /sites/aph-dev.prolificdigital.io/files/web/app/themes/mightily/emails/class-eot-gateway-email.php on line 44

Deprecated: Creation of dynamic property Teacher_Request_Email::$eot_user_id is deprecated in /sites/aph-dev.prolificdigital.io/files/web/app/themes/mightily/emails/class-teacher-request-email.php on line 44

Deprecated: Creation of dynamic property Weekly_Order_Review_Email::$user is deprecated in /sites/aph-dev.prolificdigital.io/files/web/app/themes/mightily/emails/class-weekly-order-review-email.php on line 40

Deprecated: APH\Roles::isFQAUser(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead in /sites/aph-dev.prolificdigital.io/files/web/app/themes/mightily/classes/APH/Roles.php on line 46
Why eBraille is a Braille-Based Document Type | American Printing House
Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\Handler\GuzzleV6\GuzzleHandler::__construct(): Implicitly marking parameter $client as nullable is deprecated, the explicit nullable type must be used instead in /sites/aph-dev.prolificdigital.io/files/web/app/plugins/amazon-s3-and-cloudfront-pro/vendor/Aws3/Aws/Handler/GuzzleV6/GuzzleHandler.php on line 23

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\HandlerList::__construct(): Implicitly marking parameter $handler as nullable is deprecated, the explicit nullable type must be used instead in /sites/aph-dev.prolificdigital.io/files/web/app/plugins/amazon-s3-and-cloudfront-pro/vendor/Aws3/Aws/HandlerList.php on line 53

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\HandlerList::interpose(): Implicitly marking parameter $fn as nullable is deprecated, the explicit nullable type must be used instead in /sites/aph-dev.prolificdigital.io/files/web/app/plugins/amazon-s3-and-cloudfront-pro/vendor/Aws3/Aws/HandlerList.php on line 249

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\JmesPath\AstRuntime::__construct(): Implicitly marking parameter $parser as nullable is deprecated, the explicit nullable type must be used instead in /sites/aph-dev.prolificdigital.io/files/web/app/plugins/amazon-s3-and-cloudfront-pro/vendor/Aws3/JmesPath/AstRuntime.php on line 14

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\JmesPath\AstRuntime::__construct(): Implicitly marking parameter $fnDispatcher as nullable is deprecated, the explicit nullable type must be used instead in /sites/aph-dev.prolificdigital.io/files/web/app/plugins/amazon-s3-and-cloudfront-pro/vendor/Aws3/JmesPath/AstRuntime.php on line 14

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\JmesPath\TreeInterpreter::__construct(): Implicitly marking parameter $fnDispatcher as nullable is deprecated, the explicit nullable type must be used instead in /sites/aph-dev.prolificdigital.io/files/web/app/plugins/amazon-s3-and-cloudfront-pro/vendor/Aws3/JmesPath/TreeInterpreter.php on line 17

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\JmesPath\Parser::__construct(): Implicitly marking parameter $lexer as nullable is deprecated, the explicit nullable type must be used instead in /sites/aph-dev.prolificdigital.io/files/web/app/plugins/amazon-s3-and-cloudfront-pro/vendor/Aws3/JmesPath/Parser.php on line 38

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\JmesPath\Parser::parseWildcardObject(): Implicitly marking parameter $left as nullable is deprecated, the explicit nullable type must be used instead in /sites/aph-dev.prolificdigital.io/files/web/app/plugins/amazon-s3-and-cloudfront-pro/vendor/Aws3/JmesPath/Parser.php on line 258

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\JmesPath\Parser::parseWildcardArray(): Implicitly marking parameter $left as nullable is deprecated, the explicit nullable type must be used instead in /sites/aph-dev.prolificdigital.io/files/web/app/plugins/amazon-s3-and-cloudfront-pro/vendor/Aws3/JmesPath/Parser.php on line 263

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\JmesPath\Parser::next(): Implicitly marking parameter $match as nullable is deprecated, the explicit nullable type must be used instead in /sites/aph-dev.prolificdigital.io/files/web/app/plugins/amazon-s3-and-cloudfront-pro/vendor/Aws3/JmesPath/Parser.php on line 322

Deprecated: DeliciousBrains\WP_Offload_Media\Providers\Storage\Streams\AWS_S3_Stream_Wrapper::register(): Implicitly marking parameter $cache as nullable is deprecated, the explicit nullable type must be used instead in /sites/aph-dev.prolificdigital.io/files/web/app/plugins/amazon-s3-and-cloudfront-pro/classes/providers/storage/streams/aws-s3-stream-wrapper.php on line 21

Deprecated: DeliciousBrains\WP_Offload_Media\Aws3\Aws\S3\StreamWrapper::register(): Implicitly marking parameter $cache as nullable is deprecated, the explicit nullable type must be used instead in /sites/aph-dev.prolificdigital.io/files/web/app/plugins/amazon-s3-and-cloudfront-pro/vendor/Aws3/Aws/S3/StreamWrapper.php on line 97
Skip to main content Skip to main menu

Why eBraille is a Braille-Based Document Type

A student sits at a desk, hands on the monarch exploring the navigation buttons.

One of the biggest early questions about eBraille was whether the standard would be print-based, like DOCX or EPUB, or braille-based, like BRF or PEF. Both approaches are used today so it’s possible to know the benefits and drawbacks of each approach. This question was much discussed when the process of creating eBraille started and it’s important that people know why we took the approach that we did. 

Translated automatically via a screen reader or braille display, there are many advantages to utilizing print-based file types. These file types usually require less training than a braille-based file type, which requires knowing braille and braille formatting. The translation is handled using tables that are usually provided either by Duxbury or LibLouis, which are usually very good. When there is an issue with the translation, it is typically because of the quality of the file being translated. 

The most obvious problem is that sometimes print-based materials, especially those that are prepared by the publisher or by an entity that is not familiar with the requirements of braille, will use pictures of text instead of text. Used instead of a set of materials like a timeline, or in place of diacritical marks or mathematical notation, this material is often inaccessible to whatever software is handling the translation and will be skipped in the automatic braille rendition. 

The main problem, however, is proper translation of technical material like science, math, and chemistry. Requiring precise representations of the information that needs to be translated often means utilizing MathML or other similar methods for describing mathematical notation, like LaTeX. However, creating MathML and LaTeX often requires even more training and can take more time than just providing the correct braille translation. 

An additional problem with relying on an automatic translation is that translation tables receive updates which aren’t always applied to the hardware and software that is processing the translation. This can lead to a situation where one person is using one kind of hardware and getting one translation of the material, while another person is using a different kind of hardware and getting a completely different translation. This may be fine for casual reading, but it can be detrimental for high stakes situations like tests, textbooks, and other educational activities. Automatic translations are also insufficient for music and the availability and quality of tables varies throughout the world.  

While there are drawbacks to print-based materials, we could potentially correct them by having people help to correct issues that are identified. The problem is that there are braille regions that already utilize this basic system and the results don’t really change outcomes for students. In some European countries, they provide each student with a single-line braille display and then give them digital print-based versions of their textbooks and hardcopy tactile graphics. This system then leads to costs and delays that are comparable to what we have in the United States with our braille-based system. 

It is for all these reasons that the working group pursued a braille-based system. By making eBraille a primarily braille-based document type, we’re keeping an emphasis on the need for a correct, precise, and consistent translation. We’re also using a workflow and the talents of the same transcribers, teachers, and braillists that have been providing braille to braille users for many years, so that we don’t have to create new software, methods, or workflows just to accommodate the file type. 

eBraille will be another option going forward. Adult braille users will be able to decide for themselves whether they would prefer an automatic translation with a print file, a formatted braille document like BRF, or the new eBraille file type. Students will benefit from these same options. 

The important thing is that we keep making braille available by whatever means are available to us. Braille is not going away. If anything, it is only going to become more readily available and less expensive as we continue to take advantage of the latest technological innovations. Let’s keep making braille! 

Share this article.

Related articles

Two students, a boy and a girl sit ont he couch together reading the braille book.

Braille Tales Grows Readers Both in and Outside of the Classroom

At APH, our Braille Tales books help introduce braille to young readers. By giving blind or low vision students books...

A bridge of bright blue and orange appears above the words

Building an Easy Transition to Braille Learning with Braille Bridge

Learning to read braille as an adult can be a daunting task. The majority of early braille learning materials often...

A student with glasses leans in to examine a textbook

Louis and the AMP Database: Supporting Students and the Field

The Louis Database The concept of sharing information between braille-producing agencies dates back to the 1950s, when APH used a...