Techstravaganza

Setting Up an iPhone Independently with Voiceover, Thursday, August 13, 2026

Written by

Macara

in

Good evening Techstravaganza friends,

Have a listen to tonight’s wonderful tutorial of setting up an iPhone independently using voiceover, at the following link: https://open.spotify.com/episode/1lVtJpgd0hASh2D32VhPPg

Show Notes

iPhone Setup Tutorial: VoiceOver Accessibility Walkthrough

The main tutorial of the session involved Siena setting up an iPhone 11 from scratch using VoiceOver, simulating an out-of-box experience.

  • Details
    • Siena: Demonstrated activating VoiceOver via triple-click of the side button; selected language (English) and region (Canada); connected to Wi-Fi; set up a custom four-digit numeric passcode; signed into iCloud with her Apple account; completed two-factor authentication; chose to restore from an iCloud backup; accepted Apple data and privacy terms; enrolled in the Apple Beta Software Program; and initiated an iOS 27 Beta 3 download and installation.
    • Siena: Explained that the iPhone 11 had previously belonged to her grandmother, who is now using Siena’s iPhone 15. Siena reclaimed the iPhone 11 and set it up fresh.
    • Ali Moosa: Noted that the Activation Lock prompt appears when a phone is not properly signed out before being passed on, and explained the process of turning off Find My and Activation Lock before transferring a device.
    • Siena: Chose to skip Face ID setup during the tutorial (to avoid making Ali cringe, as an inside joke) and deferred Apple Pay setup to later.
    • Siena: Explained two main data transfer methods: restoring from iCloud backup, and placing two iPhones side by side to use Apple’s Near Field Communication (NFC) technology for direct device-to-device transfer.
    • Jackie Castrogiovanni: Asked whether the phones literally “talk to each other” during the side-by-side transfer; Siena clarified it is a proprietary NFC-based connection, not audible communication, though VoiceOver prompts appear on each device.
    • Ali Moosa: Shared that he prefers manual setup over the quick-start proximity method for greater control and confirmation.
    • Ashlyn Eddy’s: Shared a story about store staff thinking her iPhone 15 screen was broken during setup because Screen Curtain was enabled, making the display appear black.
    • Lily: Noted she has done setup both ways and that it depends on what works for each person.
    • Siena: Noted that the iOS update prompt during setup is expected regardless of beta enrollment, as new phones typically require updates out of the box.
    • Siena: Confirmed the setup was completed fully independently using VoiceOver, without sighted assistance.
  • Conclusion
    • The full iPhone setup process using VoiceOver was successfully demonstrated.
    • Key steps covered: VoiceOver activation, language/region, Wi-Fi, passcode, iCloud sign-in, 2FA, data transfer options, privacy settings, beta enrollment, and iOS update.
    • Participants were encouraged to attempt setup independently, as VoiceOver guides users through every step.
    • The restore process was still in progress (approximately 10 GB remaining) at the end of the session.

iOS Update Download Progress and Battery Best Practices

While waiting for the iOS 27 Beta 3 download to complete, the group discussed update behavior and battery health.

  • Details
    • Siena: Monitored and narrated download progress live (from 2% to 99%), noting that progress percentages can appear to stall before resuming.
    • Ali Moosa: Observed that update percentages can be misleading and sometimes do not reflect actual progress accurately. He also shared that he uses a stopwatch on the Mac Clock app to time updates.
    • Lily: Mentioned that her phone updated overnight without being plugged in, which surprised her.
    • Ali Moosa: Explained that battery level at the time of update initiation affects whether the phone will proceed without being plugged in.
    • Lily: Suggested setting maximum charge to 80% to preserve battery health, noting that repeatedly charging to 100% and draining fully accelerates battery degradation.
    • Ali Moosa: Noted this is already the default behavior when charging overnight.
    • Ashlyn Eddy’s: Mentioned her iPhone 15 is at 85% maximum battery health and expressed concern about adding more strain.
    • Siena: Noted she would be curious to check the iPhone 11’s battery health.
    • Ali Moosa: Reassured Ashlyn that 85% should still be usable for at least another couple of years.
  • Conclusion
    • Plugging in the device during updates is recommended as a safeguard.
    • Battery health degrades naturally over time; limiting charge to 80% can help slow degradation.
    • Update percentages are not always linear and may pause before continuing.

Repurposing Old iPhones and Device Hand-Me-Down Practices

A casual discussion arose about how participants use older devices after upgrading.

  • Details
    • Siena: Uses older iPhones for listening to music, audiobooks, and testing battery-intensive apps to avoid draining her primary device.
    • Ali Moosa: Uses his iPad primarily for listening to content, banking apps (e.g., RBC), and audiobooks; currently running iOS 26 beta rather than iOS 27 beta on it.
    • Ashlyn Eddy’s: Shared that her 15-year-old cousin received an iPhone 11 as a hand-me-down from her mother’s work colleague and complained about needing to charge it twice a day.
    • Lily: Described a family phone hierarchy where devices pass from one family member to the next as upgrades occur.
    • Ali Moosa: Shared that he gave his iPhone 12 to his father after erasing it and turning off Activation Lock, then helped set it up under his father’s account.
  • Conclusion
    • Keeping older devices for secondary use (media, testing) is a practical approach endorsed by the group.
    • Properly erasing a device and disabling Activation Lock before transferring it to another person is essential.

Face ID: Privacy Concerns and Personal Preferences

A discussion about Face ID emerged during the setup, touching on security risks and personal comfort.

  • Details
    • Ali Moosa: Shared a story about spending 20 minutes trying to set up Face ID, becoming frustrated when it kept asking him to reposition his head, and ultimately abandoning it.
    • Ashlyn Eddy’s: Also does not use Face ID, preferring a four-digit numeric passcode.
    • Lily: Referenced the Netflix show “You,” in which a character uses a victim’s face to unlock their phone posthumously.
    • Ali Moosa: Raised the real-world concern of someone lifting a sleeping person’s eyelid to unlock their phone via Face ID.
    • Siena: Mentioned reports of possessive or abusive partners accessing phones this way.
    • Ali Moosa: Noted that Touch ID (fingerprint) may be harder to abuse in the same manner.
    • Siena: Questioned whether Touch ID could similarly be exploited by pressing a sleeping person’s finger to the sensor.
  • Conclusion
    • Face ID was skipped during the tutorial; Siena planned to set it up privately later.
    • The group generally preferred passcodes or Touch ID over Face ID for privacy and usability reasons.
    • Both Face ID and Touch ID carry potential misuse risks, but the group felt passcodes remain the most straightforward option.

TextEdit and Google Docs Workflow on Mac

Ali asked Siena for advice on managing meeting notes from Google Meet in a Mac-compatible format.

  • Details
    • Ali Moosa: Explained that Google Meet automatically saves meeting notes to Google Docs, which he accesses via Safari on Mac. He wanted to know the best way to edit and save this content locally.
    • Siena: Recommended copying the text into TextEdit and saving it as a .txt file, which can then be opened in Google Docs or LibreOffice.
    • Siena: Also mentioned that LibreOffice now works on Mac and that exporting from Pages as a Word document is another option.
    • Ali Moosa: Confirmed he would use TextEdit with Command+N to create a new document and paste the content.
  • Conclusion
    • Ali will copy Google Meet notes into TextEdit and save as a .txt file for local editing and storage.

Upcoming Session Topics and Schedule Announcements

Siena outlined the confirmed schedule and topics for upcoming Techstravaganza sessions.

  • Details
    • Siena: Techstravaganza Extra on Friday, September 4 — LibreOffice on Mac (previously attempted but affected by accessibility bugs, now resolved).
    • Siena: Techstravaganza Evenings on Thursday, September 10 — WhatsApp on Mac.
    • Siena: October Techstravaganza Evenings — WhatsApp on PC.
    • Siena: Also expressed interest in covering Android content in a future session.
    • Ashlyn Eddy’s: Asked whether the LibreOffice session would include spreadsheets, which had caused crashes previously.
    • Siena: Confirmed she would test all components of the LibreOffice suite beforehand to determine which parts are stable enough to demonstrate.
    • Siena: Noted that the LibreOffice accessibility bugs have been resolved, including through workarounds she discovered independently.
    • Ali Moosa: Jokingly suggested asking Jack (a mutual contact known for workarounds) for help, though expressed concern about letting him touch his system unsupervised.
  • Conclusion
    • Three upcoming sessions confirmed with specific topics and dates.
    • Pre-session testing of LibreOffice will be conducted by Siena before the September 4session.
    • Android coverage is planned for a future session (date TBD).
    • Topic for Techstravaganza Extra (September 4) will also be posted in the newsletter.

Remote Incident Manager and Supervised Remote Access

A brief discussion touched on using Remote Incident Manager (RIM) for remote tech support.

  • Details
    • Ali Moosa: Explained that if Jack were to assist him remotely, it would be done through Remote Incident Manager, which uses Ali’s own screen reader voice and settings, allowing Ali to hear everything being done on his machine.
    • Siena: Confirmed that RIM also allows the remote helper to chat with the user during the session.
    • Ashlyn Eddy’s: Humorously suggested leaving a sticky note listing only the specific things Jack is allowed to touch and change.
  • Conclusion
    • Remote Incident Manager was identified as a preferred tool for supervised remote assistance, as it preserves the user’s screen reader settings and maintains transparency.

Contact the team:

Email: support@techstravaganza.ca

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

Would you like to join the Techstravaganza Workshops Whatsapp Group? Fill out the form located at the following link: https://techstravaganza.ca/join-the-techstravaganza-workshops-whatsapp-group/

Follow the Show:

Tunein: http://tun.in/pxXlj

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

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

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

Spotify: https://spotify.link/vVGru9nKBXb

Comments

Leave a Reply

More posts

Discover more from Techstravaganza

Subscribe now to keep reading and get access to the full archive.

Continue reading