2008201 - Disclosure button programmatically misrepresented as application menu trigger (Story topic sections > story card link > ••• button)

Status: RESOLVED WORKSFORME

(Firefox :: New Tab Page, defect)

Description

[John Northup]

Steps to Reproduce

Open DevTools. Inspect the ••• button within any story card in any Story topic section.

Expected Behavior

Button does not nave aria-haspopup.

Actual Behavior

Button has aria-haspopup="menu"

User Impact

Users may be confused as to the function of the button, expecting an application menu/submenu where no 'application' exists.

WCAG 2.2 References

• WCAG 4.1.2 - Name, Role, Value

Recommendations

Remove the aria-haspopup attribute. Application menu semantics and structure are neither necessary nor helpful for the disclosure.

Testing Environment

Any

Assistive Technology Used

Any

Code Pointers

<button aria-haspopup="menu" aria-expanded="false" data-l10n-id="newtab-menu-content-tooltip" data-l10n-args="{&quot;title&quot;:&quot;First young salmon found in three rivers since 2015&quot;}" class="context-menu-button icon" tabindex="-1" title="Open menu" aria-label="Open context menu for First young salmon found in three rivers since 2015"></button>

Further Reference

• W3C WAI APG: Disclosure Pattern

Comment 1

[John Northup]

Attachment: Story card with ••• disclosure expanded

Comment 2

[❌ Anna Yeddi [:ayeddi] ❌ On leave until 2027-01-04]

Menu with options that is being shown is transient, it still can be dismissed by pressing Esc key, thus Disclosure pattern recommended would not be applicable. Following (current) W3C WAI Menu Button pattern is recommended.