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
{{ message }}
Repository navigation
WAI-ARIA 1.1: role= None and role=presentation #80
I suggest two alternatives with my preference for the first:
i. If the perception is that developers do not understand use of role=presentation, then the solution is to clarify its usage in the specs / education material. Makers of user agents / AT should not be required to make a change if they already support role=presentation.
ii. Sure role=none makes better sense than role=presentation from a wording / semantic perspective.
Instead of retaining role=presentation, consider deprecating role=presentation.
Deprecating it will give a clear signal to makers of user agents / AT and in the interim, validators can flag "warning" for role=presentation.
Defining two roles with identical functionality will make it difficult for makers of user agent / AT. Some will support it sooner or later or not at all. They may not regard supporting role=none as critical if they already support role=presentation.
Developers will need to cope with this problem by setting role=presentation and role=none to deal with user agent variations.
I suggest two alternatives with my preference for the first:
i. If the perception is that developers do not understand use of
role=presentation, then the solution is to clarify its usage in the specs /
education material. Makers of user agents / AT should not be required to
make a change if they already support role=presentation.
ii. Sure role=none makes better sense than role=presentation from a
wording / semantic perspective.
Instead of retaining role=presentation, consider deprecating
role=presentation.
Deprecating it will give a clear signal to makers of user agents / AT and
in the interim, validators can flag "warning" for role=presentation.
Defining two roles with identical functionality will make it difficult for
makers of user agent / AT. Some will support it sooner or later or not at
all. They may not regard supporting role=none as critical if they already
support role=presentation.
Developers will need to cope with this problem by setting
role=presentation and role=none to deal with user agent variations.
Thanks,
Sailesh Panchang
—
Reply to this email directly or view it on GitHub #80.
Activity
asurkov commentedon Aug 6, 2015
ARIA doesn't need two roles for same thing, role="presentation" can go away.
On Thu, Aug 6, 2015 at 11:13 AM, michael-n-cooper notifications@github.com
wrote:
ZoeBijl commentedon Sep 21, 2015
My preference goes to option number two, but I can see that this involves more work for all parties.
michael-n-cooper commentedon Oct 25, 2016
Moving to ARIA 2.0 as we don't expect to address deprecation of presentation until then.
pkra commentedon Jun 28, 2023
Related: #1863
pkra commentedon May 13, 2024
As per editors meeting, closing this as completed.
Merge pull request #80 from w3c/sideshowbarker/doc-afterword
Clarify UIA and AX mappings for audio/video and sub-dom controls