Re: [w3ctag/design-reviews] [HTML] Canvas place element (Issue #997)

Thanks for all the info on this interesting proposal (we're happy to see [you're using the WHATWG Stages process](https://github.com/whatwg/html/issues/10650)). You've listed several general advantages of placing elements on the canvas, but there isn't much info in the explainer (no specifics at the beginning) on the specific use cases you envisage for this. Please could you add those at the beginning of the explainer?

There are a few areas in which it would be wise to warn developers that they still need to do some additional work in order to ensure the accessibility of the controls, such as ensuring that focus indicators are visible against variable canvas 'background' content. Also, some people would find it hard to read text content that is significantly rotated, for example. Whilst cases like these are inherently covered by WCAG, it would be a good idea to remind developers that they need to check these things - something to consider for the developer docs in future.

How do you envisage that the user's varying base font size, zoom level, and/or viewport size would come into play? For example, when elements are placed at specific coordinates, there seems to be a risk that they could end up overlapping/occluding each other, or having content truncated, if the user increased the base font size, or zoomed the page.

We also encourage you to get in touch with the [Accessible Platform Architectures (APA) WG](https://www.w3.org/WAI/about/groups/apawg/), this group provides accessibility review and may have more input/suggestions (I'm one of the co-chairs). You can get in touch with APA by adding the `a11y-tracker` label to an issue in any W3C or WHATWG repo.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/997#issuecomment-2427376698
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/997/2427376698@github.com>