Dante
It is mostly in self-written applications, as I didn't know about the
AutomationProperty. I am going to give it a try as soon as possible and
will reach out again when neededn.
Thank you very much.
Sincerely, Jordy.
On 10/23/2018 10:13 PM, Dante Gagne (Redacted sender danteg for DMARC)
wrote:
In WPF, there is a dependency property, namely AutomationProperties.LabeledBy** To leave the list, click on the immediately-following link:-
which you can databind by reference to another control. So, consider the
following snippet of XAML:
<Grid>
<TextBlock x:Name="ReferenceLabel" Text="Enter Address Here"/>
<TextBox x:Name="AddressBox" AutomationProperties.LabeledBy="{Binding
ElementName=textBlock, Mode=OneWay}"/>
</Grid>
In this case, the first TextBlock has a name specified and the TextBox has an
automation property set on it that indicates the association between the two.
It sounds like JAWS understands this relationship and when it encounters a
TextBlock (or any Text entry control) that exposes this automation property, it
knows to follow it to the given label and read the text. Developers could also
choose to bind the HelpText to the Text property of the label or any other
similar relationship.
This one feels like one that's worth referring to NVDA. My concern, though, is
that I'm not 100% sure this is called out in the UIA specification. And if it's
not, this might be a solution that's limited specifically to XAML based
applications.
As far as the braille display, I'm not 100% sure of the expected behavior here.
If keyboard focus were to go to the TextBox I described above, what should be
displayed on the Braille display? The current contents of the box? The label
describing the box? I'm not entirely sure how it should behave and my gut says
that this is a configuration on how the screen reader works with the Braille
display, isn't it? You'd click something on the keyboard to tell the braille
display to switch from one value to the next, correct?
--Dante
-----Original Message-----
From: program-l-bounce@xxxxxxxxxxxxx <program-l-bounce@xxxxxxxxxxxxx> On Behalf
Of Jordy Deweer
Sent: Tuesday, October 23, 2018 12:42 PM
To: program-l@xxxxxxxxxxxxx
Subject: [program-l] Re: VS2017: Two issues
Hi Dante and others
WPF itself has (using NVDA) an issue with field labeling. It is namely
impossible to see the label for a TextBox in braille when using NVDA. In Jaws,
the labels are correctly shown.
Do I need to link the labels to the TextBox - as we need to do in HTML to make
sure that screen readers find the right label - or should that work
out-of-the-box? If we need to connect them: how?
Thank you in advance for any response.
Sincerely, Jordy.
On 10/23/2018 8:20 PM, Dante Gagne (Redacted sender danteg for DMARC) wrote:
Jaffar, the freeze that you're seeing... is that with Azure DevOps (VSTS)? And" ay+ -faq=
do you see that lock with both NVDA and JAWS? If that's true, then this *IS* a
much bigger issue than I thought. I'm not aware of a freeze on new project
solution creation, but if you're running into it, I want to know more.
Additionally, more fuel to put on the fire to get the WPF guys to address the
situation would be useful.
-----Original Message-----
From: program-l-bounce@xxxxxxxxxxxxx <program-l-bounce@xxxxxxxxxxxxx>
On Behalf Of Jaffar Sidek
Sent: Monday, October 22, 2018 8:42 PM
To: program-l@xxxxxxxxxxxxx
Subject: [program-l] Re: VS2017: Two issues
Hi. This is negatively impacting screen readers in more ways than anticipated.
I usse both NVDA and Jaws, and in my case VS2017 freezes at the stage where a
new project solution has been created. It would be interesting to know if
there is such a great difference in the code base from the 15.76 to the
15.87.builds. Hope this gets resolfved soon. Cheers!
On 23/10/2018 2:49 AM, Dante Gagne (Redacted sender danteg for DMARC) wrote:
It is, unfortunately, a known issue, and it's a very deep issue in the way that" ay+ -faq=
WPF and JAWS interact with each other. And, unfortunately, since it is such a
deep issue, it's been taking FAR longer than it should to get it fixed. I
really wish I had better news about it. It's easily the single biggest item I'm
embarrassed about and one of the most impactful to folks who use JAWS
specifically.
I'll dive into it again and see if I can get the glacier to move.
--Dante
Senior Program Manager
Microsoft - Visual Studio
-----Original Message-----
From: program-l-bounce@xxxxxxxxxxxxx <program-l-bounce@xxxxxxxxxxxxx>
On Behalf Of Soronel Haetir
Sent: Sunday, October 21, 2018 1:08 PM
To: program-l@xxxxxxxxxxxxx
Subject: [program-l] Re: VS2017: Two issues
With jaws you can avoid it by using the jaws cursor and seeing that it's there
and shift+tabbing rather than tabbing so you never focus on the notification
but honestly I usually forget and have to restart VS.
It has been in VS2017 from the beginning although it's much more recently that
I took the time to inform MS and got a known issue response.
On 10/21/18, Jordy Deweer <jordyydeweer@xxxxxxxxx> wrote:
Soronel Haetir wrote:--
The notification crash is a known issue and so far as I know we're
still waiting on a fix.
Are there ways to avoid crashing? And how long has it been going on?
On 10/20/2018 10:39 PM, Soronel Haetir wrote:
The notification crash is a known issue and so far as I know we're
still waiting on a fix.
On 10/20/18, Jordy Deweer <jordyydeweer@xxxxxxxxx> wrote:
Dear all
I have two issues with Visual Studio 2017 (Community).
The first problem is the following: when I work with the Team
Explorer (to manipulate Git), everything works fine, until I commited something.
After commiting, an extra part in the window appears, which
ontains notifications. If I press Tab to go back to the list of,
for example, unstaged items, I need to pass-by that notifications area.
But, VS crashes as soon as the notifications area gets the focus
(using tab). Is that a known problem, can it be resolved by a
modification in the settings, etc.? When tere are errors and I try
to read the notifications from the Team Explorer window, the first
line goes well, but as soon as I press one of the panning buttons
on my Focus 40 Blue (4th Gen) braille display, everything crashes
as well, just like it does when tere are no errors and the notifications box
get the focus...
My second problem is that, when I am using JAWS 2018 to edit code,
it happens that the braille stays on the "mnu text editor" message
of IntelliSense, while I am back in the code itself with my focus.
The speech works fine though. I tried maximalizing the window,
restarting everything, but it did not resolve the problem. Hereby
needs to be said that it doesn't always happen. When I am in
trouble, a simpel restart of JAWS is enough to solve everything- until it
happens again.
Is there a way to solve the above problems or will there need to
be bug fixes in Visual Studio?
Thanks in advance for possible replies.
Yours faithfully
Jordy Deweer
** To leave the list, click on the immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** program-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** program-l-request@xxxxxxxxxxxxx with the Subject:- faq
Soronel Haetir
soronel.haetir@xxxxxxxxx
** To leave the list, click on the immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** program-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** program-l-request@xxxxxxxxxxxxx with the Subject:- faq
N ^j b % ( ^ i v& z\ Yh ) )䙨 k
ښZު笵 zX + ˛ -鹻 & ! a b Ghz jg k
ښZު笵 zX + ݊{ay+ - )*^ {.n + - \ i , Z jب j y brJ'
g ^ ' Z0 x% y&j)m 肶 -~ +- y } ǧu Ơz ) +jikz y
b (
** To leave the list, click on the immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** program-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** program-l-request@xxxxxxxxxxxxx with the Subject:- faq
N ^j b % ( ^ i v& z\ Yh ) )䙨 k
ښZު笵 zX + ˛ -鹻 & ! a b Ghz jg k
ښZު笵 zX + ݊{ay+ - )*^ {.n + - \ i , Z jب j y brJ'
g ^ ' Z0 x% y&j)m 肶 -~ +- y } ǧu Ơz ) +jikz y
b (
** To leave the list, click on the immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** program-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** program-l-request@xxxxxxxxxxxxx with the Subject:- faq
N�^j����b��%��(��^�i�v&�z\��Yh�)��)䙨���k�
ښZު笵��zX���+�˛��-鹻 �&�!�a��b�Ghz�������jg��� ��k�
ښZު笵��zX���+��݊{ay+���-�)*^�{.n�+�����-����\�i���,��Z���jب�j y�brJ'���g���^�'�Z0�x%�y&j)m��肶������-~���+-�����y�}���ǧu���Ơz�)��+jikz�����y�b��(�
"�ay+���-faq=
