SC1.3.2 Name 'Order of element in code' wrongly suggests that it's not the remit of designers to avoid that issue

[jfhector]

What's the issue

On top of my head, I believe that unaware designers can easily cause failures to SC1.3.2.

E.g. when they create designs where elements are not in the same left-to-right reading order when viewed on different screen sizes.

Educating designers about this potential barrier is important. But the current wording of this summary suggests that it's purely an engineering issue.

Next steps

• Look at the official wording of the success criterion
  • Can designers cause this issue?
  • What's the official short name of this success criterion in the WCAG?
• Propose new phrasing for the name of this success criterion
• Add 'Design' to the 'Responsibility' column of the table, if appropriate