Microsoft Access Database - Cell Data Type not read

[Qchristensen]

Steps to reproduce:

1. Open Microsoft Access
2. Creat a "Blank Database".
3. Choose Design View: alt+h, w, d
4. Press ENTER to save the table as prompted
5. TAB once to "Data Type".
6. Press alt+down arrow to open the list of data types
7. Arrow though the data types

Actual behavior:

At Steps 5 and 6, NVDA does not read the data types.

Expected behavior:

NVDA should read the data types

System configuration

NVDA installed/portable/running from source:

NVDA version:

NVDA 2020.4

Windows version:

Windows 10 (64-bit) Version: 2009, Build: 19042

Name and version of other software in use when reproducing the issue:

Other information about your system:

Office 365 (64-bit) Version: 16.0.13801.20214
Also reported against Office 2010 - I assume it's always been an issue.

Other questions

Does the issue still occur after restarting your computer?

Yes

Have you tried any other versions of NVDA? If so, please report their behaviors.

If add-ons are disabled, is your problem still occurring?

No add-ons

Did you try to run the COM registry fixing tool in NVDA menu / tools?

[Brian1Gaff]

Did this ever work. I have had no end of strange non reading things and lock ups with varies incarnations of Microsoft access way back since xp days. Its a bit of a cludged together bit of software, but I have to use it, sadly.. Brian ***@***.*** Sent via blueyonder. Please address personal E-mail to:- ***@***.***, putting 'Brian Gaff' in the display name field. Newsgroup monitored: alt.comp.blind-users ----- Original Message ----- From: "Quentin Christensen" ***@***.***> To: "nvaccess/nvda" ***@***.***> Cc: "Subscribed" ***@***.***> Sent: Sunday, March 14, 2021 10:27 PM Subject: [nvaccess/nvda] Microsoft Access Database - Cell Data Type not read (#12167)

…

<!-- Please read the text in this edit field before filling it in. Please thoroughly read NVDA's wiki article on how to fill in this template, including how to provide the required files. Issues may be closed if the required information is not present. https://github.com/nvaccess/nvda/wiki/Github-issue-template-explanation-and-examples Please also note that the NVDA project has a Citizen and Contributor Code of Conduct which can be found at https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md. NV Access expects that all contributors and other community members read and abide by the rules set out in this document while participating or contributing to this project. This includes creating or commenting on issues and pull requests. --> ### Steps to reproduce: 1. Open Microsoft Access 2. Creat a "Blank Database". 3. Choose Design View: alt+h, w, d 4. Press ENTER to save the table as prompted 4. TAB once to "Data Type". 5. Press alt+down arrow to open the list of data types 6. Arrow though the data types ### Actual behavior: At Steps 5 and 6, NVDA does not read the data types. ### Expected behavior: NVDA should read the data types ### System configuration #### NVDA installed/portable/running from source: #### NVDA version: NVDA 2020.4 #### Windows version: Windows 10 (64-bit) Version: 2009, Build: 19042 #### Name and version of other software in use when reproducing the issue: #### Other information about your system: Office 365 (64-bit) Version: 16.0.13801.20214 Also reported against Office 2010 - I assume it's always been an issue. ### Other questions #### Does the issue still occur after restarting your computer? Yes #### Have you tried any other versions of NVDA? If so, please report their behaviors. #### If add-ons are disabled, is your problem still occurring? No add-ons #### Did you try to run the COM registry fixing tool in NVDA menu / tools? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #12167

[Qchristensen]

I must admit I don't know, I haven't really touched Access in years - someone reported this and as it was a relatively simple standalone thing I could easily test and reproduce, I wrote it up.

[lukaszgo1]

My impression was that since NVDA has no explicit support for MS Access issues there aren't going to be looked at. Has there been a change in that regard?

[Qchristensen]

It's not that NVDA deliberately doesn't support Access - more it's a range of issues:

• The accessibility of MS Access is not quite at the same level as other Office programs
• NVDA could likely work better in Access (from our end).
• Access is not as widely popular as say Word or Excel, and we try to prioritise issues which will have the most beneficial impact to the widest number of users, so they may not be prioritised as highly.

I'd still encourage anyone to report issues with Access or any other program.