- From: Joseph Scheuhammer <clown@alum.mit.edu>
- Date: Thu, 10 Sep 2015 09:24:11 -0400
- To: James Craig <jcraig@apple.com>, Richard Schwerdtfeger <schwer@us.ibm.com>
- Cc: PF <public-pfwg@w3.org>
There's another way to look at this that could get rid of the problem.
If there is no reason to ever expose an accessible for an element with
role="rowgroup", then the semantics of rowgroup are non-existent, for
all intents and purposes.
In that case, the rowgroup role can be deprecated and removed from the
spec. The advantages are:
- no author could ever make the error of adding @tabindex to a rowgroup
element.
- no author could ever make the error of adding click, keypress or other
events to the element.
- no webapp would be affected since there are no real world examples,
or, if there are, then we would find out pretty quickly.
- user agent mappings would be interoperable since no user agent would
expose the role.
Any objections to removing the rowgroup role?
--
;;;;joseph.
'Array(16).join("wat" - 1) + " Batman!"'
- G. Bernhardt -
Received on Thursday, 10 September 2015 13:24:43 UTC