Re: [Timely] Accessibility vs validation on WCAG 3

Michael:

I think I owe you an eval on the efficacy of role on Details, certainly
prior to any issue on HTML.

Is there a specific id href I should look at that you have handy? To
spare me grepping through the source?

Thanks.

Janina

Michael Cooper writes:
> I have to remind everyone that our previous publication of WCAG 3 had HTML
> validation errors for which we were granted a one-time exception to be
> allowed to publish. We set role="region" on the <details> element to get it
> identified as separate content, but HTML doesn't allow that (there may be an
> issue to file on HTML). I also have the script putting in a "end of
> <whatever>" at the bottom of each <details>, so it may meet the need. We
> also used @summary on <table> to provide a more contextualized title for it
> for text users, but HTML no longer allows that.
> 
> I am open to statements of "this feature is essential notwithstanding being
> non-valid HTML, because no other feature accomplishes the goal", or
> alternate proposals for how to meet the needs in valid HTML. If I don't get
> a clear answer before publication, my edits will be to:
> 
>  * Remove @role on <details>
>  * Convert @summary to <caption> and use CSS to hide from visible screen
> 
> Michael
> 

-- 

Janina Sajka
https://linkedin.com/in/jsajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa

Received on Friday, 4 June 2021 13:55:29 UTC