You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After another reading of the ARIA spinbutton specification, I am wondering how we should structure the spinbutton and whether or not we need multiple examples, each with a different structure. The spec says:
Authors MAY create a spinbutton with children or owned elements, but MUST limit those elements to a textbox and/or two buttons.
It also says:
When a spinbutton receives focus, authors SHOULD ensure focus is placed on the textbox element if one is present, and on the spinbutton itself otherwise. Authors SHOULD NOT include contained button elements in the primary navigation ring, e.g., the Tab ring in HTML, because they are superfluous for people using keyboard devices.
The above text is describing a composite structure like:
After another reading of the ARIA spinbutton specification, I am wondering how we should structure the spinbutton and whether or not we need multiple examples, each with a different structure. The spec says:
It also says:
The above text is describing a composite structure like:
Another structure supported by this spec language is:
However, I've normally seen a flat structure like:
Now, I'm wondering if this latter structure is actually allowed? The spec does not appear to support it. Should it?
Related to issue #125.
The text was updated successfully, but these errors were encountered: