Re: Subgroups proposal for support personalization and important request from coga

What we are proposes really appears to be cases of 1.3.1 that were not
covered in previous iterations of the techniques. Could we achieve this be
adding to sufficient conditions to be sufficient for meeting 1.3.1.

Consider the sufficient condition
Situation A: The technology provides semantic structure to make information
and relationships conveyed through presentation programmatically
determinable:
By adding a point 11: Personalization Support we could introduce the
concept in a formal setting. People could still use the sufficient
technique, but to be sufficient for satisfying 1.3.1 they  would have to
check off more items.

This would be consistent with the charter of 2.1 which states that existing
Criteria can be strengthened but now weakened.

While there might be objection at first, we could simply remind people that
while technology of development has moved forward very rapidly since 2008,
the techniques not have been able to keep pace. For example, the <div> has
taken on many semantic uses that cannot be determined programmatically at
this time.

In LVTF we detected a misuse of the <i> element to identify font icons and
the back-ground color to warehouse sprites. The latter actually emboldened
Chrome to declare that they will no longer support high contrast.

I suggest at the minimum a point 11 that states that semantically ambiguous
elements that serve a traditional role (like a Table, List item etc.) me
marked up to identify their use so that a program can recognize it.

Wayne