What fresh hell is THIS now? - Patrick Lauke
<dialog>
vs role=dialog
<dialog>
allows focus to escape into the browser chrome; the design pattern advice for role=dialog
suggests wrapping focus immediately back to the top of the dialog
inert
in in time to help?
Hi slackers. A quick question. Imagine from an article you generate several lists of labeled things (basically: lists of types of article fragments such quotations etc). From my initial research it seems to me that definition lists fit -- does it?
(IIUC, AT support for DLs is not ideal and perhaps li+section is better here anyway. Any other thoughts would be very helpful.)
display:none
. I was wondering if you guys would be willing to consider a feature request to not do that - or to add some indication that the content is hidden?
: - )
into :grinning:
[karlgroves] I always like using the example of a field label with a description:
“Must be xx/xx/xxxx format” - always a good time with VoiceOver
[alexlande] > aria-label is only allowed on something with an explicit role
Whoa, really? I think I’ve probably been using it incorrectly, in that case :( The spec says “Used in Roles: All elements of the base markup”, which I interpreted as “any element, regardless of role”. Does it actually mean “any explicitly defined role”?
<span aria-label=“foo”></span>
won’t work but <span aria-label=“foo” role=“checkbox"></span>
would
<a href=“#”
links that were being hijacked by JS to do some sort of fancy slide-in of content, so no actual navigation, and in auditing things, we decided that a button
is clearly a better choice
href=“#”
that got taken over, and we made it a button
too, since in both of these cases, it was executing some JS to change up page content
#
for everything (though in this one rare case, #
is arguably the correct “Back to Careers” type link).
href=“#”
that was very much links-as-buttons in a terrible way, and things are a lot better in general now, but this one area is still rough because it wasn’t the focus of the recent redesign work
abbr
and VoiceOver that came up earlier... it looks like that was fixed in Webkit today: https://bugs.webkit.org/show_bug.cgi?id=160907
role=tab
debate