[
    {
        "role": "user",
        "content": "Is%20there%20a%20database%20program%20that%20is%20accessible%20with%20the%20Jaws%20screen%20reader%3F"
    },
    {
        "role": "assistant",
        "content": "Yes \u2014 there *are* several database applications designed to be accessible with JAWS (Job Access With Speech), a popular screen reader for Windows. Whether an app will work well with JAWS depends on how well its user interface supports accessibility (especially keyboard navigation, appropriate labeling of controls, and support for Windows accessibility APIs). Below are some good options and what to look for, plus tips to choose a program that will work well for your needs.\n\n---\n\n## \u2705 Database Applications Known to Support JAWS\n\nHere are a few database tools that explicitly provide support for JAWS or have accessibility documentation confirming compatibility:\n\n| Application | How It Supports JAWS / Accessibility Features |\n|-------------|------------------------------------------------|\n| **Microsoft Access** (Office Desktop) | Microsoft offers help documents on how to use Access with screen readers such as JAWS, NVDA, or Narrator. You can create tables, queries, forms, reports, and charts using only keyboard and screen reader. ([support.microsoft.com](https://support.microsoft.com/en-us/accessibility/access/screen-reader-support-for-access?utm_source=openai)) |\n| **Oracle SQL Developer** | Provides strong accessibility support. It uses Java Access Bridge to interface with screen readers. Features include full keyboard access, readable menus and dialogs, configurable fonts and colors, and logic to alert screen reader users to errors. ([docs.oracle.com](https://docs.oracle.com/en/database/oracle/sql-developer/22.2/sqdac/sql-developer-accessibility-information.html?utm_source=openai)) |\n| **MySQL Workbench** | On Windows, MySQL Workbench supports Microsoft Active Accessibility (MSAA) to enable screen reader compatibility. You can adjust font sizes, select high-contrast themes, and change the look and feel to make it easier to use with JAWS. ([dev.mysql.com](https://dev.mysql.com/doc/workbench/en/wb-accessibility.html?utm_source=openai)) |\n\n---\n\n## \u26a0 Things to Check Before You Pick an App\n\nEven if an app claims or appears to support accessibility, performance can vary depending on how it's built. Here\u2019s what you should verify:\n\n1. **Use of Accessibility APIs**  \n   Tools should support MSAA, UI Automation, or Java Access Bridge. Without those, screen readers like JAWS struggle to get useful information from the interface.\n\n2. **Keyboard Navigation**  \n   You should be able to do most actions without the mouse \u2014 opening menus, browsing tables/views, editing fields, running queries, navigating forms, etc.\n\n3. **Screen Reader Readability**  \n   Proper labeling of controls (buttons, fields, dialogs), readable status messages, alerts, menus spoken clearly, and avoiding unlabeled graphics or icons without textual equivalents.\n\n4. **Adjustable Display Settings**  \n   Features like high contrast mode, scalable fonts, color themes, and the ability to disable or modify highly visual decorations help a lot.\n\n---\n\n## \ud83d\udca1 Other Options & Alternatives\n\nIf a tool you need to use isn\u2019t accessible enough, or if GUI apps are too cumbersome, there are alternatives:\n\n- **Command-line tools**: SQL shells or terminal-based interfaces tend to be more accessible because everything is keyboard-based, reducing reliance on unlabelled UI elements.\n\n- **Minimal GUIs + scripting**: Some tools allow scripting or have basic editors that are more screen-reader friendly (e.g. Oracle SQL Developer\u2019s source editor).\n\n- **Custom scripts or add-ons**: Where an application lacks accessibility, sometimes users create JAWS scripts (JAWS Scripting Language, JSL) to improve interaction with specific elements. If you plan to use a tool often, checking whether there\u2019s a community plug-in or script helps.\n\n---\n\nIf you tell me which database system you're using (for example, Access, MySQL, PostgreSQL, etc.) and whether you prefer GUI vs command-line, I can suggest options that are *likely* to work well with JAWS for *your specific* use case."
    },
    {
        "role": "user",
        "content": "I%27ve%20never%20used%20a%20database%20program%20before%2C%20but%20I%20do%20have%20the%20latest%20Microsoft%20365."
    },
    {
        "role": "assistant",
        "content": "Since you have Microsoft 365, you already own tools that can work as databases, and a lot of them are accessible with JAWS. I\u2019ll walk you through what you have, what might work best, and provide specific things to look for to make sure it feels usable.\n\n---\n\n## \ud83d\udd0d What Database Options You Have with Microsoft 365\n\nHere are a few Microsoft tools included (or available) in Microsoft 365 that can store, manage, and let you work with structured data. Some are simpler than others.\n\n| Tool | How It Works | What It\u2019s Good For |\n|------|---------------|----------------------|\n| **Microsoft Access (Desktop)** | A full database app. You can create tables (like spreadsheets, but structured), forms (for data entry), queries, reports. |\n| **Microsoft Lists** | Part of Microsoft 365. Lets you store and track data like in a spreadsheet (for example: tasks, inventory, issue tracking). Works across SharePoint, Teams, and the browser. |\n| **Power Apps + Dataverse** | For building custom apps that store data. Dataverse is like a more powerful, cloud-based table storage with relationships between data. Power Apps gives you forms or app-like interfaces to interact with that data. |\n\n---\n\n## \u2705 Which of These Are Accessible with JAWS?\n\nBased on Microsoft\u2019s latest documentation:\n\n- **Microsoft Access** (desktop version via Microsoft 365) explicitly supports screen readers including JAWS, NVDA, and Narrator. That means you can use Access to:\n  - Create tables, queries, forms, reports, charts  \n  - Do imports and exports  \n  ([support.microsoft.com](https://support.microsoft.com/en-us/accessibility/access/screen-reader-support-for-access?utm_source=openai))\n\n- **Microsoft Lists** supports screen readers (JAWS, NVDA, Narrator). You can use it to:\n  - Create and edit lists, share them, manage them using keyboard + screen reader commands.  \n  ([support.microsoft.com](https://support.microsoft.com/en-us/office/screen-reader-support-for-microsoft-lists-61b45b20-aede-4e4a-9fc8-1f8dcdf4a88c?utm_source=openai))\n\n- **Power Apps (Model-driven apps)**: Microsoft also states that model-driven Power Apps are accessible. These let you build apps (like simple front-ends) that work with database-like data sources (such as Dataverse). ([learn.microsoft.com](https://learn.microsoft.com/en-us/power-apps/user/screen-reader?utm_source=openai))\n\n---\n\n## \ud83d\udee0 What Might Be Best for a New User\n\nIf you\u2019re just starting out, here\u2019s how I\u2019d rank these, based on ease of use + accessibility:\n\n1. **Microsoft Lists**  \n   Best for very simple database tasks\u2014easy to start, low setup, works in browser/Teams/shareable, accessible.\n\n2. **Microsoft Access (Desktop)**  \n   More powerful. Lets you build everything from scratch. Slightly steeper learning curve, but since it supports JAWS, you can do quite a lot just with keyboard and screen reader once you get used to it.\n\n3. **Power Apps + Dataverse**  \n   More advanced. Good if you want apps that work across devices, need more structure (relationships between data), or want something you can customize more heavily. Might require a bit of learning or help.\n\n---\n\n## \ud83d\udd27 What Features to Look for or Enable in Each Tool\n\nTo make sure you get the best JAWS experience, keep these in mind:\n\n- Make sure **keyboard navigation** works: Tab, Shift-Tab, Arrow keys should let you move around forms, tables, grid views, menus.\n- Forms and fields should have **labels** or descriptions that a screen reader can recognize.\n- Use templates where possible\u2014they often have built-in structure that\u2019s more consistent.\n- When building forms, reports, or views, test them with your screen reader to see which controls are announced clearly.\n- For Lists and Power Apps, ensure you use accessible layout options (like list, grid) rather than overly visual ones that might be hard to use with screen reader.\n\n---\n\nIf you like, I can suggest a few step-by-step options or even sample templates for Microsoft Access or Lists that work well with JAWS so you can try one out. Do you want to go with the simplest (Lists) or something a bit more complex (Access or Power Apps)?"
    }
]