[
    {
        "role": "user",
        "content": "Are%20there%20any%20tutorials%20for%20Microsoft%20Access%20and%20the%20Jaws%20screen%20reader%3F"
    },
    {
        "role": "assistant",
        "content": "Yes \u2014 there *are* several tutorials and resources for using **Microsoft Access** with the **JAWS** screen reader, though they are somewhat limited compared to more common desktop apps. Below is a guide to the best resources, plus tips for finding or creating tutorials tailored to your needs.\n\n---\n\n## \ud83d\udd0d Key Official Tutorials & Guides\n\nMicrosoft offers a dedicated \"Screen reader support for Access\" section on the Microsoft Support site, with step\u2010by\u2010step help meant for people using screen readers like JAWS, Narrator, or NVDA. Topics include:\n\n- How to start Access using a screen reader  \n- Creating tables, queries, forms, reports, charts  \n- Working with templates, exporting/importing data  \n- Keyboard shortcuts tailored for Access accessibility  \n\nThese are written directly for Access users leveraging screen reader features.  \n([support.microsoft.com](https://support.microsoft.com/en-gb/office/screen-reader-support-for-access-0861c152-a09d-43f6-bb7e-1bb63a12cb93?utm_source=openai))\n\nAlso available is the **Access Accessibility Design Guide** (a Microsoft PDF), which explains how screen readers describe objects in forms and reports. For example, when you tab into a form field, it tells you which field you're in, what its label is, and the current value.  \n([download.microsoft.com](https://download.microsoft.com/download/A/0/7/A0739120-E9B0-48D6-8682-F482D2CD3A4A/Access%20Design%20Guide%20for%20Accessibility.pdf?utm_source=openai))\n\n---\n\n## \ud83c\udf93 Broader JAWS Training Resources\n\nWhile quite a few tutorials cover using JAWS generally or in other apps (web, Word), there are fewer that focus specifically on Microsoft Access. Some useful ones are:\n\n- **JAWS Essentials from AAT Solutions** \u2013 Covers core screen reader navigation, setting up reading modes, customizing settings. Helpful before applying those skills in Access.  \n  ([aatsolutions.uk](https://aatsolutions.uk/resources/screen-reader-tutorials/jaws?utm_source=openai))\n\n- **Harvard\u2019s \u201cGetting Started Testing with JAWS\u201d** \u2013 Though focused on web content, this includes essential commands & settings that work similarly in desktop apps.  \n  ([accessibility.huit.harvard.edu](https://accessibility.huit.harvard.edu/jaws?utm_source=openai))\n\nIf you're already familiar with basic JAWS commands, applying them in Access becomes easier.\n\n---\n\n## \ud83e\udde9 How to Find or Build Tutorials Specific to Access\n\nBecause there aren't many video or hands-on guides specific to Access + JAWS (especially newer versions), here's how you can expand your resources or even make your own:\n\n- Visit **Microsoft Support** and search \u201cscreen reader support Access desktop databases\u201d or \u201cuse a screen reader to create forms in Access.\u201d You\u2019ll often find recent walkthroughs.  \n  ([support.microsoft.com](https://support.microsoft.com/en-gb/office/screen-reader-support-for-access-0861c152-a09d-43f6-bb7e-1bb63a12cb93?utm_source=openai))\n\n- Use Microsoft\u2019s **Access Accessibility Design Guide** to understand structure and form/report navigation.  \n  ([download.microsoft.com](https://download.microsoft.com/download/A/0/7/A0739120-E9B0-48D6-8682-F482D2CD3A4A/Access%20Design%20Guide%20for%20Accessibility.pdf?utm_source=openai))\n\n- Check \uc6f9\uc0ac\uc774\ud2b8 or YouTube for tutorials using keywords like *\u201cAccess + JAWS navigation\u201d* or *\u201cMicrosoft Access screen reader tutorial\u201d*. The results might cover older versions, but many concepts (forms, reports, table design) remain consistent.\n\n- Join forums or community groups for blind or low-vision users. They often share scripts, tips, or custom Access templates designed for JAWS.\n\n---\n\n## \u2699\ufe0f Tips for Effective Use with Access + JAWS\n\nTo get the most out of Access when using a screen reader like JAWS, these practices help:\n\n- Use **keyboard navigation exclusively**: TAB to move forward among controls/forms, SHIFT+TAB to move backward; use arrows in lists. Access Objects like forms, fields, and buttons are better accessed this way.\n\n- Ensure all form/report elements have **clear labels**: JAWS typically reads the label first. Forms with missing or ambiguous labels are hard to follow. The Design Guide shows examples.  \n  ([download.microsoft.com](https://download.microsoft.com/download/A/0/7/A0739120-E9B0-48D6-8682-F482D2CD3A4A/Access%20Design%20Guide%20for%20Accessibility.pdf?utm_source=openai))\n\n- Use the **\u201cTab order\u201d** in forms and reports correctly so navigation happens in a logical sequence.\n\n- For reading data, use **reports** rather than just data sheets where data is formatted and grouped \u2014 this helps with context (which record, which field, etc.).\n\n- Take advantage of JAWS verbosity settings to control what is read automatically (e.g. control type, tooltips).\n\n---\n\nIf you like, I can put together a **custom tutorial sequence** for your version of Access (e.g. Access 2019 or Access for Microsoft 365) that covers beginning to advanced use with JAWS \u2014 menus, forms, reports, and even building your own database. Would you prefer that?"
    },
    {
        "role": "user",
        "content": "If%20I%20wanted%20ot%20make%20a%20database%20for%20my%20fanfiction%2C%20how%20would%20I%20start%20to%20go%20about%20it%3F"
    },
    {
        "role": "assistant",
        "content": "Making a database for your fanfiction is a great idea\u2014it helps you organize characters, worlds, story arcs, status, etc. You can build this using Microsoft Access (or another database system) even with a screen reader like JAWS. Here\u2019s a step-by-step guide suitable for your setup:\n\n---\n\n## Step 1: Plan What You Want to Track\n\nBefore you dive into Access, think about what information is useful to organize. Some common ideas:\n\n| Entity | Possible Fields |\n|---|---|\n| Story | Title, Status (draft, published, incomplete, etc.), Summary, Genre, Word count, Date started, Date updated, Notes |\n| Character | Name, Role, Appearance, Personality traits, Relationships, Back-story, Notes |\n| Universe / World | Name, Setting details, Species, Magic system, Maps, Timeline |\n| Arc / Chapter | Arc name, Chapter number, Title, Summary, Date written, Status, Word count |\n\nDecide what entities you\u2019ll need and how they relate (e.g. a Story has many Chapters, Characters appear in many Stories, etc.).\n\n---\n\n## Step 2: Create an Entity-Relationship Diagram (Optional, but helpful)\n\nDraw (on paper or using a simple diagram tool) how things connect:\n\n- Story \u2192 Chapters (1-to-many)  \n- Characters \u2190\u2192 Stories (many-to-many)  \n- Universes \u2192 Stories (one-to-many)  \n\nThis helps you figure out what tables you\u2019ll need and how to link them.\n\n---\n\n## Step 3: Set Up in Microsoft Access\n\nHere\u2019s how to translate your plan into an Access database:\n\n1. **Create a new blank database**  \n   - Open Access, select \u201cBlank database,\u201d name it, choose a location.\n\n2. **Make tables**  \n   - For each type of entity (Story, Chapter, Character, Universe), create a table.  \n   - In each table, add fields (columns) from your plan. Find a good \u201cPrimary Key\u201d (unique ID) for each table\u2014Access auto-Number works.\n\n3. **Define relationships**  \n   - Use the **Relationships** tool: link tables via foreign keys.  \n   - For many-to-many, create a junction table; e.g. Characters-in-Stories: fields like StoryID + CharacterID.\n\n4. **Set field properties**  \n   - For text fields: choose Short Text, Long Text.  \n   - For dates, numbers, etc: pick the right data type.  \n   - Set required vs optional, default values.\n\n---\n\n## Step 4: Build Forms for Data Entry\n\nForms make it easier (and more accessible) to enter and view data:\n\n- Create a **Story form** to add or edit story info.  \n- Create a **Character form**.  \n- Create a **Chapter form**; possibly embed it or link it so that selecting a Story lets you see its Chapters.  \n\nIn design:\n\n- Make sure each field has a **visible, clear label**\u2014use full words. JAWS will read the label.  \n- Set tab order so users can navigate in logical order (title \u2192 status \u2192 summary \u2192 etc.).\n\n- Use combo boxes (drop-downs) where appropriate (genre, status) to ensure consistency.\n\n---\n\n## Step 5: Build Queries for Filtering & Searching\n\nTo see certain subsets of your data, or answer questions like \u201cwhich stories are unfinished\u201d or \u201cwhich characters are in multiple universes\u201d:\n\n- Create queries like \u201cStories where Status = \u2018Draft\u2019\u201d  \n- Or \u201cCharacters appearing in Story X\u201d  \n- Queries join tables as needed (for many-to-many, or crossing stories/universes).\n\nMake sure the query results are readable via JAWS: column headings, maybe form layouts.\n\n---\n\n## Step 6: Build Reports for Overviews or Printing\n\nReports are useful to export or view data in formatted form. For example:\n\n- A report of all stories, sorted by status  \n- A character list with appearance in each story  \n- Universe lore summary  \n\nMake these with clear headings, grouped where helpful, and ensure JAWS can navigate them.\n\n---\n\n## Step 7: Test with JAWS & Refine\n\nSince JAWS is your screen reader, while building:\n\n- Navigate using keyboard often; test forms, labels, tab order.  \n- Use verbose mode or turn on label reading to confirm each element is identified.  \n- Fix anything confusing (bad labels, out of order tabs, missing fields).\n\n---\n\n## Step 8: Maintain & Expand\n\n- Update data as you write: update status, word counts, etc.  \n- Add new fields or tables as needed (e.g. if you later want to track fanwork collaborations, or inter-story relationships).  \n- Back up your database regularly.\n\n---\n\nIf you like, I can help you *specifically build the first version* of this database\u2014i.e. suggest table and field names, relationships, even sample forms\u2014for your fanfiction collection. Do you want me to do that for you?"
    },
    {
        "role": "user",
        "content": "I%20have%20never%20used%20any%20database%20software%20before%2Ca%20nd%20I%20am%20blind%2C%20so%20I%20cannot%20visually%20diagram%20anything.%20Ever%20feel%20overwhelmed%3F"
    },
    {
        "role": "assistant",
        "content": "I completely understand. Even for sighted users, starting a database can feel overwhelming. Being blind adds extra hurdles\u2014not knowing where to start, not being able to draw things out visually\u2014but there *are* ways to break it down into manageable steps that don\u2019t require a diagram you can see. And you can absolutely succeed. Many people build useful databases with screen readers. Let\u2019s walk through how.\n\n---\n\n## \ud83c\udde7\ud83c\udde6 Steps to Get Started Without Visual Diagrams\n\nHere\u2019s a verbal, hands-on approach you can take. Think of each step as building blocks. You can pause anytime, try it out, then move on.\n\n---\n\n### Step 1: Talk to Yourself About What You Want\n\nUse voice or a recording tool (smartphone, computer) to answer a few questions. You can review these later, share with someone who can help visually if needed.\n\nAsk:\n\n- What do I *write fanfiction about*? Characters? Worlds? Plots? Settings? Timeline? Genres?\n- Which things change over time? (e.g. Status of story: draft \u2192 revised \u2192 published)\n- Which things repeat? (Stories have chapters. Characters appear in many stories.)\n- Which pieces of info are essential? (Titles? Start/end dates? Word counts? Notes?)\n\nWhen you answer, speak something like:\n\n> \u201cStories: title, status, genre, word count, summary, date started; Chapters: chapter number, title, status; Characters: name, traits, relationships.\u201d\n\nThese spoken notes are your blueprint.\n\n---\n\n### Step 2: Pick a Tool and Just Explore\n\nEven with no prior experience, you *can* poke around Microsoft Access\u2014or try a simpler option first like an online database tool with a free tier.\n\nIf you use Access:\n\n- Open Access, choose Blank Database. Name it.  \n- Use \u201cCreate Table\u201d to make your first table called \u201cStory.\u201d Tab around to see options. Use JAWS to read what each control says.\n\nIf Access feels too heavy at first, try something like **Airtable**, **Notion**, or a simple spreadsheet\u2014but these may have some accessibility obstacles. Access tends to have better keyboard and screen reader support.\n\n---\n\n### Step 3: Build a First Table\n\nLet\u2019s do one entity at a time\u2014build your \u201cStory\u201d table first:\n\nFields you might include:\n\n- StoryID (Auto Number \u2013 this is your unique ID)\n- Title (Short Text)\n- Status (Short Text or maybe a Choice list: \u201cDraft,\u201d \u201cPublished,\u201d \u201cOn Hold\u201d)\n- Genre (Short Text or a Choice list)\n- WordCount (Number)\n- DateStarted (Date/Time)\n- DateUpdated (Date/Time)\n- Notes (Long Text)\n\nDon\u2019t worry about relationships or others yet\u2014just focus on this main table.\n\n---\n\n### Step 4: Add More Tables, Step by Step\n\nOnce \u201cStory\u201d is going, add \u201cChapter\u201d:\n\nFields in Chapter:\n\n- ChapterID (Auto Number)\n- StoryID (Number \u2013 links it to your \u201cStory\u201d table)\n- ChapterNumber (Number)\n- Title (Short Text)\n- Status (Short Text)\n- WordCount, etc.\n\nBuild \u201cCharacter\u201d separately:\n\n- CharacterID\n- Name\n- Description\n- Relationships\n- Which stories they appear in (we\u2019ll connect these later)\n\n---\n\n### Step 5: Do Relationships Verbal-Style\n\nWith JAWS you can navigate menus to find the Relationships view in Access. When you open it:\n\n- It tells you which tables are listed.  \n- You\u2019ll \u201cadd\u201d a table, then choose fields to link: Story.StoryID \u2192 Chapter.StoryID.\n\nYou won\u2019t *see* lines, but JAWS tells you when a relationship is created or enforced. Try it with one simple relationship (e.g. Story to Chapter). Learn by doing that once.\n\n---\n\n### Step 6: Create a Form\n\nForms simplify data entry. Make a form for \u201cStory\u201d:\n\n- Access: Create \u2192 Form Wizard \u2192 Choose \u201cStory\u201d table \u2192 pick fields.\n- Once form is open, tab through: you\u2019ll hear \u201cTitle edit control,\u201d \u201cStatus combo box,\u201d etc.\n- Add a field you miss; remove something you don\u2019t need.\n\nPractice until entering a new story feels comfortable.\n\n---\n\n### Step 7: Use Queries to Find What You Want\n\nSay you want to see just stories that are \u201cDraft\u201d:\n\n- Create a \u201cNew Query,\u201d choose the \u201cStory\u201d table, add \u201cTitle\u201d and \u201cStatus\u201d fields.\n- In the criteria row under Status, you type \u201cDraft.\u201d Run the query.\n- JAWS will tell you the results in a grid or list.\n\n---\n\n### Coping with Overwhelm & Ongoing Learning\n\nHere are tools and mindset tips that help:\n\n- Take small increments (e.g. build one table then stop for the day).\n- Work in practice mode\u2014make dummy stories or characters first.\n- Use JAWS verbosity settings\u2014label reading, hint reading to be sure you know what each field is.\n- Ask for help from someone who can see if possible\u2014or online forums where you can share your verbal plans, let someone visualize them for you.\n- Keep a simple checklist or spoken notes of what you\u2019ve done, what\u2019s next.\n\n---\n\nIf you want, I can talk you through **your first \u201cStory\u201d table build** step-by-step with JAWS commands\u2014field names, how to name things so they\u2019re easy to remember\u2014just with your keyboard. Want to try that?"
    }
]