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
Establishing a New Braille File Standard with the eBRF | 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

Establishing a New Braille File Standard with the eBRF

Close up of an embosser printing a tactile graphic on a desk.

Imagine reading an interesting article or editing a hefty document with no way to navigate by page or heading, only able to scroll down one line at a time. Braille readers experience this tedium whenever they access digital braille files, making reading at home, in the classroom, and in the workplace a slow process. We think it’s time to take the braille file into the 21st century.  In collaboration with leaders from across the field, APH is developing a new, revolutionary braille file standard that will be accessible on both braille displays and embossers and will change the way students, teachers, and transcribers interact with braille and tactile graphics. We’re calling it the eBRF.

 

Why is there a need for an eBRF?

Today, the standard braille file accessible on braille displays and embossers is known as the Braille Ready File or BRF. This braille txt file is formatted entirely using just blank lines and spaces. As a result, readers can’t easily navigate through a big file or take advantage of other conveniences, like links for footnotes and endnotes. There are also no ways to join braille content and embossed graphics in the same electronic experience. The eBRF will solve these issues by providing braille text and tactile graphics in one file with enhanced navigation.

This new standard will build on information already being added by the transcriber. We don’t have to reinvent the workflow of getting the content from the transcriber to the braille reader to take advantage of this existing information. We just need to change how files are saved and opened. The ideal eBRF will be easy to create for transcribers, fit within an existing file standard, greatly improve the navigation experience, and empower users by bundling tactile graphics and braille.

 

What is the eBRF project?

The goal of the eBRF project is to create a new braille file standard that seamlessly contains both braille and tactile graphics. This interactive file will include formatting, like headings, tables, and glossaries. Enhanced navigation will allow students to effectively jump to sections, chapters, or pages and utilize links to access footnotes or other referenced material. Users can also decide the format they would like to view tables in, whether it be spatially or in a listed form. The eBRF will be easy to create and open and will work on single- and multi-line braille displays, and embossers can emboss both braille and graphics in a single print job. The eBRF, used with displays like our upcoming Dynamic Tactile Device (DTD), will display full pages of braille text, graphics, and even braille music, giving students access to instructional materials at the same time as their sighted peers. Read our DTD blog to learn more.

 

A field-wide effort

APH has been working collaboratively with international braille authorities and organizations,

such as The DAISY Consortium, National Library Service (NLS), Braille Authority of North America (BANA), International Council on English Braille (ICEB), Royal National Institute for the Blind (RNIB), Austrian Association for the Blind, Duxbury Systems, National Network for Equitable Library Service (NNELS), and many more, to seek their input and feedback.

 

Access for all

While APH is spearheading this work, it is ultimately the braille community that will own this standard. At present, we have received great feedback from our partners on the first draft of the eBRF. However, this draft is only the beginning. Many changes will be required before we get to the final specification. We hope to have the eBRF ready for all to access without too much delay as a new file standard is needed for those who utilize electronic braille.

“The effort that has been undertaken to create an eBRF format for braille reading is truly ground-breaking. With so much braille being read on electronic devices, efficient navigation is critical to the success of electronic braille for students, professionals, and even the casual braille reader,” said Judy Dixon, President, International Council on English Braille. This new eBRF standard will not only benefit users of the Dynamic Tactile Device, but it will also help braille readers everywhere read more efficiently regardless of the device used. It puts power in the hands of braille readers in a way that was not previously possible.

 

Stay tuned to aph.org and APH News for updates on the eBRF and the Dynamic Tactile Device.

Share this article.

Related articles

The APH logo and the DAISY Consortium logo.

APH Partners with DAISY Consortium on New Digital Braille Standard 

We’re pleased to announce our partnership with the DAISY Consortium to develop a brand-new, electronic braille standard! This development is...