Ayfri
07/07/2022, 4:37 PMDavid Herman
07/07/2022, 4:43 PMCedrick Cooke
07/07/2022, 4:43 PMDavid Herman
07/07/2022, 4:43 PMexpect
/ actual
, but it probably won't be trivial.Casey Brooks
07/07/2022, 4:44 PMDavid Herman
07/07/2022, 4:45 PMAyfri
07/07/2022, 4:50 PMCedrick Cooke
07/07/2022, 4:51 PMDavid Herman
07/07/2022, 4:52 PMCasey Brooks
07/07/2022, 4:52 PMAyfri
07/07/2022, 4:55 PMDavid Herman
07/07/2022, 4:57 PMAyfri
07/07/2022, 4:59 PMDavid Herman
07/07/2022, 5:00 PMAyfri
07/07/2022, 5:02 PMCasey Brooks
07/07/2022, 5:02 PMDavid Herman
07/07/2022, 5:02 PMLucas
07/07/2022, 5:13 PMandroidx.compose.material.*
instead of
org.jetbrains.compose.web.dom.*
DOM based components will never work on android/desktop/ios, its the other way around.
Dom components only work when inside renderComposable
and canvas components only work inside onWasmReady
.
You can check https://github.com/JetBrains/compose-jb/tree/master/experimental/examples
(specially the chat-mpp, which targets most plaftorms) to have a better understanding. CfW canvas is still in early stages but it already worksMrPowerGamerBR
07/07/2022, 5:22 PMcorneil
07/07/2022, 5:59 PMcompose-canvas
and compose-web-dom
or just keep compose-web
CLOVIS
07/11/2022, 4:41 PMcorneil
07/11/2022, 4:50 PMCLOVIS
07/11/2022, 5:03 PMDavid Herman
07/11/2022, 5:03 PMCLOVIS
07/11/2022, 5:04 PMDavid Herman
07/11/2022, 5:06 PMCLOVIS
07/11/2022, 5:07 PMDavid Herman
07/11/2022, 5:07 PMCLOVIS
07/11/2022, 5:07 PMcorneil
07/11/2022, 5:09 PMCLOVIS
07/11/2022, 5:10 PMDavid Herman
07/11/2022, 5:11 PMCLOVIS
07/11/2022, 5:12 PMDavid Herman
07/11/2022, 5:12 PMcorneil
07/11/2022, 5:13 PMCLOVIS
07/11/2022, 5:13 PMCasey Brooks
07/11/2022, 5:17 PMDavid Herman
07/11/2022, 5:19 PMCanvas content is not exposed to accessibility tools as semantic HTML is. In general, you should avoid using canvas in an accessible website or app.Yikes 😬
CLOVIS
07/11/2022, 5:20 PMDavid Herman
07/11/2022, 5:20 PMCLOVIS
07/11/2022, 5:20 PMCasey Brooks
07/11/2022, 5:20 PMDavid Herman
07/11/2022, 5:22 PMAyfri
07/11/2022, 5:23 PMdisplay: none
so it's completely hidden, then the canvas would be there normally, and screen reader could see a DOM exactly like the canvas isDavid Herman
07/11/2022, 5:23 PMCasey Brooks
07/11/2022, 5:37 PMWhile it is possible for assistive technologies to access these properties directly through the Document Object Model [dom], the preferred mechanism is for the user agent to map the states and properties to the accessibility API of the operating system.So for browers, they’re primarily not looking directly at HTML for a11y info, but the browers translate the HTML into ARIA info and feed that into screen readers and similar tools. And it looks like there’s a JS API for dynamically providing these ARIA attributes when you can’t/don’t want to use DOM-based attributes https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA
CLOVIS
07/13/2022, 4:47 PM