matatk left a comment (w3ctag/design-reviews#1120) Thanks @schenney-chromium and @bramus for your input. This message is just from me personally... Restoring the discussions you mentioned @schenney-chromium, sounds to me like a good approach. We'll look forward to reading the Explainer updates (please could you also include the possible abuse case we mentioned, and any others that occur to you?) @bramus: You're right, of course, that there are far more impactful CSS features that could be misused or abused. You picked some particularly good examples. WCAG aims to protect against misuse, whilst still giving designers freedom. For active abuse, there are other measures, both technical and non-technical that could be used, but all of the features you mention involve some risk. Documenting abuse cases is intended to help with the design and review process, and future reference. Ideas for mitigations often come out of discussion of the abuse cases. Of course, when weighing up the benefits and risks of this proposal, all the factors you mentioned should be borne in mind. I hope that clarifies the reason for the ask. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/1120#issuecomment-3265774308 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/1120/3265774308@github.com>
Received on Monday, 8 September 2025 11:04:16 UTC