Editorial: make shape attributes table consistent

[keithamus]

This formats the wording & HTML around shape attribute such that it is consistent with the format described in #9832

---

/image-maps.html ( diff )

[annevk]

This is also not ideal as-is I think. Non-conforming is a state that for this particular attribute is relevant for https://html.spec.whatwg.org/#canonical-keyword as multiple keywords map to the same state. And non-conforming is not the same as a brief description.

We could restate the non-conforming keywords after the table, but perhaps having an additional column for them is better. Some kind of "Non-conforming" column with checkmarks. Or perhaps the inverse if folks think that's not clear enough.

[domenic]

As I mentioned in #9832 (comment), I think we should keep the notes column, in addition to adding the brief description column.

[keithamus]

Okay I've kept the Notes column, but given how State is now on the right, it felt unclear to have Notes anywhere but adjacent to the Keyword column, so it now reads Keywword, Notes, State, Brief Description, which is a little odd.

Let me know your thoughts and I'll update #9850 to do the same.

[annevk]

@domenic how about we instead move the "non-conforming" annotations into the keyword column? As

circ (non-conforming)

? (And then drop the paragraph that states they are non-conforming as it's redundant with the table.)

[domenic]

It looks pretty weird that way:

This is maybe slightly better?

Not sure what to suggest...

I agree the paragraph is redundant and can be removed.

[annevk]

From those two tables I think the first is better a11y-wise. I'd be a bit worried that if you land on one of the non-conforming cells in isolation you can't make sense of it, unless perhaps we'd also mark the keywords as headings?

(Amazing by the way how it's inconsistent with regards to whether the abbreviated keyword is conforming or not.)

[domenic]

We could always overkill it with CSS grid inside the table cell, at the cost of some extra markup and having to edit the stylesheet...

[domenic]

Separate Conforming column:

[domenic]

The CSS right-aligning ended up looking weird to my eyes, but maybe if I was better at design it would be better...

[domenic]

In Chat we have settled on the extra Conforming column. Notes:

• Add class="yesno" to the table
• Add class="no" to the "no" cells to get them centered.
• Don't do anything for the yes cells, IMO?
• No more need for the "Note the circ, polygon, and rectangle, keywords are non-conforming." sentence.
• Separately, "default" is missing a "Brief description".

[keithamus]

I've added the classes but the styles aren't applying as /styles.css seems to be the wrong URL. Is this a known issue?

Aside from that I think this is complete.

[domenic]

Yeah, PR preview doesn't seem to work that well in certain ways. One of us can do a local build and double-check before merging (probably during the workweek).