- From: James Nurthen <nurthen@adobe.com>
- Date: Thu, 11 Feb 2021 16:54:09 +0000
- To: ARIA Working Group <public-aria@w3.org>
- Message-ID: <BY5PR02MB6979D3C467352A9F87DAD4D6A68C9@BY5PR02MB6979.namprd02.prod.outlook.com>
Note to ARIA folks - this is NOT the same as the usual meeting number Join Zoom Meeting https://mit.zoom.us/j/<https://mit.zoom.us/j/97458924977>97458924977<https://mit.zoom.us/j/97458924977> Meeting ID: 974 5892 4977 US : +1 646 558 8656 or +1 669 900 6833 IRC: #aria-dive ________________________________ From: James Nurthen Sent: Wednesday, February 10, 2021 10:34 AM To: ARIA Working Group <public-aria@w3.org> Subject: Deep Dive call Thursday Feb 11, 2021 9am PST / noon EST Please find call details at https://github.com/w3c/aria/issues/1371#issuecomment-776310886 [https://avatars.githubusercontent.com/u/379216?s=400&v=4]<https://github.com/w3c/aria/issues/1371#issuecomment-776310886> Detectability of assistive technology · Issue #1371 · w3c/aria · GitHub<https://github.com/w3c/aria/issues/1371#issuecomment-776310886> If I understand the test page correctly, the cause is the screen reader, because screen readers convert keyboard events into click events. I have tested Firefox with JAWS and NVDA and in both cases the screen reader is recognized correctly. In JAWS I can set that the conversion of events should not take place and then JAWS is also no longer recognized. github.com Issue background can be found in that same issue. Regards, James
Received on Thursday, 11 February 2021 16:54:29 UTC