Skip to content

[Port dspace-7_x] support for disabled buttons for screen readers#3270

Merged
tdonohue merged 11 commits intoDSpace:dspace-7_xfrom
atmire:w2p-117544_support-for-disabled-elements-for-screen-readers-7.x
Jan 28, 2025
Merged

[Port dspace-7_x] support for disabled buttons for screen readers#3270
tdonohue merged 11 commits intoDSpace:dspace-7_xfrom
atmire:w2p-117544_support-for-disabled-elements-for-screen-readers-7.x

Conversation

@jensvannerum
Copy link
Copy Markdown
Contributor

References

This is a backport to DSpace 7 of #3268

Description

see #3268

Checklist

  • My PR is created against the main branch of code (unless it is a backport or is fixing an issue specific to an older branch).
  • My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
  • My PR passes ESLint validation using yarn lint
  • My PR doesn't introduce circular dependencies (verified via yarn check-circ-deps)
  • My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
  • My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
  • My PR aligns with Accessibility guidelines if it makes changes to the user interface.
  • My PR uses i18n (internationalization) keys instead of hardcoded English text, to allow for translations.
  • My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
  • If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
  • If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
  • If my PR fixes an issue ticket, I've linked them together.

@tdonohue tdonohue changed the title support for disabled elements for screen readers [Port dspace-7_x] support for disabled elements for screen readers Aug 27, 2024
@tdonohue tdonohue added this to the 7.6.3 milestone Aug 27, 2024
Jens Vannerum added 3 commits September 16, 2024 14:24
- added typedocs
- changed directive to only be present for buttons
- various other small fixes
@github-actions
Copy link
Copy Markdown

Hi @jensvannerum,
Conflicts have been detected against the base branch.
Please resolve these conflicts as soon as you can. Thanks!

…ort-for-disabled-elements-for-screen-readers-7.x
Copy link
Copy Markdown
Member

@tdonohue tdonohue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jensvannerum : This looks mostly good! However, I found a minor mistake in this backport.

It appears you've accidently created an empty src/app/admin/admin-reports/filtered-items/filtered-items.component.html file in this PR. That feature only exists in 8.x and above, so this file should be removed.

@jensvannerum jensvannerum force-pushed the w2p-117544_support-for-disabled-elements-for-screen-readers-7.x branch from 6e88bee to cd2f8ab Compare January 27, 2025 09:23
@tdonohue tdonohue changed the title [Port dspace-7_x] support for disabled elements for screen readers [Port dspace-7_x] support for disabled buttons for screen readers Jan 28, 2025
Copy link
Copy Markdown
Member

@tdonohue tdonohue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Thanks @jensvannerum ! I gave this a quick test on 7.x to make sure it works the same, and it does. Code looks good now too.

@tdonohue tdonohue merged commit 1cc4756 into DSpace:dspace-7_x Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Development

Successfully merging this pull request may close these issues.

2 participants