Related spec PR: whatwg/html#12424
Spec issue: whatwg/html#10293
The HTML spec is gaining a readonly content attribute on <fieldset>,
mirroring disabled. This raises a few ARIA-in-HTML questions:
- Should
aria-readonly on <fieldset> be permitted, prohibited, or
considered redundant when the content attribute is present?
- Should
aria-readonly on a descendant <input>/<textarea> whose
readonly state is inherited from a <fieldset readonly> ancestor
be considered redundant? (Same question as for aria-disabled
inside <fieldset disabled> today.)
- Any role restrictions to call out?
Companion HTML AAM issue: w3c/html-aam#606
Related spec PR: whatwg/html#12424
Spec issue: whatwg/html#10293
The HTML spec is gaining a
readonlycontent attribute on<fieldset>,mirroring
disabled. This raises a few ARIA-in-HTML questions:aria-readonlyon<fieldset>be permitted, prohibited, orconsidered redundant when the content attribute is present?
aria-readonlyon a descendant<input>/<textarea>whosereadonly state is inherited from a
<fieldset readonly>ancestorbe considered redundant? (Same question as for
aria-disabledinside
<fieldset disabled>today.)Companion HTML AAM issue: w3c/html-aam#606