#36627 closed defect (bug) (fixed)
Theme preview/details: change non-links to buttons and remove disabled buttons from tabindex
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 5.1 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Themes | Keywords: | has-patch semantic-buttons |
Focuses: | accessibility, javascript | Cc: |
Description
The next/prev theme navigation gets the classname .disabled
but is still available in the tabindex. Also the navigation is non-links <a href="#">
that should be <button>
.
If you previewing a installed theme, there is a non-link thats says installed. The link should not be a link.
Attachments (5)
Change History (14)
#2
@
7 years ago
- Focuses javascript added
- Keywords needs-refresh added
- Milestone changed from Awaiting Review to Future Release
This ticket was mentioned in Slack in #accessibility by afercia. View the logs.
6 years ago
#5
@
6 years ago
- Milestone changed from Future Release to 5.0
Just checked again this and seems to me a few things have changed and there's only one point to address:
in the theme installer, the buttons that look "disabled" are still focusable and it is possibel to Tab to them. They should use a disabled
attribute. See screenshot below.
#6
@
6 years ago
@afercia Updated the patch so to add disabled
attribute to the buttons when disabled.
#7
@
5 years ago
- Keywords needs-refresh removed
36627.diff avoids a focus loss when navigation is at the first or last theme, and improves the buttons accessibility text.
Thanks @walbo yes the theme browser needs some accessibility improvements and many of the points you outlined are perfectly valid. Many things have changed in the last months, see for example [38084] that added a
disabled
attribute on the next/prev navigation to take them out from the tab order when they're... disabled :)Other things need to be fixed yet, for example some buttons miss a
type="button"
attribute and the JS part could be probably simplified. Also, some links (with a few exceptions for the ones that still work when JS is off) need to be buttons.I'd suggest to keep things separated though and open a separate ticket for the theme installer. Keeping the issues related to the theme browser in this ticket and addressing the theme installer issues in a separate ticket would help to make things more clear for other contributors and reviewers.