Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
On clicking the image the user should be directed to respective module page.
Steps to reproduce
Proposed resolution
Remaining tasks
- ✅ File an issue about this project
- ☐ Manual Testing
- ☐ Code Review
- ☐ Accessibility Review
- ☐ Automated tests needed/written?
Comment | File | Size | Author |
---|---|---|---|
#19 | headings.jpg | 236.62 KB | rkoller |
#18 | form_elements.jpg | 314.63 KB | rkoller |
#18 | links.jpg | 303.47 KB | rkoller |
#18 | safari.jpg | 47.86 KB | rkoller |
#17 | Screenshot 2022-11-11 at 11.50.47 AM.png | 80.65 KB | srishtiiee |
Issue fork project_browser-3311992
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
Utkarsh_33 CreditAttribution: Utkarsh_33 commentedComment #4
narendraRComment #5
narendraRAdded some suggestions
Comment #6
Utkarsh_33 CreditAttribution: Utkarsh_33 commentedComment #7
narendraRChanges looks good to me.
Comment #8
bnjmnmScreenreaders/rotors/other assistive tech will interpret these as a bunch of empty links. The logo images are marked as decorative (no alt text) because they're pulled from an external source where alt data is not reliable. Adding links where the only content is a decorative image is a problem as there's no non-sighted way to identify that link.
Comment #9
Utkarsh_33 CreditAttribution: Utkarsh_33 commentedComment #10
Utkarsh_33 CreditAttribution: Utkarsh_33 commentedComment #11
srishtiiee CreditAttribution: srishtiiee at Acquia commentedReferring to the earlier discussions on making the project tile more accessible we should make the complete region having the logo and the title clickable.
Left a comment for the same in the MR.
Comment #12
Utkarsh_33 CreditAttribution: Utkarsh_33 commentedComment #13
srishtiiee CreditAttribution: srishtiiee at Acquia commentedComment #14
Utkarsh_33 CreditAttribution: Utkarsh_33 commentedComment #16
Utkarsh_33 CreditAttribution: Utkarsh_33 commentedComment #17
srishtiiee CreditAttribution: srishtiiee at Acquia commentedThe new MR looks good! Just the focus on the bottom needs to be fixed. It is currently overlapped by another element:
Comment #18
rkolleri've applied the latest state of the merge request. at least in my environment i was unable to reproduce the outline issue described in #17. i've tested on macos 12.6.1 in the latest versions of safari, firefox and edge. for me all browsers looked like in the screenshot here in safari:
in regards rotor as mentioned in #8 i've quickly tested in macos voiceover:
currently in both sections (links and form elements) it is impossible to distinguish between the listed elements for a screenreader users. you either have
modules
orinstalled button
repeated in a redundant way. each of the entries is missing a context.additionally in the rotors headings section there is no heading for any of the card components listed. the only way that one heading is listed is if you get one card heading into focus by tabbing into it, then start voiceover, and open the rotor. then you are able to see the card heading in focus in the rotors heading section as well. the rest of the modules is still not available in the rotors headings section.
and one detail i've notice i am not sure if it is related with the current issue. but if you tab through one card the first tab you get headline and logo into focus, on the next tab the focus disappears and on the last tab inside the card the button in the bottom right corner gets into focus.
Comment #19
rkolleruploaded the image that i've added to the previous comment in my edit.
Comment #20
Utkarsh_33 CreditAttribution: Utkarsh_33 commentedNeeds some changes.
Comment #21
Utkarsh_33 CreditAttribution: Utkarsh_33 commentedComment #22
Utkarsh_33 CreditAttribution: Utkarsh_33 commentedComment #23
tim.plunkettComment #24
kevinting CreditAttribution: kevinting commentedI am working on this issue as part of DrupalCon Pittsburgh
Comment #25
kevinting CreditAttribution: kevinting commentedComment #27
kevinting CreditAttribution: kevinting commentedAdded Merge Request. Solution is to just wrap the Image element with anchor tag linking to project page.
@earthday47 is willing to add tests as needed.
Changes committed to branch 3311992-make-image-clickable-pittsburgh2023
Comment #29
kevinting CreditAttribution: kevinting commentedThanks @fjgarlin for re-pushing commits and running tests.
Comment #31
earthday47Hi all! Catching up on this issue's history, I do see that we wanted to have the top region clickable for accessibility reasons. I didn't want our work from yesterday to invalidate all of this useful work, so I rebased the 2nd-to-last MR/branch.
So we have a couple options... the a wrapping the Image element, which would create two anchors to tab through, or the original approach creating a click event/action on the wrapping div.
Comment #32
chrisfromredfinI definitely prefer "the original approach creating a click event/action on the wrapping div." 2 click targets makes less sense especially for a non-sighted user.
Comment #33
fjgarlin CreditAttribution: fjgarlin as a volunteer and at Drupal Association commentedIt'd also be great to close the MRs that are no longer used.
Comment #36
chrisfromredfinComment #38
RajeshreeputraRebased
Comment #39
fjgarlin CreditAttribution: fjgarlin as a volunteer and at Drupal Association commentedTests are not passing. Back to NW.
Comment #40
chrisfromredfin