> Sorry I don't think you can do it like this for localization. It's going to be wrong in many languages where words have to be formed differently when put after one another. I had the same feeling and I suspected this wasn't a good solution. > I think you can just let the aria-label reference the relevant <th> (give it an id). The problem with this approach, is that it will be impossible to distinguish between incoming and outgoing fields. Using the "Server" row for example, we have two manulist which represent the "Incoming" and "Outgoing". If I use "Server", we're gonna have 2 menulists with the "Server" aria-label but no distinction between incoming and outgoing. If I use the "Incoming" and "Outgoing" labels from the column header, the screen reader will not know that those lists are related to the "Server" settings, returning only "Incoming" or "Outgoing".
Bug 1620718 Comment 9 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> Sorry I don't think you can do it like this for localization. It's going to be wrong in many languages where words have to be formed differently when put after one another. I had the same feeling and I suspected this wasn't a good solution. > I think you can just let the aria-label reference the relevant <th> (give it an id). The problem with this approach, is that it will be impossible to distinguish between incoming and outgoing fields. Using the "Server" row for example, we have two menulists which represent the "Incoming" and "Outgoing". If I use "Server", we're gonna have 2 menulists with the "Server" aria-label but no distinction between incoming and outgoing. If I use the "Incoming" and "Outgoing" labels from the column header, the screen reader will not know that those lists are related to the "Server" settings, returning only "Incoming" or "Outgoing".