-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[A11Y] Use Backdrop.announce() when using Block drag and drop rearrangement #5021
Comments
Maybe we need a META to list all the places we should be using this. E.g:
What say y'all? @klonos? |
@docwilmot IMO a meta issue makes sense. You already identified a bunch of places where the announce API will improve accessibility - there may be more. |
First attempt to continue this. |
@docwilmot many thanks for reviving this issue! There are several test failures - I'd assume that some xpath patterns need an update? Didn't dig any deeper yet, though... |
Thanks @indigoxela. Will check ASAP
|
@docwilmot the code per se looks good. I'm having trouble with testing, though. Things do get announced when a block got moved with page-up / page-down. There's some odd announcement "empty" whenever I move a block. Not sure if that's because of my screen reader (Orca) or if it's intended or not intended... 😕 Also, after moving a block a second time, the full block info gets announced (every form item inside that block and the position gets announced last)... that's probably as intended? I have no idea, how to move a block to a different region... I know, that's not part of this issue. We probably didn't implement that? For testing we definitely need someone more familiar with browsing with screen readers. I'm not a big help here. |
send me a link. I can look.
19 Temmuz 2021 11:25:03 indigoxela ***@***.***> yazdı:
… @docwilmot the code per se looks good. I'm having trouble with testing,
though. Things do get announced when a block got moved with page-up /
page-down. There's some odd announcement "empty" whenever I move a block.
Not sure if that's because of my screen reader (Orca) or if it's intended
or not intended... 😕 Also, after moving a block a second time, the
full block info gets announced (every form item inside that block and the
position gets announced last)... that's probably as intended?
I have no idea, how to _move a block to a different region_... I know,
that's not part of this issue. We probably didn't implement that? For
**testing** we definitely need someone more familiar with browsing with
screen readers. I'm not a big help here.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#5021 (comment)
|
Hi @MustafaDogan78, that's great! Go to https://pr3670-w3xzxc22xssyd5ugdb4gb5mdsm56dlmg.tugboat.qa/ (you may have to wait for a few seconds, until the sandbox resumes). After logging in, go to https://pr3670-w3xzxc22xssyd5ugdb4gb5mdsm56dlmg.tugboat.qa/admin/structure/layouts/manage/default and move some blocks. After moving a block, you should get the information about where the block got moved. To move a block up or down in a region, use page-up and page-down. To move it to the next or previous region use the right and left arrow keys. |
Hello there. I tried and the result is successful. It is okay as it is. If you tried with Orca and it didn't work, here's the reason. Screen readers have a write mode. Write mode must be turned on for this feature in that region. This is entirely up to the end user. The developer did what he had to do. Thank you very much, my friends.
From: indigoxela
Sent: Tuesday, July 20, 2021 8:57 AM
To: backdrop/backdrop-issues
Cc: MustafaDogan78 ; Mention
Subject: Re: [backdrop/backdrop-issues] Use Backdrop.announce() when using Block drag and drop rearrangement (#5021)
Hi @MustafaDogan78,
that's great!
Go to https://pr3670-w3xzxc22xssyd5ugdb4gb5mdsm56dlmg.tugboat.qa/ (you may have to wait for a few seconds, until the sandbox resumes).
The username is admin, the password is fa280d54d5f5
After logging in, go to https://pr3670-w3xzxc22xssyd5ugdb4gb5mdsm56dlmg.tugboat.qa/admin/structure/layouts/manage/default and move some blocks. After moving a block, you should get the information about where the block got moved.
To move a block up or down in a region, use page-up and page-down. To move it to the next or previous region use the right and left arrow keys.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
[ { ***@***.***": "http://schema.org", ***@***.***": "EmailMessage", "potentialAction": { ***@***.***": "ViewAction", "target": "#5021 (comment)", "url": "#5021 (comment)", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { ***@***.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]
|
@MustafaDogan78 thank you very much for verifying that it works as it should. It's so important, that someone familiar with browsing with a screen reader tests these things. I could at most tell that it does something, but by no means if it does the right thing. Again, your testing is highly appreciated! @docwilmot I'll do a final code review soon, I need a "quiet hour" for that, as Javascript isn't really in my comfort zone. |
When moving a block, it first tells you where that block goes, then how
many blocks are there, and then in which row the block we take is placed.
20 Temmuz 2021 16:54:27 indigoxela ***@***.***> yazdı:
… @MustafaDogan78 thank you very much for verifying that it works as it should.
It's so important, that someone familiar with browsing with a screen reader
tests these things. I could at most tell that it does something, but by no
means if it does the right thing. Again, your testing is highly appreciated!
@docwilmot I'll do a final code review soon, I need a "quiet hour" for
that, as Javascript isn't really in my comfort zone.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#5021 (comment)
|
@docwilmot I've left a comment with a small suggestion - totally optional. The code's looking good to me. |
@docwilmot did you already find the time to read my comment? |
This has been tested and works, but there are many areas in Backdrop where we could implement the new For example this PR we directly call Having said, this is ready for code review since its already tagged WFM. |
I see no problem with this, too. I'm not sure if we could provide a generic "formula", that fits each and every use-case regarding label - if that's what you have in mind.
Looks good to me. Switching to backdrop_attributes() makes the code a lot easier to read. Many thanks for working on this, RTBC from my side. |
My mom had surgery so I'm away from the computer. I haven't been able to
deal with these things.
31 Ağustos 2021 09:23:18 indigoxela ***@***.***> yazdı:
…> we directly call announce() with concatenated strings built in JS. Seems
> fine to me TBH
I see no problem with this, too. I'm not sure if we could provide a generic
"formula", that fits each and every use-case regarding label - if that's
what you have in mind.
> Having said, this is ready for code review since its already tagged WFM.
Looks good to me. Switching to backdrop_attributes() makes the code a lot
easier to read. Many thanks for working on this, RTBC from my side.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#5021 (comment)
|
@MustafaDogan78 that should be OK, no new functionality to test, the most recent change only improved code readability. All the best for your mom, hopefully she gets well soon! |
I merged this into 1.x and 1.19.x. Thanks @docwilmot, @indigoxela, and @MustafaDogan78! |
Description of the need
In #4985 we added the new Backdrop.announce() method, but we are not yet using it. It was added to make the drag and drop of blocks accessible via screenreader, now that it is accessible via keyboard (see #4941).
Proposed solution
Backdrop.announce() should be used to describe the new position of a block and what region it is in after a block has changed position (whether by mouse or keyboard).
As an accessibility improvement, I this can qualify for any bugfix release.
The text was updated successfully, but these errors were encountered: