- From: Michael[tm] Smith <notifications@github.com>
- Date: Mon, 31 May 2021 01:50:42 -0700
- To: whatwg/encoding <encoding@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/encoding/pull/260/c851331386@github.com>
> @sideshowbarker Changing the `aria-label` attributes to `title` would make the checker work, but I'm not sure whether that'd be fine accessibility-wise. Per a strict reading of the current wording of the implementation requirements at https://w3c.github.io/html-aam/#other-tabular-data-elements, I believe it would not be wrong accessibility-wise to change the `aria-label` attributes to `title`. However, it seems like that current wording in the AAM spec may not actually makes much sense and may instead be a spec bug. I mean, why would it make sense to make use of any `title` attribute on the `td`/`th`/`tr`, but not make use of any `aria-lable` attribute? So I raised https://github.com/w3c/html-aam/issues/335 to get clarification. If a change does end up getting made to the AAM spec, then I guess it would be appropriate for me to change the checker back to allowing `aria-label` on `td`/`th`/`tr` without warning. I say *“I guess”* because https://html5accessibility.com/stuff/2020/11/07/not-so-short-note-on-aria-label-usage-big-table-edition/ says that `td`/`th`/`tr` for “aria-label use not well supported” in UAs/AT. So I take that to mean those `aria-label` attributes would in practice not actually get exposed as accessible names in practice in current UAs/AT. And I suspect that `title` wouldn’t either. So I really don’t know what’s best to do here… -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/encoding/pull/260#issuecomment-851331386
Received on Monday, 31 May 2021 08:51:01 UTC