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?
Command icon 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:

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Utkarsh_33 created an issue. See original summary.

Utkarsh_33’s picture

Assigned: Utkarsh_33 » Unassigned
Status: Active » Needs review
narendraR’s picture

Issue tags: +Needs tests
narendraR’s picture

Status: Needs review » Needs work
Issue tags: -Needs tests

Added some suggestions

Utkarsh_33’s picture

Status: Needs work » Needs review
narendraR’s picture

Status: Needs review » Reviewed & tested by the community

Changes looks good to me.

bnjmnm’s picture

Status: Reviewed & tested by the community » Needs work

Screenreaders/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.

Utkarsh_33’s picture

Assigned: Unassigned » Utkarsh_33
Utkarsh_33’s picture

Assigned: Utkarsh_33 » Unassigned
Status: Needs work » Needs review
srishtiiee’s picture

Status: Needs review » Needs work
FileSize
120.35 KB

Referring 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.

Utkarsh_33’s picture

Status: Needs work » Needs review
srishtiiee’s picture

Status: Needs review » Needs work
Utkarsh_33’s picture

Assigned: Unassigned » Utkarsh_33

Utkarsh_33’s picture

Assigned: Utkarsh_33 » Unassigned
Status: Needs work » Needs review
srishtiiee’s picture

Status: Needs review » Needs work
FileSize
80.65 KB

The new MR looks good! Just the focus on the bottom needs to be fixed. It is currently overlapped by another element:

rkoller’s picture

FileSize
47.86 KB
303.47 KB
314.63 KB

i'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:

focus outline around image and module title in a project browser module card
in regards rotor as mentioned in #8 i've quickly tested in macos voiceover:

voiceover rotor list of link elements with redundant module listings
voiceover list of form elements with redundant installed button listings

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 or installed 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.

voiceover list of headings only showing the heading of the card in focus the rest is not shown

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.

rkoller’s picture

FileSize
236.62 KB

uploaded the image that i've added to the previous comment in my edit.

Utkarsh_33’s picture

Status: Needs work » Needs review

Needs some changes.

Utkarsh_33’s picture

Assigned: Unassigned » Utkarsh_33
Status: Needs review » Needs work
Utkarsh_33’s picture

Assigned: Utkarsh_33 » Unassigned
tim.plunkett’s picture

Issue tags: +core-post-mvp
kevinting’s picture

I am working on this issue as part of DrupalCon Pittsburgh

kevinting’s picture

Assigned: Unassigned » kevinting

kevinting’s picture

Status: Needs work » Needs review

Added 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

fjgarlin made their first commit to this issue’s fork.

kevinting’s picture

Thanks @fjgarlin for re-pushing commits and running tests.

earthday47 made their first commit to this issue’s fork.

earthday47’s picture

Hi 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.

chrisfromredfin’s picture

I 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.

fjgarlin’s picture

It'd also be great to close the MRs that are no longer used.

chrisfromredfin’s picture

Issue tags: +Needs reroll

Rajeshreeputra made their first commit to this issue’s fork.

Rajeshreeputra’s picture

Rebased

fjgarlin’s picture

Status: Needs review » Needs work

Tests are not passing. Back to NW.

chrisfromredfin’s picture