Skip to content

Jaws screen reader  #11730

Closed
Closed

Description

@gomaltao

Windows Terminal seems to be totally inaccessible with the JAWS screen reader.

Activity

  1. ghost added
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Nov 11, 2021
  2. ghost added
    Needs-Tag-FixDoesn't match tag requirements
    on Nov 11, 2021
  3. zadjii-msft commented on Nov 11, 2021

    @zadjii-msft
    Member

    Which version of the Terminal? Which OS version? Which JAWS version? I'm pretty sure JAWS is supposed to work... /cc Carlos Zamora (@carlos-zamora)

  4. carlos-zamora commented on Nov 11, 2021

    @carlos-zamora

    Bill Dengler (@codeofdusk) I know you use NVDA a lot, have you tried using JAWS? Or have you heard from any JAWS users trying to use Windows Terminal at all?

  5. codeofdusk commented on Nov 11, 2021

    @codeofdusk
    Contributor

    Sorry, no.

    Graham Pearce (@Grahamwp) What happens if you try and run wt from the run dialog on your machine? Is the opened terminal accessible at all?

  6. gomaltao commented on Nov 11, 2021

    @gomaltao
    Author

    Windows Terminal 1.11.2921.0
    OS Name: Microsoft Windows 10 Pro
    OS Version: 10.0.19042 N/A Build 19042
    JAWS Version 2020.2012.13 ILM

    I have tried to use WT since the first beta without any success with JAWS.

  7. ghost added
    Needs-AttentionThe core contributors need to come back around and look at this ASAP.
    on Nov 11, 2021
  8. ghost removed
    Needs-Author-FeedbackThe original author of the issue/PR needs to come back and respond to something
    on Nov 11, 2021
  9. gomaltao commented on Nov 11, 2021

    @gomaltao
    Author

    I closed the issue by misstake.

  10. Grahamwp commented on Nov 12, 2021

    @Grahamwp

    I can confirm this is the case with Windows Terminal version 1.11.2921.0and the latest version of JAWS, 2022.2110.36.400.

  11. zadjii-msft commented on Nov 15, 2021

    @zadjii-msft
    Member

    I'm kinda shocked that JAWS doesn't work at all. We should fix that. Does the vintage console host work? If it does, then it shouldn't be too hard to find the piece of console code we're missing in the Terminal that makes JAWS work.

  12. 32 remaining items

  13. Grahamwp commented on Nov 17, 2021

    @Grahamwp

    There's also relevant documentation from Freedom Scientific but I wouldn't personally be able to further help with this on the JAWS scripting side.

  14. carlos-zamora commented on Nov 17, 2021

    @carlos-zamora

    FYI, I've managed to reach out to JAWS. Hoping I can provide some direct support to them. They are definitely aware of this issue and I've even forwarded them this GitHub issue. 🙂

  15. ghost added
    Needs-Tag-FixDoesn't match tag requirements
    on Feb 7, 2022
  16. zadjii-msft commented on Feb 7, 2022

    @zadjii-msft
    Member

    Moving this into 1.14 based on recent conversations.

  17. ghost removed
    Needs-Tag-FixDoesn't match tag requirements
    on Feb 7, 2022
  18. zadjii-msft commented on Mar 17, 2022

    @zadjii-msft
    Member

    Carlos Zamora (@carlos-zamora) should have fixed this in #12358, and confirmed that JAWS made the fix on their end as well. We're not sure exactly which version of JAWS the fix is in, but it should be in the next version of the Terminal.

  19. ghost added
    Needs-Tag-FixDoesn't match tag requirements
    on Mar 17, 2022
  20. ghost removed
    Needs-Tag-FixDoesn't match tag requirements
    on Mar 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Area-AccessibilityIssues related to accessibilityIssue-BugIt either shouldn't be doing this or needs an investigation.Priority-1A description (P1)Product-TerminalThe new Windows Terminal.Resolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions