Revising what ARIA attributes should be considered global #999

scottaohara · 2019-06-20T18:32:58Z

Per mention in the WG call today, and spurred by the discussions started with #990, I've created the following break down for review of the attributes I believe should remain global, and those that should become either prohibited on roles where they don't make sense, or should be removed from being global attributes all together.

The following has been worded under the assumption the attributes would be removed from being global:

Attributes to remain global

aria-atomic
aria-busy (state)
aria-current (state)
aria-dropeffect - "deprecated"
aria-flowto
aria-grabbed (state) - "deprecated"
aria-hidden (state)
aria-live
aria-owns
aria-relevant
aria-roledescription

Attributes to remain global, but prohibited

Per other work already happening for role=generic and accName, aria-label and aria-labelledby have consensus of staying global, but should be noted as prohibited due to wanting to advice against naming certain roles.

aria-label
aria-labelledby

I'd also submit that if a role shouldn't be named, it also likely shouldn't have a description associated with it...

aria-describedby
aria-details

Undecided

aria-keyshortcuts
I'm not exactly sure what to do with this one. Is there actual value in allowing keyboard shortcuts for non-interactive elements? I can't think of a reason, but maybe someone else?

Attributes to reallocate to specific roles

Pending further discussion, especially regarding the roles that are listed with a "(?)", the following attributes should not be global, or should be noted as prohibited on all applicable roles where they would not be expected.

`aria-disabled` should be allowed on:

Widget Container Roles
Widget roles excluding:
- link
- meter
- progressbar
- ~~scrollbar~~
- ~~separator~~
- tabpanel

Discussion point

aria-disabled could be allowed on the following Document Structure roles as well:

application
group
toolbar

Doing so would allow for parity with HTML's allowance of <fieldset disabled>. Though allowing on these could also be more trouble than its worth. Really interested to hear what others think.

`aria-errormessage` and `aria-invalid` should be allowed on:

checkbox
combobox
listbox
tree
gridcell
radiogroup
searchbox
slider
switch
textbox

`aria-controls` should be allowed on:

button
checkbox
link
menuitem (?)
menuitemcheckbox (?)
menuitemradio (?)
option (?)
radio
scrollbar
searchbox
slider
spinbutton
switch
tab
textbox (?)
treeitem (?)

Note, #995 may mean aria-controls should remain global until a larger discussion on if any redefinition of the attribute should take place so that AT will be more inclined implement it / not ignore it.

`aria-haspopup` should be allowed on:

button
combobox
gridcell (?)
menuitem
searchbox
slider (?) - datalist is allowed on HTML's input but treated differently
textbox
treeitem (?)

(edit) Final note:

Whatever is decided here, I'd imagine a good path forward would be to not necessarily act on this as a single issue, but to create sub-issues for any reallocation. Then make PRs on those sub-tasks individually, instead of tackling this all at once.

The text was updated successfully, but these errors were encountered:

jnurthen · 2019-06-20T18:41:54Z

I think aria-invalid & aria-errormessage are missing some.
I would add

tree
gridcell
radiogroup (remove radio as this makes no sense)

scottaohara · 2019-06-20T23:34:23Z

updated the list to add those in. from here on out i won't edit the original list, just figured it made sense since discussion hadn't picked up yet.

scottaohara · 2019-06-21T02:14:25Z

Also for consideration per today's call, aria-roledescription should likely remain global, but prohibited from role=generic

carmacleod · 2019-08-01T17:25:41Z

Possibly related discussion regarding aria-controls in APG: w3c/aria-practices#805

scottaohara · 2019-08-01T17:42:05Z

note: pending further discussion on aria-haspopup, tab should have been in the listing of role allowances.

I am curious as to the mechanism that would invoke the popup on a tab, outside of potentially having to note to press a particular key to reveal the popup widget. Not sure how that would translate to touch devices right now.

carmacleod · 2019-10-09T16:49:53Z

Probably need to allow AllTheThings on role="application"? In case someone uses it to create a non-standard widget?

scottaohara · 2019-10-09T18:50:09Z

i'd submit they're not necessary on the application itself, but may be on the focusable elements that the application contains.

jnurthen · 2019-10-09T19:07:56Z

@scottaohara application is pretty much any unknown widget. I don't see why it may not have any of these attributes.

scottaohara · 2019-10-09T19:41:40Z

fair point i suppose. i just typically think of it as a wrapper to the focusable elements within being it's a subclass of a structure role

A structure containing one or more focusable elements requiring user input, such as keyboard or gesture events, that do not follow a standard interaction pattern supported by a widget role.

that said, with aria-roledescription i guess why not allow the application to be the focusable element itself and let it / its child content be affected by the user input/gestures/what-have-you

Removes the following 4 attributes from global attributes: * aria-disabled * aria-errormessage * aria-haspopup * aria-invalid Adds the above attributes back as supported attributes on certain roles (and their subclasses), as follows: aria-disabled application button composite gridcell group input link menuitem scrollbar separator tab aria-errormessage application checkbox combobox gridcell listbox radiogroup slider spinbutton textbox tree aria-haspopup application button combobox gridcell menuitem slider tab textbox treeitem aria-invalid application checkbox combobox gridcell listbox radiogroup slider spinbutton textbox tree

Add Editors Note stating that implementations for this feature are still pending. Removes the following 4 attributes from global attributes: * aria-disabled * aria-errormessage * aria-haspopup * aria-invalid Adds the above attributes back as supported attributes on certain roles (and their subclasses), as follows: aria-disabled application button composite gridcell group input link menuitem scrollbar separator tab aria-errormessage application checkbox combobox gridcell listbox radiogroup slider spinbutton textbox tree aria-haspopup application button combobox gridcell menuitem slider tab textbox treeitem aria-invalid application checkbox combobox gridcell listbox radiogroup slider spinbutton textbox tree

Removes the following 4 attributes from global attributes: * aria-disabled * aria-errormessage * aria-haspopup * aria-invalid Adds the above attributes back as supported attributes on certain roles (and their subclasses), as follows: aria-disabled application button composite gridcell group input link menuitem scrollbar separator tab aria-errormessage application checkbox combobox gridcell listbox radiogroup slider spinbutton textbox tree aria-haspopup application button combobox gridcell menuitem slider tab textbox treeitem aria-invalid application checkbox combobox gridcell listbox radiogroup slider spinbutton textbox tree

jnurthen added the Agenda label Jun 25, 2019

jnurthen mentioned this issue Jun 25, 2019

Suggest disallowing aria-disabled on role="link" #990

Closed

carmacleod mentioned this issue Jun 27, 2019

initial draft for role="generic" issue #699 #805

Merged

jnurthen added this to the ARIA 1.2 milestone Jun 27, 2019

jnurthen added a commit that referenced this issue Jul 31, 2019

Initial version for #999

758d784

jnurthen mentioned this issue Jul 31, 2019

remove 4 Global States and properties (#999) #1023

Merged

scottaohara mentioned this issue Aug 1, 2019

Clarify usage of aria-haspopup #1024

Closed

smhigley mentioned this issue Aug 7, 2019

Revisit allowed roles for aria-expanded #1026

Open

jnurthen added the has PR PR exists that will close this issue label Oct 2, 2019

scottaohara mentioned this issue Oct 9, 2019

Further global attribute considerations #1089

Closed

jnurthen closed this as completed in #1023 Oct 22, 2019

scottaohara mentioned this issue Dec 21, 2019

aria-roledescription should not be allowed on role generic #1140

Closed

majornista mentioned this issue Jun 17, 2020

aria-haspopup should still be supported on link #1289

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Revising what ARIA attributes should be considered global #999

Revising what ARIA attributes should be considered global #999

scottaohara commented Jun 20, 2019 •

edited

jnurthen commented Jun 20, 2019

scottaohara commented Jun 20, 2019

scottaohara commented Jun 21, 2019

carmacleod commented Aug 1, 2019

scottaohara commented Aug 1, 2019 •

edited

carmacleod commented Oct 9, 2019

scottaohara commented Oct 9, 2019

jnurthen commented Oct 9, 2019

scottaohara commented Oct 9, 2019

Revising what ARIA attributes should be considered global #999

Revising what ARIA attributes should be considered global #999

Comments

scottaohara commented Jun 20, 2019 • edited

Attributes to remain global

Attributes to remain global, but prohibited

Undecided

Attributes to reallocate to specific roles

aria-disabled should be allowed on:

Discussion point

aria-errormessage and aria-invalid should be allowed on:

aria-controls should be allowed on:

aria-haspopup should be allowed on:

(edit) Final note:

jnurthen commented Jun 20, 2019

scottaohara commented Jun 20, 2019

scottaohara commented Jun 21, 2019

carmacleod commented Aug 1, 2019

scottaohara commented Aug 1, 2019 • edited

carmacleod commented Oct 9, 2019

scottaohara commented Oct 9, 2019

jnurthen commented Oct 9, 2019

scottaohara commented Oct 9, 2019

scottaohara commented Jun 20, 2019 •

edited

`aria-disabled` should be allowed on:

`aria-errormessage` and `aria-invalid` should be allowed on:

`aria-controls` should be allowed on:

`aria-haspopup` should be allowed on:

scottaohara commented Aug 1, 2019 •

edited