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
Accessible Tools for Working from Home | 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

Accessible Tools for Working from Home

a man wearing glasses working on a monitor with increased magnification. text reads "Accessible tools for WFH. #AtHomeWithAPH"

Working from home (WFH) was once something that was a small possibility for some of us, maybe someday; but right now it’s the standard operating procedure for APH and for many others. With so many people working from home, it’s even more important to ensure that your content is accessible. We’ve put together some tips and resources from our internal Accessibility Hub!

Include Everyone in Your Meetings

Meetings … they must continue virtually, so make sure everyone can attend your meeting no matter what device they use. Unfortunately, several of the most popular conferencing tools have major accessibility problems.

To make sure that our virtual meetings are accessible, we’re using two different tools. For large meetings or meetings involving people from different departments, we use the Zoom Conferencing Platform for several reasons. It’s fully accessible with adaptive technology and is relatively simple to use overall. With Zoom, it’s easy to create or join a meeting, chat, share screens or ask questions. You can use the app for Windows, MacOS, iOS, Android, or the browser extensions for the most popular browsers.

For smaller groups, we also use Microsoft Teams. Teams is part of Office 365 and offers apps for MacOS, iOS, Windows, Linux, and Android. Teams is useful for making calls, sending short messages, document collaboration, and online meetings. You can create “teams” of people to interact with as a group or you can work one-on-one. You can set meetings through the app or through Outlook.

My personal experience has been almost universally good with Zoom while Teams, at times, provides challenges, especially if you have to cycle through lots of messages and documents from varying teams. Nevertheless, it’s a multifaceted tool that may solve some of your virtual meeting needs. Screen reader users also may benefit from this webinar from Vispero about JAWS and Microsoft Teams.

Document Accessibility

OK, so you’ve got the meetings part taken care of, but what about the documents you share during these meetings—are they accessible?

PowerPoint

Let’s start with one of the more difficult document types to make accessible, namely, PowerPoint documents. In our Accessibility Hub, we provide a list of guidelines for vendors and people making presentations for APH. On this page, we include a unique PowerPoint template that was created to enhance the overall accessibility of PowerPoint documents created with it. You can use this as a template to create accessible PowerPoints of your own.

PDF Documents

The mention of the word PDF often evokes a long collective sigh and groan from many screen reader users. “Please, not another PDF! Anything, literally anything but that!” But not anymore.

Our Accessibility Hub provides some methods for fixing some PDF files. However, let’s discuss some even more basic things not covered there.

First, please avoid sending PDF documents that are images of text. Images of text do not function as text when using a screen reader. Imagine trying to pay for something with a picture of a $100; would this image pass for payment? Always, without exception, avoid sending images of text and expecting anyone who is blind to read them.

Second, when in doubt, you can convert your document to a Microsoft Word document. While it’s ideal to be proficient in creating accessible PDFs—yes these do exist—sometimes you need something that is accessible and time is short. Try taking the text of the document and putting it into Word. Sure, you may lose formatting, but at least you’ll have a comparable document to provide to someone who is blind.

We have lots more information on accessible file types on our Accessibility Hub, check it out!

And as always, if you have questions about accessibility, you can send them to accessibility@aph.org

For more resources please check out our #AtHomeWithAPH resource list for free and accessible activities, tips, webinars, and more from APH, our partners, and the field at large. Have a free and accessible resource you would like us to include? Email us at communications@aph.org to tell us about it!

Share this article.

Related articles

Three students sit at a table and work on math problems in a classroom.

ADA Anniversary 2023: Celebrating an Accessible World

Thirty-three years ago, the Americans with Disabilities Act (ADA) was signed into law. The ADA protects against discrimination against people...