[Webkit-unassigned] [Bug 163647] AX: don't expose empty roledescription
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed May 3 17:19:09 PDT 2017
https://bugs.webkit.org/show_bug.cgi?id=163647
Joanmarie Diggs (irc: joanie) <jdiggs at igalia.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jdiggs at igalia.com
--- Comment #2 from Joanmarie Diggs (irc: joanie) <jdiggs at igalia.com> ---
(In reply to James Craig from comment #0)
> Also note the following restriction in the same section:
> > User agents must not expose the aria-roledescription property if … The element to which aria-roledescription is applied does not have a valid WAI-ARIA role or does not have an implicit WAI-ARIA role semantic.
>
> Which seems overly restrictive and I asked for it to be removed. FWIW, I
> doubt we'd want to implement this restriction even if the WG declines the
> spec change.
James: Do you still think it's acceptable to do what you stated in the related github issue [1], namely:
<quote>
What if you only included this stipulation on generic elements like <div> and <span>? I'd be okay with that restriction. The goal seems to be to avoid problem cases like <div aria-roledescription="button"> and restricting usage on generics would be one way to do that, without penalizing appropriate use on another type of element.
</quote>
If so, are you ok with my proceeding with that in Safari and WebKitGtk, independent of when the WG adopts the change?
[1] https://github.com/w3c/aria/issues/500#issuecomment-266968158
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170504/e63bf125/attachment.html>
More information about the webkit-unassigned
mailing list