[
    {
        "role": "user",
        "content": "my%20word%20365%20says%20it%20is%20in%20coauthoring%20mode.%20how%20do%20i%20turn%20that%20off%3F%20i%20am%20blind%20and%20use%20jaws%20for%20windows."
    },
    {
        "role": "assistant",
        "content": "Here\u2019s how to turn off co-authoring (live collaboration) in **Microsoft Word for Microsoft 365** (on Windows), especially when using JAWS, the screen reader. Usually \u201cco-authoring mode\u201d means **AutoSave** is on and the document is stored on a cloud location (OneDrive, SharePoint), and someone else can also edit it.\n\n---\n\n### What turning off co-authoring does\n\n- Disables **AutoSave** so Word stops syncing every change in real time.  \n- Prevents seeing or merging edits from other people while you work.  \n- Allows you to work locally, without simultaneous editing by others.  \n\n---\n\n### Steps to disable co-authoring / AutoSave\n\n1. **Open the document in Word desktop** \u2014 not Word Online.  \n   If you're in the browser, switch to desktop by selecting **Open in Word**. ([support.microsoft.com](https://support.microsoft.com/en-US/Word/training/collaborate-on-word-documents-with-real-time-co-authoring?utm_source=openai))\n\n2. **Turn off AutoSave**  \n   - Press **Alt + F** to open the **File** menu.  \n   - Use the arrow keys or letters to navigate to AutoSave toggle (it\u2019s near the top of the screen).  \n   - Press **Space** to switch AutoSave off.  \n   Disabling AutoSave stops live co-authoring updates.  \n\n3. **Save a local copy** (if needed)  \n   - After turning off AutoSave, save the document to your computer instead of saving back to OneDrive or SharePoint. Use **Save As** and choose a local folder.  \n   This ensures Word is working on a single-user, local file.  \n\n4. **Close shared cloud version**  \n   - If the document is open elsewhere (on another device or by another user), closing those copy(ies) helps avoid conflicts.\n\n---\n\n### What if the document *must* stay in the cloud?\n\nSometimes, your organization requires documents to remain on OneDrive or SharePoint. In that case:\n\n- You still **turn off AutoSave**. This will stop Word uploading every change. You\u2019ll need to manually **Save** when you want to store changes.  \n- You will still technically be in a shared version, but it won\u2019t update in real time. It behaves more like a traditional save-and-share workflow.  \n\n---\n\n### Important for JAWS users\n\n- After turning AutoSave off, Word might announce \u201cAutoSave is off.\u201d Make sure to verify via the status bar or dialog boxes.  \n- If the AutoSave toggle can\u2019t be found, use **ALT + F**, then **T** for Options, then navigate to **Save** settings to check if there is an \u201cAutoSave default\u201d that can be changed.  \n- If possible, customize Word so that documents open **locally by default** instead of in the cloud or shared mode.\n\n---\n\nIf you like, I can give you a step-by-step list of keyboard commands (with JAWS-friendly cues) specific to your Word version to turn off co-authoring. Would that be helpful?"
    },
    {
        "role": "user",
        "content": "have%20there%20been%20objections%20by%20blind%20people%20to%20the%20installation%20in%20Toronto%20or%20other%20cities%20of%20a%20scramble%20intersection%3F"
    },
    {
        "role": "assistant",
        "content": "Yes \u2014 there *have* been objections and concerns from blind and visually impaired people about pedestrian scramble intersections in Toronto and elsewhere. Much of this feedback centers on issues with **accessibility**, **information cues**, and **safety**. Below are examples of those objections, plus ideas discussed or implemented for addressing them.\n\n---\n\n## What are scramble intersections\n\nA \u201cscramble\u201d (also called *exclusive pedestrian phase*, *pedestrian scramble*, or *Barnes Dance*) is a traffic signal phase where all vehicular traffic is stopped, and pedestrians may cross in every direction, including diagonally. Toronto has several such intersections (e.g. Yonge & Dundas, Yonge & Bay, Yonge & Bloor) ([toronto.ca](https://www.toronto.ca/wp-content/uploads/2017/11/8eee-pedestrian_scramble_crossings.pdf?utm_source=openai)).\n\n---\n\n## Objections or concerns from blind/visually impaired people\n\nFrom Toronto and beyond, some visually impaired pedestrians have raised concerns about scramble crossings. Key issues:\n\n1. **Loss of audio and traffic cues during scramble phases**  \n   - In Toronto, when the scramble (diagonal) phase is active, there is *no vehicle movement noise or directional cues*. The usual sound of traffic helps blind pedestrians know which direction vehicular traffic is moving, letting them orient themselves. With scramble phases, this orientation can become confusing. ([toronto.ca](https://www.toronto.ca/wp-content/uploads/2017/11/8eee-pedestrian_scramble_crossings.pdf?utm_source=openai))  \n   - Also, the \u201cbodies of pedestrians moving in all directions\u201d may obscure or disappear around them, further reducing spatial cues. ([toronto.ca](https://www.toronto.ca/wp-content/uploads/2017/11/8eee-pedestrian_scramble_crossings.pdf?utm_source=openai))\n\n2. **Difficulty staying on desired crossing paths**  \n   - Without clear directional cues, a blind pedestrian or guide dog may be led diagonally instead of crossing straight across on a non-scramble phase. They might also try to cross during what appears to be a \u201cwalk\u201d phase, but which is actually part of a scramble or mixture of pedestrian/vehicle movement. ([toronto.ca](https://www.toronto.ca/wp-content/uploads/2017/11/8eee-pedestrian_scramble_crossings.pdf?utm_source=openai))\n\n3. **Crowding at push-button stations and APS (Accessible Pedestrian Signals)**  \n   - Scramble intersections can get very crowded. This can block access to APS pushbuttons or make tactile indicators hard to find quickly. ([toronto.ca](https://www.toronto.ca/wp-content/uploads/2017/11/8eee-pedestrian_scramble_crossings.pdf?utm_source=openai))  \n   - The tones used in APS systems may not differ clearly between north-south vs. east-west crossings. At scramble intersections, people have said that distinct tones are needed to let them know which leg of the crossing is active. ([toronto.ca](https://www.toronto.ca/wp-content/uploads/2017/11/8eee-pedestrian_scramble_crossings.pdf?utm_source=openai))\n\n4. **Lack of awareness that the intersection is a scramble**  \n   - People unfamiliar with a specific intersection (especially if blind or low vision) may not know the intersection operates differently than a typical \u201cwalk on green\u201d crossing. That uncertainty increases risk. ([toronto.ca](https://www.toronto.ca/wp-content/uploads/2017/11/8eee-pedestrian_scramble_crossings.pdf?utm_source=openai))\n\n5. **Volume and timing of pedestrians**  \n   - At some intersections (e.g. Yonge & Eglinton), crowding is already noted. The potential for large pedestrian volume during scramble phases affects comfort, safety, and predictability for those who are blind. ([toronto.ca](https://www.toronto.ca/legdocs/mmis/2025/ie/comm/communicationfile-196393.pdf?utm_source=openai))\n\n---\n\n## Actual cases & debates\n\n- **Toronto**: A 2017 report by the City noted these concerns specifically at some scramble intersections. The citizens and disability-advocate groups expressed that APS tones weren\u2019t always sufficient or clear, that pushbuttons and signals are crowded, and guide dogs could be led diagonally when that wasn\u2019t the user's choice. ([toronto.ca](https://www.toronto.ca/wp-content/uploads/2017/11/8eee-pedestrian_scramble_crossings.pdf?utm_source=openai))  \n- **Canada-wide position paper** (APS Position Paper) says that in some places, scramble phasing should either be **made accessible** \u2014 including better APS, messaging, tones \u2014 or be **avoided** altogether if these accessibility features aren\u2019t or can\u2019t be provided. ([vision.alberta.ca](https://vision.alberta.ca/media/87388/accessible%20pedestrian%20signals%20-%20aps%20position%20paper.pdf?utm_source=openai))  \n- **United States / Legal context (DC case)**: The lawsuit *DC Council of the Blind vs. the District of Columbia* explicitly cites \u201cpedestrian scramble\u201d (exclusive pedestrian phase) intersections as examples where blind pedestrians face risks if there are no proper audible cues to indicate when the walk interval is active. ([relmanlaw.com](https://www.relmanlaw.com/media/cases/2244_DC-APS_Complaint_FINAL803144.2_ACC.pdf?utm_source=openai))\n\n---\n\n## Recommendations or ways to mitigate the concerns\n\nBecause the objections are common and important, several solutions are suggested or attempted:\n\n| Issue | Possible/Existing Mitigation |\n|---|---|\n| No directional cues during scramble phase | Verbal announcements like \u201cWALK sign is on for all crossings,\u201d louder or directional APS tones, or distinct tones for different crossing phases (north-south vs. east-west) ([toronto.ca](https://www.toronto.ca/wp-content/uploads/2017/11/8eee-pedestrian_scramble_crossings.pdf?utm_source=openai)) |\n| Crowding blocking APS buttons | Signal timing adjustments to reduce crowding, better sidewalk design, possibly relocating pushbuttons to more accessible positions ([toronto.ca](https://www.toronto.ca/wp-content/uploads/2017/11/8eee-pedestrian_scramble_crossings.pdf?utm_source=openai)) |\n| Blind pedestrians crossing diagonally when they don\u2019t want to | Clear instruction via APS, tactile cues embedded in curb ramps or crosswalks, orientation materials or signage to signal that there is a diagonal option but also conventional crosswalk phases ([toronto.ca](https://www.toronto.ca/wp-content/uploads/2017/11/8eee-pedestrian_scramble_crossings.pdf?utm_source=openai)) |\n| Lack of recognition that intersection is different | Public education, signage indicating \u201cPedestrian scramble operates here,\u201d maybe even audio signals that announce phase changes, so that people know what to expect ([toronto.ca](https://www.toronto.ca/wp-content/uploads/2017/11/8eee-pedestrian_scramble_crossings.pdf?utm_source=openai)) |\n\n---\n\n## Specific Toronto case: *Yonge and Eglinton*\n\n- There has been strong support from Walk Toronto and others to install a scramble intersection at Yonge & Eglinton. At the same time, concerns were raised (in staff reports) about pedestrian delays, transit vehicle delays, etc. However, I found no formal report or evidence that specifically collects complaints from blind individuals *there* yet \u2014 the discussion has been more general about pedestrians. ([walktoronto.ca](https://www.walktoronto.ca/2025/09/29/walk-toronto-advocates-for-pedestrian-scramble-intersection-at-yonge-and-eglinton/?utm_source=openai))\n\n---\n\nIf you want, I can try to find *first-hand testimonies* from blind people in Toronto about specific intersections with scramble crosswalks, so you can see the kinds of experiences they're reporting. Do you want me to gather those?"
    }
]