Skip to content

WAI-ARIA 1.1: role= None and role=presentation #80

Closed

Description

@michael-n-cooper

Filed at https://lists.w3.org/Archives/Public/public-pfwg-comments/2015JulSep/0004.html by Sailesh Panchang spanchang02@yahoo.com

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

Activity

  1. asurkov commented on Aug 6, 2015

    @asurkov
    Contributor

    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:

    Filed at
    https://lists.w3.org/Archives/Public/public-pfwg-comments/2015JulSep/0004.html
    by Sailesh Panchang spanchang02@yahoo.com

    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.

  2. ZoeBijl commented on Sep 21, 2015

    @ZoeBijl
    Contributor

    My preference goes to option number two, but I can see that this involves more work for all parties.

  3. michael-n-cooper commented on Oct 25, 2016

    @michael-n-cooper
    MemberAuthor

    Moving to ARIA 2.0 as we don't expect to address deprecation of presentation until then.

  4. modified the milestone: on Nov 3, 2016
  5. pkra commented on Jun 28, 2023

    @pkra
    Member

    Related: #1863

  6. modified the milestones: ARIA 2.0, ARIA 1.3 on Jun 28, 2023
  7. pkra commented on May 13, 2024

    @pkra
    Member

    As per editors meeting, closing this as completed.

  8. added 2 commits that reference this issue on May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions