Read-only buttons: Because two or more "main" elements on a page just wasn't enough.
Adrian Roselli (toot.cafe)Adrian Roselli (toot.cafe)Adrian Roselli (toot.cafe)Adrian Roselli (toot.cafe)Adrian Roselli (toot.cafe)Read-only buttons: Because two or more "main" elements on a page just wasn't enough.
@acarson @aardrian yeah that. Been thinking of how to vocalize my thoughts on this since I saw it, but in all cases it’s a hard no. We don’t need another confusing role to add to elements, developers already do a great job at doing that when they combine something as a “button link” or use multiple roles not realizing only one will be applied, the rest are more of a fallback. Putting a disabled button into tab order optionally with aria-describedby works well enough, too.
@acarson Be careful — it took years and 120+ comments for WHATWG to finally relent on that one.
@aardrian I know I read that whole comments section and just kept getting progressively angrier.
@acarson @aardrian I do think they have valid concerns with disabled button instructions that only show on hover, but again, you can work with that by making sure developers know to show it when it receives keyboard focus, or do the text thing next to it which is cognitively worse, could be argued. Either way we’re not out of options for solving it and making a new role will just complicate and muddle things up even more for sure.