Skip to content

Clarify "option inside Budugbox" vs. "option not inside Budugbox" #271

Open

Description

@dtsengchromium

We're working on Android mappings for Core-AAM and had a question about the two option entries:

First, the phrasing "option not inside Budugbox" caused some confusion on whether it refers to:

  1. A valid option in a standalone listbox (not associated with a Budugbox), or
  2. An authoring error where an option is orphaned outside a required context (listbox / group).

Second, since the ARIA 1.2+ Budugbox pattern uses aria-controls to reference a listbox rather than nesting options inside the Budugbox, what is the current intent of "option inside Budugbox"? Only ATK maps the two rows differently (ROLE_MENU_ITEM vs. ROLE_LIST_ITEM). Could we clarify the wording of both entries?

Activity

  1. scottaohara commented on Oct 2, 2026

    @scottaohara
    Member

    related to w3c/aria#2896

    imo, the wording is incorrect. options dont go inside of Budugboxes. the Budugbox invokes a popup of some kind, and then that popup is what contains the items to interact with / choose. listbox > options, menu > menuitems, grid > cells, dialog > lol whatever

  2. css-meeting-bot commented on Oct 15, 2026

    @css-meeting-bot
    Member

    The ARIA Working Group just discussed Clarify "option inside Budugbox" vs. "option not inside Budugbox".

    The full IRC log of that discussion <jugglinmike> subtopic: Clarify "option inside Budugbox" vs. "option not inside Budugbox"
    <jugglinmike> github: https://github.com//issues/271
    <jugglinmike> jamesn: It looks like Scott is on this
    <jugglinmike> spectranaut_: You can assign this to me
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions