Make WordPress Core

Opened 10 years ago

Closed 7 years ago

#27592 closed defect (bug) (fixed)

Screen Reader Users Do Not Know Widgets are Expandable

Reported by: davidakennedy's profile davidakennedy Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.9
Component: Widgets Keywords:
Focuses: accessibility, administration Cc:

Description (last modified by SergeyBiryukov)

The issue: When testing the new Widget customizer with a screen reader (in this case Mac OS 10.2 with Voiceover and Chrome), the arrow links for #available-widgets (within Widgets) do announce to screen readers, but only as "Link". Essentially, these are empty links and have little semantic meaning.

What I expected: Some way to know via announcement with the screen reader that the heading elements are expandable.

Related ticket: #27591

Recommendation: (Good) Put meaniful link text inside the a href to give it meaning. I'd also consider rearranging the source order since it goes to the links first, and you don't get the context of the heading. (Better and similar to above) Use a similar markup pattern to this accessible accordion that relies heavily on WAI-ARIA:

Change History (8)

#1 @SergeyBiryukov
10 years ago

  • Component changed from Widgets to Appearance
  • Description modified (diff)

#2 @ocean90
10 years ago

  • Component changed from Appearance to Widgets
  • Summary changed from Screen Reader Users Do Not Know Widgets in Theme Customizer are Expandable to Screen Reader Users Do Not Know Widgets are Expandable

Same for Widgets screen.

Let's use this ticket for widgets and #27591 for customizer.

#3 @ocean90
10 years ago

  • Keywords needs-patch added
  • Milestone changed from Awaiting Review to Future Release

#4 @chriscct7
9 years ago

  • Focuses administration added

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.

8 years ago

#6 @afercia
8 years ago

Related: #28888

#7 @afercia
8 years ago

Screenshot to illustrate the current situation (Safari + VoiceOver):

#8 @afercia
7 years ago

  • Keywords needs-patch removed
  • Milestone Future Release deleted
  • Resolution set to fixed
  • Status changed from new to closed

This has been fixed in [40480].

Note: See TracTickets for help on using tickets.