Gitter Channel Archive 8th of December 2016
What fresh hell is THIS now? - Patrick Lauke
<header> for the site, and a <header> for each article. Does it make sense to give each header its own aria label, like “Site header” and “Article Header”, or is that overkill?
<aside> tags the same aria-label. Specifically, if i have a news story with two pull quotes, simply labeling each one with aria-label=”pull quote”
aria-label at all
fieldset element (http://w3c.github.io/html/sec-forms.html#the-fieldset-element) and am trying to work out if I can put aria-required and aria-invalid attributes on it. I can't work out if I can or whether I have to do something hacky like give the fieldset an attribute of radiogroup first. Interestingly, JAWS announces required and invalid on fieldsets which is useful; I can't remember what NVDA does, but VoiceOver ignores it.
role=radiogroup on the fieldset as you suspect
fieldset designed to group things like radio buttons and, if so, then isn't it by default a radiogroup?
role=radiogroup on the immediate container of the elements. That said, I tend to use <ul> elements to mark up forms and add role=presentation on the <ul> so that wouldn't work either.