Opened 21 months ago
Last modified 2 days ago
#18650 new enhancement
Make archives and categories widgets dropdown ada compliant
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 3.6 |
| Component: | Accessibility | Version: | 3.2.1 |
| Severity: | major | Keywords: | has-patch dev-feedback |
| Cc: | webstoc |
Description
Conditionally add the <label> tag for the archives and categories widgets so they are ada compliant.
Attachments (4)
Change History (13)
jlevandowski — 21 months ago
comment:1
SergeyBiryukov — 21 months ago
I'd prefer to see the <select> element get an id attribute that had the widget ID as a suffix - that way, more than one archive dropdown widget can be used on a page with valid unique ids.
jlevandowski — 21 months ago
comment:3
jlevandowski — 21 months ago
Added patch that adds widget id so that more than one widget of the same kind can be used on a page.
comment:4
jlevandowski — 10 months ago
- Component changed from Widgets to Accessibility
- Keywords dev-feedback added
- Severity changed from normal to major
We verified that the patch fixes red flags in the WAVE toolbar. Curious what the hold up is on reviewing the patch by jlevandowski and getting it into the widgets? There are dozens (if not hundreds) of .gov sites using WordPress that need these fixes. As an "accessibility" issue, this more than of a "major" than "normal" severity.
SergeyBiryukov — 3 months ago
comment:7
follow-up:
↓ 9
SergeyBiryukov — 3 months ago
- Milestone changed from Awaiting Review to 3.6
Refreshed the patch.
Not sure if changing the existing id attribute for Categories widget is a good idea though. I guess it may lead to unexpected results in some themes.
comment:8
SergeyBiryukov — 3 months ago
#16527 was marked as a duplicate.
comment:9
in reply to:
↑ 7
DrewAPicture — 2 days ago
Replying to SergeyBiryukov:
Not sure if changing the existing id attribute for Categories widget is a good idea though. I guess it may lead to unexpected results in some themes.
I see where you're coming from on this. And I can see why the inner select id was left alone -- the main widget id is unique for each instance just as with the other core widgets. On that same token, themes shouldn't have been targeting ids since they are by nature meant to be unique anyway.
18650.patch builds off 18650.2.patch and swaps out echo esc_attr( __( 'String' ) ) for esc_attr_e( 'String' )

Related: #16527