[Screenreader Accessibility] Make GPT4All screenreader accessible

[shadowplumber]

Make GPT4All screenreader accessible

I work for a university in Utah, and we have a full accessibility department who has to test new software before we can offer it to students. I'm going to paste the results of their accessibility test below (everything that pertains to screenreader accessibility). Since it's "GPT4All", making the desktop applications accessible should hopefully be a big priority :)

Test report summary:

GPT4All was tested for minimum functional accessibility using a Windows computer and JAWS screenreader. The following accessibility issues were identified:

1. User is unable to navigate application using a screenreader.

Accessibility testing indicates that GPT4All is likely to present accessibility barriers to some individuals with disabilities.

Fine-grained test report

• Test: JAWS: down arrow to read through page
  • Expected Outcome: Should be able to read all text, links, buttons, etc.
  • Actual Outcome: User is unable to read text, links, buttons.
  • Result: FAIL
  • Severity: Blocker
• Test: JAWS: tab/shift-tab to read through page
  • Expected Outcome: Should be able to access all controls and each control should be operable from the keyboard alone.
  • Actual Outcome: User is able to access/operate controls; however, not all interactive elements have associated, accessible labels.
  • Result: FAIL
  • Severity: Blocker
• Test: JAWS: JAWS: Heading Nav (Insert-F6)
  • Expected Outcome: Should open heading structure menu; should be able to navigate to each heading using arrow keys and activate by using enter key.
  • Actual Outcome: JAWS simply reads "F6" aloud.
  • Result: FAIL
  • Severity: Blocker
• Test: JAWS: Links Nav (Insert-F7)
  • Expected Outcome: Should open link navigation menu; links in list should have meaning in context and list.
  • Actual Outcome: JAWS simply reads "F7" aloud.
  • Result: FAIL
  • Severity: Blocker
• Test: JAWS: Lists (L) Key
  • Expected Outcome: Should notify user of lists on page and number of items in list; lists should be navigable from the keyboard alone.
  • Actual Outcome: JAWS simply reads the letter "L" aloud.
  • Result: FAIL
  • Severity: Blocker
• Test: JAWS: JAWS: Forms Nav (F)
  • Expected Outcome: Should list form fields in order.
  • Actual Outcome: JAWS simply reads the letter "F" aloud.
  • Result: FAIL
  • Severity: Blocker
• Test: JAWS: Table Nav (T)
  • Expected Outcome: Should give information regarding number of table columns/rows and read them in order.
  • Actual Outcome: JAWS simply reads the letter "T" aloud.
  • Result: FAIL
  • Severity: Blocker
• Test: Alt Text
  • Expected Outcome: All non-text content should have descriptive alternative text.
  • Actual Outcome: There are no images, so test was not run.
  • Result: N/A
  • Severity: N/A

[manyoso]

Is there an app or test harness that can be used during development that would aid in fixing this? Once I think I've made a change that fixes it... how can I test it locally?

[shadowplumber]

JAWS would be your best bet, since that's what was used to test: download JAWS webpage. I'm pretty sure (but not certain) there is a free trial included.

[shadowplumber]

Or I’ve been told you can use this program, which is free: https://www.nvaccess.org/download/