E-mail List Archives
Thread: Silence after user action
Number of posts in this thread: 6 (In chronological order)
From: Sumit Patel
Date: Tue, Apr 30 2024 12:12PM
Subject: Silence after user action
No previous message | Next message →
Hai all,
It is really if screen reader is silent after user action .
But, Is it a WCAG failure if there is no change on the screen after that
action For example : Clicking Copy button copies the above sentence to
clipboard . But, ther is no status message or any other visual clu that it
has been copied. Similarly, after successfully submitting a form within a
dialog closes the dialog . Here also no status message or no change on the
page .
Here in the first scenario, a Visually Impaired user would not come to know
whether the text copied to clipboard or not unless they read the clipboard
content. In the second scenario, keyboard focus set back to the button
which the user initially clicked to open the dialog . They didn't get any
message to notify them that the form was submitted successfully .
Do I need to mark these scenarios as violations of 4.1.3 or just best
practices which are good to have
Would like to know your thoughts
Regards,
Sumit.
From: Dean.Vasile@outlook.com
Date: Tue, Apr 30 2024 12:16PM
Subject: Re: Silence after user action
← Previous message | Next message →
I see that behavior a lot with NVDA. I think there are some settings. You might be able to adjust there, but otherwise it does not always speak when you perform tasks for example, if you copy text, it does not say copied, but it does do the task.
On the other hand, JAWS gives you a whole lot more feedback and rarely do you have situations where it doesnât speak.
Dean Vasile
617-799-1162
> On Apr 30, 2024, at 2:12â¯PM, Sumit Patel < = EMAIL ADDRESS REMOVED = > wrote:
>
> Hai all,
>
> It is really if screen reader is silent after user action .
> But, Is it a WCAG failure if there is no change on the screen after that
> action For example : Clicking Copy button copies the above sentence to
> clipboard . But, ther is no status message or any other visual clu that it
> has been copied. Similarly, after successfully submitting a form within a
> dialog closes the dialog . Here also no status message or no change on the
> page .
>
> Here in the first scenario, a Visually Impaired user would not come to know
> whether the text copied to clipboard or not unless they read the clipboard
> content. In the second scenario, keyboard focus set back to the button
> which the user initially clicked to open the dialog . They didn't get any
> message to notify them that the form was submitted successfully .
>
> Do I need to mark these scenarios as violations of 4.1.3 or just best
> practices which are good to have
>
> Would like to know your thoughts
>
> Regards,
> Sumit.
> > > >
From: David Farough
Date: Tue, Apr 30 2024 12:53PM
Subject: Re: Silence after user action
← Previous message | Next message →
Initially I thought that the screenreader usually indicates whether or not text was copied.
In this case however it sound like the user is activating a button to perform the copying.
In this scenario perhaps using Aria-Pressed on the button would do the trick.
For the form submission, it seems to me that some sort of status message should appear in the dialogue.
From: Patrick H. Lauke
Date: Tue, Apr 30 2024 12:58PM
Subject: Re: Silence after user action
← Previous message | Next message →
On 30/04/2024 19:12, Sumit Patel wrote:
> It is really if screen reader is silent after user action .
> But, Is it a WCAG failure if there is no change on the screen after that
> action For example : Clicking Copy button copies the above sentence to
> clipboard . But, ther is no status message or any other visual clu that it
> has been copied.
In this case, there doesn't seem to be an actual WCAG failure (as 4.1.3
Status Messages, for instance, only applies if there's a visible
status/confirmation message which would then need to be announced). As a
best practice though, you probably want to have some form of
confirmation (both for screen readers and non-SR users alike), which
then you do want to have announce as a live region for instance.
> Similarly, after successfully submitting a form within a
> dialog closes the dialog . Here also no status message or no change on the
> page .
Closing a dialog should result in focus being moved (explicitly)
somewhere sensible (which then, in turn, should result in the newly
focused thing being announced, which gives an indication that something
happened to SR users). If focus is just lost, that's generally a failure
of 2.4.3 Focus Order .
P
--
Patrick H. Lauke
* https://www.splintered.co.uk/
* https://github.com/patrickhlauke
* https://flickr.com/photos/redux/
* https://mastodon.social/@patrick_h_lauke
From: Weston Thayer
Date: Tue, Apr 30 2024 1:01PM
Subject: Re: Silence after user action
← Previous message | Next message →
In the copy scenario, any chance the Copy button disappears after invoking
(like if it was in a tooltip or menu that showed on text selection)? If so
that'd make it similar to the dialog.
From: Ben Moxey
Date: Wed, May 01 2024 5:11PM
Subject: Re: Silence after user action
← Previous message | No next message
This is a multi-part message in MIME format.
------_=_NextPart_f2319852-f97d-49f8-8fec-5d5611dcb94e
Content-Language: en-US
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Hi everyone
To clarify Dean's comment regarding NVDA and JAWS speaking copy, paste etc,=
these are screen reader specific announcements that can be configured when=
you are manually performing these actions. Note that NVDA requires an add-=
on for this functionality. However, if you are using a dedicated button on =
a website to copy information to the clipboard, this should always trigger =
a confirmation announcement to let the screen reader user know it worked.
If anyone wants to configure NVDA to announce copy, paste etc in general, i=
nstall a simple add-on called Clipspeak from the add-on Store (NVDA menu/To=
ols/Add-on Store). If you do start experimenting with add-ons (there are so=
me fantastic features you can install), it's always a good idea to run NVDA=
with them disabled when testing. The easiest way to do this is from the Ex=
it NVDA screen. You'll find this option.
All the best.
Ben