Introduction to LibreOffice — Overview and Navigation

Siena introduced LibreOffice as a free, open-source office suite comparable to OpenOffice but more accessible on both Mac and Windows (and Linux). She demonstrated the LibreOffice Start Center, navigating through its components using the Tab key.

• Details
  • Siena: Described LibreOffice as similar to OpenOffice but more accessible; noted a sighted friend uses it on Linux.
  • Siena: Navigated the Start Center, identifying components: Writer (word processor), Calc (spreadsheet), Impress (presentations), Draw, Math Formula, and Base (database).
  • Siena: Demonstrated filtering recent documents and clearing the recent documents list.
  • Siena: Noted that LibreOffice occasionally shows a “not responding” state on startup and may prompt about default file format registration.
• Conclusion
  • LibreOffice is a robust, free office suite with components covering word processing, spreadsheets, presentations, drawing, math, and databases.
  • It is accessible with JAWS on Windows and VoiceOver on Mac.

LibreOffice Writer — Document Creation and Formatting

Siena opened LibreOffice Writer, typed a sample document, and explored the menu bar structure, demonstrating how to navigate menus using the ALT key and arrow keys.

• Details
  • Siena: Typed a title (“Test LibreOffice Writer Document”) and a sample sentence (“The quick brown fox jumps over the lazy dog…”) to demonstrate basic text entry.
  • Siena: Navigated the File, Edit, View, Insert, Format, and Styles menus, describing available options such as page breaks, image insertion, comments, line spacing, bullets and numbering, watermarks, alt text for images, and more.
  • Siena: Noted that keyboard shortcuts in LibreOffice are largely equivalent to Microsoft Word.
  • Liz: Asked how formatting options are accessed without clicking, as she had only used visual interfaces before.
  • Siena: Explained the ALT key activates the menu bar, and arrow keys navigate through menus and submenus.
• Conclusion
  • LibreOffice Writer’s menu structure is navigable via keyboard and screen reader in a manner very similar to Microsoft Word.
  • Standard shortcuts (Ctrl+S, Ctrl+P, etc.) function as expected.

LibreOffice Writer — Saving, File Formats, and Export Options

Siena demonstrated saving a document for the first time, exploring the wide range of available file formats in both the Save As and Export dialogs.

• Details
  • Siena: Saved the document as an ODT (Open Document Text) file by default, explaining ODT stands for Open Document Format Text.
  • Siena: Demonstrated the Save As dialog, listing 18 available formats including ODT, DOCX (Word 2010–365), DOC (Word 97–2003), RTF, HTML, Markdown, plain text, EPUB, PDF, and XML.
  • Siena: Highlighted the password protection feature when saving, noting Google Docs does not recognize password-protected files.
  • Siena: Demonstrated the Export dialog, showing formats such as EPUB, PDF, XHTML, and MediaWiki.
  • Liz: Asked whether ODT files are widely accepted and whether PDF would be safer for sending documents.
  • Siena: Recommended saving as Word 2010–365 (.docx) for maximum compatibility, or PDF for universal readability.
  • Lily: Asked whether LibreOffice could save documents as Word files, which Siena confirmed.
  • Lily: Noted this would be very useful for her volunteer work at a church library, where cross-platform formatting issues between Mac and Windows have been a problem.
  • Siena: Confirmed LibreOffice is accessible on both Mac and Windows, making it a strong cross-platform solution.
  • Ali: Noted the GPG key encryption option visible in the Save dialog and offered to explain it.
• Conclusion
  • LibreOffice Writer supports 18 save formats and multiple export formats, including full compatibility with current Microsoft Word (.docx).
  • For sending documents to others, .docx or PDF are the recommended formats.
  • Password protection is available natively in LibreOffice.

Explanation of GPG Key Encryption

Ali explained the GPG key option that appeared in the LibreOffice Save dialog.

• Details
  • Ali: Defined GPG (GNU Privacy Guard) as a cryptographic key used to encrypt, decrypt, and digitally sign data, ensuring files can only be read by their intended recipient and verifying the content genuinely originates from the claimed sender.
  • Ali: Read the definition from his Braille display.
• Conclusion
  • GPG encryption is an advanced security feature available in LibreOffice for protecting sensitive documents.

LibreOffice as a Free Alternative to Microsoft Office 365

A broader discussion emerged about the value of LibreOffice as a subscription-free alternative to Microsoft Office 365.

• Details
  • Ali: Stated he uses a PC but dislikes the Microsoft suite of products and does not want to pay for Office 365.
  • Siena: Shared that her vendor suggested installing Microsoft 365 on her new computer, but she declined, preferring Google Docs and LibreOffice.
  • Ali: Expressed frustration with the accumulation of subscription costs across multiple services.
  • Siena: Noted LibreOffice works on both Windows and Mac, eliminating the need for separate licenses, and is less of a memory hog than Word.
  • Lily: Agreed LibreOffice is powerful for a free tool and relevant to her volunteer cataloging work.
• Conclusion
  • LibreOffice is a viable, cost-free alternative to Microsoft Office 365 for users on Windows, Mac, and Linux.
  • Cross-platform compatibility and accessibility make it particularly attractive for blind and low-vision users.

Braille Literacy and Assistive Technology Workflows

A candid discussion arose about the role of Braille displays in productivity and whether working without one is feasible.

• Details
  • Ali: Expressed that he could not imagine working efficiently without a Braille display, and wondered how users who never learned Braille manage complex tasks.
  • Lily: Explained she works effectively with a screen reader only, noting the only challenges were math equations and French pronunciation.
  • Siena: Agreed French is better read on a Braille display unless a French voice is installed.
  • Macara: Affirmed Lily’s point, noting it is a very human tendency to find it hard to imagine ways of doing things outside one’s own experience; also confirmed Braille was essential for math.
  • Siena: Shared she began using Braille displays around Grade 11 and finds them most valuable in meetings where she needs to turn off speech.
  • Ali: Acknowledged he may be viewing the issue through his own lens and appreciated the perspective.
  • Lily: Drew a parallel to navigation — she could not imagine traveling in Toronto the way Ali does, just as he cannot imagine working without a Braille display; both approaches stem from lived experience.
• Conclusion
  • Both Braille-display-assisted and screen-reader-only workflows are valid and effective depending on the individual’s background and needs.
  • There is no single “right” way to use assistive technology.

LibreOffice Calc — Spreadsheet Exploration

Siena opened LibreOffice Calc and collaboratively built a sample monthly budget spreadsheet with participant input, exploring accessibility with JAWS.

• Details
  • Siena: Opened Calc from the LibreOffice Start Center and navigated the spreadsheet using arrow keys, explaining columns (letters) and rows (numbers).
  • Siena: Created a “Monthly Expenses” spreadsheet with columns for Month, Phone Bill, Credit Card Bill, Gas, Electricity (Hydro), Phone/TV/Internet, Tim Hortons, Food Orders, Monthly Subscriptions, and a Total column.
  • Liz: Requested a simple budget example with a total at the bottom, noting she had not used a spreadsheet in 15 years.
  • Liz: Asked about defining field types (text vs. numeric) and how to create a SUM function.
  • Siena: Entered sample values for January across all expense categories.
  • Siena: Looked up the SUM formula syntax and successfully used =SUM(D4:L4) via Alt+= to calculate the January total, arriving at $1,460.57.
  • Participants contributed sample expense figures and discussed real-life costs (hydro, Tim Hortons, Uber Eats, subscriptions).
  • Liz: Noted she saves on hydro by keeping lights off.
  • Ali and Lily: Shared they also do not turn on lights, as they do not need them.
• Conclusion
  • LibreOffice Calc functions similarly to Microsoft Excel, including SUM formulas using the same syntax.
  • The Alt+= shortcut auto-generates a SUM formula in LibreOffice Calc.
  • The spreadsheet is navigable and usable with JAWS.

Downloading and Installing LibreOffice on Mac

Lily asked about how to obtain LibreOffice on a Mac.

• Details
  • Lily: Asked whether LibreOffice can be downloaded from the Mac App Store or must be obtained from the LibreOffice website.
  • Siena: Confirmed it must be downloaded from the LibreOffice website (libreoffice.org), not the App Store.
  • Siena: Noted that Mac security settings must allow apps from “App Store and identified developers,” which is the recommended setting.
  • Ali: Confirmed LibreOffice qualifies as an identified developer, so there should be no installation issues.
• Conclusion
  • LibreOffice for Mac is downloaded from libreoffice.org.
  • Mac security settings should be set to “App Store and identified developers” to allow installation.

Upcoming Sessions and Closing Remarks

Siena wrapped up the session and announced upcoming events.

• Details
  • Siena: Announced an afternoon workshop on June 10th and Techstravaganza 2.0 on June 11th.
  • Siena: Mentioned she plans to cover LibreOffice on Mac in a future Techstravaganza 2.0 session.

Find out What’s Coming Up on Future Workshops at the Following link: https://techstravaganza.ca/2026/05/13/updated-as-of-may-13-2026-whats-coming-up-on-techstravaganza/

Contact the team:

Email: support@techstravaganza.ca

Like us on Facebook: https://www.facebook.com/profile.php?id=61578990010675

Follow the Show:

Tunein: http://tun.in/pxXlj

On Apple Podcasts: https://podcasts.apple.com/ca/podcast/techstravaganza/id1846930800

On Audible: https://podcasts.apple.com/ca/podcast/techstravaganza/id1846930800

On iHeart: https://www.iheart.com/podcast/269-techstravaganza-301161434/

On Spotify: https://spotify.link/vVGru9nKBXb

TalkBack Tutorial: Android Home Screen Navigation

Samantha led the main tutorial segment, demonstrating how to navigate an Android phone using TalkBack, with contributions from Siena and Jackie.

• Details
  • Samantha: Introduced herself as a full-time Android user with a Google Pixel 10 and Google Pixel Watch 4, previously an iPhone user.
  • Samantha: Explained how to activate TalkBack out of the box by holding the power button and then both volume keys for 3–5 seconds.
  • Samantha: Described the home screen structure (e.g., “Home screen 1 of 3”) and how to access the full apps list by swiping down to “Apps List” and double-tapping.
  • Samantha: Demonstrated that apps in the list are displayed alphabetically and can be double-tapped to open or added to the home screen via the shortcut menu.
  • Samantha: Discovered live during the tutorial that individual timers and alarms can be added directly to the home screen via the shortcut menu — a feature new to her.
  • Siena: Noted she typically navigated via the app switcher rather than adding items to the home screen.
  • Samantha: Explained the three virtual navigation buttons — Back, Home, and Overview (equivalent to iOS app switcher) — and noted that app focus wraps around the screen edges.
  • Samantha: Described angle gestures for navigation: swipe up-then-left for Home, swipe down-then-left for Back, swipe up-then-right for TalkBack menu, and swipe left-then-up for Overview/Recents.
  • Siena: Demonstrated the gestures live on her Motorola, confirming they work the same way.
  • Jackie: Noted she primarily uses a physical keyboard with her Samsung Galaxy rather than touch gestures.
• Conclusion
  • TalkBack navigation shares some similarities with VoiceOver but has distinct angle gestures.
  • App wrapping on Android was highlighted as a convenience feature.
  • Every day is a learning experience, even for experienced users.

Google Pixel Camera Guidance Feature

Samantha briefly mentioned a unique accessibility feature on Google Pixel devices for taking photos.

• Details
  • Samantha: Explained that the Google Pixel guides users when taking photos using speech, helping blind users frame shots.
  • Siena: Noted she has not yet tried taking photos with her Motorola.
  • Samantha: Suggested that on Motorola, photo-taking involves more guesswork compared to the Pixel’s guided experience.
• Conclusion
  • The Pixel’s guided camera feature was highlighted as a notable accessibility advantage over other Android manufacturers.

Android vs. iOS: Reasons for Switching and Platform Comparison

Jackie asked Samantha why she switched from iPhone to Android, prompting a broader comparison discussion.

• Details
  • Samantha: Cited customizability, the feel of the device, TalkBack guidance, and better accessibility of certain apps (e.g., Telegram, Facebook/Meta) on Android as reasons for switching.
  • Samantha: Noted that Meta tends to break its Android app less frequently than its iOS app, and bug fixes are faster on Android.
  • Samantha: Also mentioned boredom with iOS after 10 years, notification issues on iPhone, and the increasing cost of iPhones.
  • Jackie: Agreed that Meta apps are consistently broken on iPhone.
  • Samantha: Noted that Google Pixel users receive Android system updates first, while Samsung and Motorola users may wait 4–5 months.
  • Siena: Confirmed that Motorola has less intrusive bloatware than Samsung, staying mostly in its own folder.
  • Samantha: Recommended the Pixel as the best Android choice for timely updates and a cleaner experience.
  • Ali: Expressed growing interest in trying a Pixel as a secondary device but acknowledged hesitation about the initial setup process.
  • Samantha: Offered to lend Ali a Google Pixel 7 for testing; Ali declined for now but expressed interest in a private one-on-one session with Samantha.
• Conclusion
  • Google Pixel was recommended as the best Android option for accessibility users due to timely updates and stock Android.
  • Ali and Samantha agreed to arrange a private session to explore Android further.

TalkBack Granularity and Gesture Customization

Samantha and Siena demonstrated how to customize TalkBack gestures and use granularity navigation.

• Details
  • Samantha: Explained that default granularity navigation uses three-finger swipe up/down, cycling through characters, words, links, headings, and controls (equivalent to iOS form fields).
  • Samantha: Demonstrated navigating to TalkBack Settings > Controls > Gestures to customize gesture assignments using radio buttons.
  • Siena: Shared that she had customized gestures for toggling speech on/off and activating Braille screen input.
  • Siena: Demonstrated the TalkBack Practice Gestures mode (activated via four-finger double-tap), which announces what each gesture does — similar to VoiceOver Help on iOS.
  • Ali: Noted a preference for the term “commands” over “gestures.”
  • Samantha: Acknowledged the terminology difference and noted VoiceOver on iOS also now supports gesture customization, though Android’s implementation is more flexible.
  • Siena: Recalled that iOS gesture customization was introduced around iOS 14–16; Ali suggested it may have been earlier.
• Conclusion
  • TalkBack offers extensive gesture customization, which is a significant accessibility advantage.
  • The Practice Gestures mode is a useful learning tool for new Android users.

Braille Display Compatibility with TalkBack on Android

Siena raised an issue she had experienced with Braille display output on her Motorola.

• Details
  • Siena: Noted that regardless of whether she uses her Focus or Mantis Q40 Braille display, TalkBack allows keyboard input but does not display Braille output.
  • Samantha: Suggested Siena consult Nick, who also uses a Motorola and Mantis, for guidance.
  • Samantha: Proposed that Siena could do a future tutorial specifically on Braille display commands with Android.
• Conclusion
  • The Braille display output issue on Motorola remains unresolved; Nick was identified as a resource.
  • A future Braille display tutorial on Android was proposed.

Podcast Listening Options for Android / Cross-Platform Strategy

Ali raised the question of finding a cross-platform podcast solution in preparation for potentially adopting an Android device.

• Details
  • Ali: Noted that some apps he uses (e.g., EyeCatcher, Overcast) are iOS-exclusive and asked for cross-platform alternatives.
  • Samantha: Suggested Spotify, noting it is accessible on Android; Ali declined as he does not use Spotify.
  • Samantha: Confirmed Apple Music is available and accessible on Android.
  • Ali: Noted he uses YouTube Premium and prefers YouTube Music as his primary platform.
  • Samantha: Confirmed YouTube Music is accessible on Android and that she and Nick have both tested it.
  • Macara: Suggested Ali could use YouTube directly to listen to podcasts, as most are now available there.
  • Ali: Confirmed most of his podcasts are on YouTube Music and noted that custom RSS feeds can be added manually.
  • Lily (via chat): Noted that YouTube Premium syncs watch/listen history across all logged-in devices, including Android.
  • Ali: Concluded that YouTube Music with RSS feed support would be his preferred cross-platform solution.
  • Siena: Suggested getting Textravaganza onto YouTube as a next step.
• Conclusion
  • YouTube Music (with RSS feed support) was identified as the preferred cross-platform podcast solution.
  • Textravaganza being added to YouTube was flagged as an action item.

Google Pixel Watch 4 Demonstration

Samantha demonstrated the accessibility features of her Google Pixel Watch 4.

• Details
  • Samantha: Demonstrated the watch home screen, which displays steps, weather, and app shortcuts (e.g., Google Gemini, Calendar, WhatsApp).
  • Samantha: Showed how to access the apps list using the crown button and navigate notifications with a two-finger swipe up.
  • Samantha: Noted the watch rings simultaneously with the phone when a call comes in, similar to Apple Watch behavior.
  • Samantha: Described the watch as feeling similar to an Apple Watch but round rather than rectangular.
  • Samantha: Mentioned difficulty changing watch straps, which require pressing two release buttons simultaneously.
  • Jackie: Highlighted the convenience of receiving Facebook and other notifications directly on the wrist while traveling.
  • Siena: Expressed interest in trying a Pixel Watch.
  • Samantha: Clarified that Fitbit is still a separate product but shares some apps with the Pixel Watch ecosystem; she was unsure whether Fitbit has TalkBack support.
• Conclusion
  • The Google Pixel Watch 4 offers solid accessibility via TalkBack and mirrors many Apple Watch features.
  • Whether Fitbit devices support TalkBack remains an open question.

Transferring Files (e.g., Ringtones) Between Android and Computer

A brief discussion arose about copying files to an Android device from a computer.

• Details
  • Samantha: Noted that ringtones and other files can be copied to Android via a Windows PC.
  • Siena: Asked whether a Mac could be used; Samantha said it is possible but more technical.
  • Ali: Recalled that connecting Android in mass storage mode via Finder on Mac was possible, referencing tutorials by Mike Arrigo from approximately 10 years ago.
  • Samantha: Remembered Mike Arrigo’s early Mac tutorials and noted she had not heard from him since around 2009.
  • Ali: Expressed interest in reaching out to Mike Arrigo and potentially inviting him as a guest on his show.
  • Samantha: Also suggested inviting David Woodbridge, noting he is active on X and Mastodon.
• Conclusion
  • Windows is the straightforward method for file transfer to Android; Mac requires a more technical approach.
  • Ali plans to reach out to Mike Arrigo and David Woodbridge as potential podcast guests.

---

Social Media Platform Strategy (X, Mastodon, Bluesky)

A discussion arose about the use of X (formerly Twitter) versus alternative platforms.

• Details
  • Samantha: Acknowledged controversy around blind users remaining on X but noted she follows opera companies and news accounts there.
  • Ali: Argued that leaving X means missing opportunities to reach audiences and spread awareness of his work.
  • Samantha: Mentioned Tusky as an accessible Mastodon app for Android.
  • Samantha: Noted Bluesky feels “a bit boring” compared to X.
  • Ali: Agreed that many key contacts remain on X, making it difficult to leave entirely.
  • Samantha: Noted some people are now using WhatsApp Channels as an alternative.
• Conclusion
  • No platform migration was decided; participants agreed that maintaining a presence on X remains strategically important for reach.

Consolidating Community Group Chats

Lily raised the idea of consolidating the various group chats (Messenger, WhatsApp, Discord) used across Textravaganza and related shows.

• Details
  • Lily: Suggested consolidating to fewer platforms to reduce the burden of posting updates in multiple places.
  • Ali: Noted that Zapier could help automate cross-posting to Discord but cannot post to private WhatsApp groups due to WhatsApp’s API limitations.
  • Siena: Confirmed this is a WhatsApp/Messenger limitation, not a Zapier limitation.
  • Ali: Expressed a preference for dropping Messenger, as neither he nor Siena are fans of it for group use.
  • Jackie: Strongly recommended keeping WhatsApp, noting the group is very active.
  • Ali: Confirmed the WhatsApp group link was made private after spammers joined, and new members must now request access.
  • Lily: Raised a concern about bad actors entering more public spaces, drawing from experience in online gaming communities.
  • Ali: Noted that YouTube allows channel owners to remove or ban problematic subscribers.
• Conclusion
  • Messenger is likely to be phased out; WhatsApp will be retained as the primary community platform.
  • Discord remains under consideration.
  • YouTube’s moderation tools were noted as sufficient to manage bad actors if Textravaganza expands there.

Expanding Textravaganza to YouTube

The group discussed uploading Textravaganza recordings to YouTube to increase reach and engagement.

• Details
  • Ali: Proposed uploading Textravaganza episodes to YouTube for broader discoverability.
  • Siena: Noted that Textravaganza is not yet on YouTube, unlike the Ali Musa Show and Books Panel.
  • Ali: Explained that adding an RSS feed to YouTube Music is only visible to the individual user; a proper YouTube channel with uploaded videos is needed for public discoverability.
  • Lily: Raised a question about participant consent, given that episodes would be accessible to strangers on a public platform.
  • Ali: Responded that the goal is awareness and growth, and that moderation tools (e.g., banning subscribers) are available on YouTube.
  • Siena: Noted that existing security measures (e.g., private WhatsApp group) already reflect a consent-based approach.
  • Lily: Acknowledged the point but noted that more open communities can attract bad actors.
  • Ali: Confirmed that YouTube allows removal of problematic subscribers.
  • Jackie: Asked whether Textravaganza would eventually live stream on YouTube.
  • Ali: Said live streaming is not the immediate plan; uploading recorded episodes is the priority. Noted YouTube requires either a 4-month waiting period or ID verification to enable live streaming.
• Conclusion
  • Textravaganza will be uploaded to YouTube as recorded episodes to increase reach.
  • Live streaming on YouTube is not an immediate priority.
  • Ali will lead the effort to set up the YouTube channel and upload content.

---

Future Textravaganza Session Planning

The group briefly discussed upcoming session topics and scheduling.

• Details
  • Siena: Reviewed the Textravaganza 2.0 schedule, which includes YouTube on iPhone and iPad (June 11), Custom Ringtones Part 2 / Zedge (July 9), and Gmail App Review (August).
  • Ashlyn: Suggested adding a WhatsApp refresher session.
  • Siena: Added a WhatsApp Refresher session to the schedule, tentatively placed in the fall.
  • Samantha: Suggested Rob could do a tutorial on the BlindShell phone, noting it runs a hybrid of Android and proprietary software.
  • Siena: Agreed it would be a worthwhile tutorial for those interested in a button-based Android hybrid device.
  • Ali: Reminded participants about the upcoming Books Panel session on Friday.
• Conclusion
  • WhatsApp Refresher was added to the fall schedule.
  • A BlindShell tutorial with Rob is being considered; Siena will follow up via email.
  • Next Textravaganza session: June 3.

Battery Life: Android vs. iPhone

A brief informal discussion occurred about battery performance.

• Details
  • Jackie: Noted that Android generally offers better battery life than iPhone.
  • Siena: Agreed, noting her Motorola has strong battery performance.
  • Ashlyn: Mentioned her iPhone battery died mid-session, partly due to Bluetooth drain from a connected watch.
  • Jackie: Noted she charges her Android every other day since it is no longer her primary phone.
  • Ali: Recommended not letting the battery drop too low to preserve long-term battery health.
• Conclusion
  • Android devices, particularly Motorola, were noted for superior battery life compared to iPhone.
  • Best practice is to charge before the battery drops too low.

Check out What’s Coming up on Techstravaganza at the following link: https://techstravaganza.ca/2026/05/13/updated-as-of-may-13-2026-whats-coming-up-on-techstravaganza/

Contact the team:

Email: support@techstravaganza.ca

Like us on Facebook: https://www.facebook.com/profile.php?id=61578990010675

Follow the Show:

Tunein: http://tun.in/pxXlj

On Apple Podcasts: https://podcasts.apple.com/ca/podcast/techstravaganza/id1846930800

On Audible: https://podcasts.apple.com/ca/podcast/techstravaganza/id1846930800

On iHeart: https://www.iheart.com/podcast/269-techstravaganza-301161434/

On Spotify: https://spotify.link/vVGru9nKBXb

VoiceOver Touch Gesture Customization — Overview and Reset

Ali demonstrated how to access VoiceOver touch gesture settings and reset all commands to defaults before reassigning them.

• Details
  • Ali: Navigated to Settings > Accessibility > VoiceOver > Commands > Touch Gestures on an iPhone.
  • Ali: Reviewed existing custom commands before resetting, noting that some commands (shown as dimmed) cannot be changed.
  • Ali: Activated the “Reset VoiceOver Commands” button, which restores all touch gestures, keyboard shortcuts, and braille shortcuts to their defaults.
  • Ali: Explained that resetting is useful as a clean starting point before customizing.
• Conclusion
  • VoiceOver commands can be reset via Settings > Accessibility > VoiceOver > Commands > Reset VoiceOver Commands.
  • Dimmed commands are system-locked and cannot be reassigned.

VoiceOver Touch Gesture Customization — Assigning Specific Commands

Ali walked through reassigning specific touch gestures to preferred system functions, demonstrating the process live.

• Details
  • Ali: Assigned one-finger triple tap to “Home” (previously “Perform Long Press”).
  • Ali: Assigned one-finger quadruple tap to “App Switcher” (previously “Secondary Activate”).
  • Ali: Assigned two-finger triple tap to “Notification Center” (previously “Show Item Chooser”).
  • Ali: Assigned two-finger quadruple tap to “Control Center” (previously “Open Quick Settings”).
  • Ali: Removed the two-finger double tap on far edges (Braille Screen Input) and two-finger triple tap on far edges (Braille Screen Input Command Mode) as they were not personally used.
  • Ali: Assigned four-finger triple tap to “Escape” (previously “Live Recognition”), after confirming with Siena that Live Recognition was not essential for his workflow.
  • Ali: Assigned four-finger quadruple tap to “Perform Long Press.”
  • Ali: Noted that when a gesture conflict arises, an alert appears offering the option to reassign or cancel.
  • Ali: Highlighted the usefulness of the search field within the commands menu to locate specific commands quickly, rather than flicking through the entire list.
• Conclusion
  • Touch gestures can be customized to suit individual workflows via Settings > Accessibility > VoiceOver > Commands > Touch Gestures.
  • When a gesture is already assigned, users are prompted to reassign or cancel.
  • The search field within the commands menu significantly speeds up navigation.

Q&A: Navigating to VoiceOver Command Settings (Liz)

Liz asked for a recap of how to access the VoiceOver gesture settings.

• Details
  • Liz: Asked how to navigate to the VoiceOver default gesture settings, having missed the initial explanation.
  • Ali: Directed her to Settings > Accessibility > VoiceOver > Commands > Touch Gestures, or to use the Settings search box and type “voiceover.”
  • Liz: Confirmed understanding that dimmed items cannot be changed.
• Conclusion
  • Path to VoiceOver gesture settings: Settings > Accessibility > VoiceOver > Commands > Touch Gestures.
  • Using the Settings search box is a recommended shortcut.

Q&A: One-Finger Triple Tap vs. Long Press for Home (Jeroo)

Jeroo asked about the original function of the one-finger triple tap and whether braille commands could be repurposed for the Home function.

• Details
  • Jeroo: Asked which command was originally assigned to one-finger triple tap (it was “Perform Long Press”).
  • Jeroo: Inquired whether braille commands could be reassigned to Home for easier access.
  • Ali: Explained that braille screen input commands require placing a finger on a specific part of the screen, making them less convenient than a simple tap gesture.
  • Ali: Clarified that one-finger triple tap for Home is easier because it does not require being in a specific screen location.
  • Siena: Added that the two-finger double tap on far edges (Braille Screen Input on/off) and two-finger triple tap on far edges (Braille Screen Input Command Mode) can be reassigned if not in use, and offered one-on-one assistance.
• Conclusion
  • One-finger triple tap for Home is more accessible than braille edge commands, which require precise finger placement.
  • Unused braille screen input commands can be reassigned to other functions.

Q&A: Memory Patterns for Gesture Commands (Liz)

Liz asked whether there is a logical pattern to help remember the 16 possible gesture combinations.

• Details
  • Liz: Noted there are 16 possible combinations (1–4 fingers × single/double/triple/quadruple tap) and asked if there is a rule of thumb.
  • Siena: Explained her personal pattern — one-finger triple tap for Home, one-finger quadruple tap for App Switcher, two-finger triple tap for Notification Center, two-finger quadruple tap for Control Center — chosen for ease of recall.
  • Siena: Demonstrated VoiceOver Help (four-finger double tap) as a practice area where performing a gesture announces its assigned command.
  • Siena: Suggested customizing gestures in a personally meaningful pattern and practicing daily until memorized.
  • Ali: Confirmed he uses the same gesture assignments as Siena.
• Conclusion
  • There is no universal rule of thumb; users should customize gestures in a personally logical pattern.
  • VoiceOver Help (four-finger double tap) can be used to verify what each gesture is assigned to.
  • Regular practice is recommended to build muscle memory.

Q&A: Rotor Customization and Braille Screen Input Activation (Lily)

Lily raised a question about activating Braille Screen Input, finding the rotor method cumbersome.

• Details
  • Lily: Found it difficult to activate Braille Screen Input via the rotor due to the number of options.
  • Siena: Explained the gesture to activate Braille Screen Input: hold the phone in landscape mode (charging port to the right) and double tap the top and bottom edges simultaneously, typically using ring fingers.
  • Siena: Confirmed the gesture works regardless of whether orientation lock is on or off, and regardless of Braille Screen Input orientation settings.
• Conclusion
  • Braille Screen Input can be activated by double tapping the top and bottom edges of the screen simultaneously while holding the phone in landscape mode.
  • This works with orientation lock enabled or disabled.

Double Tap and Hold (Long Press) as a Navigation Shortcut

Ali demonstrated using a double tap and hold to access a back-navigation context menu, and discussed assigning it to a gesture command.

• Details
  • Ali: Demonstrated that a one-finger double tap and hold reveals a context menu showing the navigation hierarchy (e.g., Commands > VoiceOver > Accessibility > Settings), allowing quick return to a higher-level screen.
  • Ali: Noted that the double tap and hold motion can be imprecise and suggested assigning “Perform Long Press” to the four-finger quadruple tap for easier access.
  • Siena: Confirmed that double tap and hold is equivalent to a long press.
• Conclusion
  • Double tap and hold activates a context menu for quick back-navigation through screen hierarchy.
  • Assigning “Perform Long Press” to a tap gesture (e.g., four-finger quadruple tap) provides a more reliable alternative.

Using the Settings Search Box as a Navigation Shortcut

Ali highlighted the Settings search box as a time-saving tool for locating VoiceOver settings.

• Details
  • Ali: Demonstrated typing “commands” into the Settings search box to directly navigate to VoiceOver Commands, rather than manually flicking through Settings > Accessibility > VoiceOver > Commands.
  • Ali: Noted the search results include multiple entries with “commands” in the name, with the VoiceOver Commands option appearing prominently.
• Conclusion
  • Using the Settings search box is the recommended method for quickly locating VoiceOver command settings.

VoiceOver Keyboard Shortcut Customization

Ali demonstrated customizing VoiceOver keyboard shortcuts using a Matthias wireless keyboard paired to the iPhone.

• Details
  • Ali: Explained that many users are unaware VoiceOver supports keyboard commands on iPhone, and that he uses a full-size Matthias wireless keyboard paired across Mac, PC, iPad, and iPhone.
  • Ali: Navigated using keyboard commands (Ctrl+Option+Left/Right Arrow, Ctrl+Option+S, Ctrl+Option+Space) to reach Settings > Accessibility > VoiceOver > Commands > Keyboard Shortcuts.
  • Ali: Reassigned the Control Center keyboard shortcut from Ctrl+Option+Page Down to Ctrl+Option+I, first deleting the existing “Show Item Chooser” assignment for the letter I.
  • Ali: Reassigned the Notification Center keyboard shortcut from Ctrl+Option+Page Up to Ctrl+Option+N, first deleting the existing “Toggle Announcement History” assignment for the letter N.
  • Ali: Noted that when entering a new keyboard shortcut, the Done button must be activated via the touchscreen, as continuing to type on the keyboard will alter the command being assigned.
  • Jeroo: Asked whether two-character combinations (e.g., CC) could be used for commands; Ali confirmed this is not possible due to the single-key structure of VoiceOver keyboard commands.
  • Lily: Asked whether punctuation characters could be used; Ali clarified that all keyboard commands use the Ctrl+Option modifier plus a single key, so punctuation is not a separate input layer.
  • Ali: Reflected that Ctrl+Option+C for Control Center and Ctrl+Option+N for Notification Center would be a logical and memorable pairing.
• Conclusion
  • VoiceOver keyboard shortcuts can be customized via Settings > Accessibility > VoiceOver > Commands > Keyboard Shortcuts.
  • When reassigning a key already in use, the existing assignment must be deleted first.
  • The Done button after entering a new shortcut must be activated via touchscreen, not keyboard.
  • Only single-key combinations with the Ctrl+Option modifier are supported.

Screen Curtain: Usage and Privacy

Liz asked about Ali’s use of the screen curtain feature.

• Details
  • Liz: Asked whether Ali uses the screen curtain on or off.
  • Ali: Stated he keeps the screen curtain on by default for privacy, turning it off only when demonstrating the screen to others.
  • Siena: Added that keeping the screen curtain on also conserves battery.
  • Liz: Mentioned that another instructor removes the screen curtain command from their teaching setup because students accidentally activate it and panic, thinking their phone has died.
  • Ali: Acknowledged different teaching approaches without commenting on others’ methods.
• Conclusion
  • Screen curtain is a personal preference; keeping it on provides privacy and saves battery.
  • Some instructors choose to remove the command to prevent accidental activation by new users.

Back Tap Gestures

Hans raised the topic of back tap gestures as an additional customization option.

• Details
  • Hans: Asked whether back tap gestures (tapping the back of the iPhone) can be customized, noting he had seen the option in settings but had not used it.
  • Ali: Confirmed he believes back tap gestures can be customized but has not personally used them and would need to research further.
  • Ali: Raised a concern that placing the phone face-down might accidentally trigger back tap commands.
  • Hans: Noted that back tap may be available from iPhone X and later models, and that it could be useful for complex gestures.
  • Yvonne: Shared that she uses back tap frequently to toggle VoiceOver on and off, finding it very convenient, particularly when VoiceOver is off and she needs to navigate the phone more easily.
  • Yvonne: Acknowledged that accidental activation can occur but is easy to correct.
• Conclusion
  • Back tap gestures are available on iPhone X and later and can be used to toggle VoiceOver on/off, among other functions.
  • Ali will research back tap customization for a future session.

Q&A: Gesture Sync Across Devices (Liz)

Liz asked whether customized gestures on iPhone automatically sync to iPad.

• Details
  • Liz: Asked if changes made on iPhone automatically apply to iPad.
  • Ali: Confirmed that gesture customizations do not sync between devices and must be set up separately on each device.
• Conclusion
  • VoiceOver gesture customizations are device-specific and must be configured individually on each device.

Upcoming Session Announcement

The session concluded with an announcement of the next Techstravaganza topic.

• Details
  • Siena: Announced that the next session will cover Android TalkBack settings.
  • Ali and participants expressed enthusiasm for the upcoming topic.
  • Jackie: Noted she still has an Android device.
• Conclusion
  • Next Techstravaganza session: Android TalkBack settings.

Check out the upcoming topics schedule for Techstravaganza at the following link: https://techstravaganza.ca/2026/05/13/updated-as-of-may-13-2026-whats-coming-up-on-techstravaganza/

Contact the team:

Email: support@techstravaganza.ca

Like us on Facebook: https://www.facebook.com/profile.php?id=61578990010675

Follow the Show:

Tunein: http://tun.in/pxXlj

On Apple Podcasts: https://podcasts.apple.com/ca/podcast/techstravaganza/id1846930800

On Audible: https://podcasts.apple.com/ca/podcast/techstravaganza/id1846930800

On iHeart: https://www.iheart.com/podcast/269-techstravaganza-301161434/

On Spotify: https://spotify.link/vVGru9nKBXb