Mauve 👁💜

@Azure @alcinnz @loke @lunch I love that! Yeah one thing I've been thinking about too is instead of HTML rendering, the browser could parse out the semantic components and let the user bring their own component sets to represent the data.

Defs more useful for content based pages than apps, but I think there could be paths between those worlds.

Also a reason I've been more curious about stuff lately.

1
lunchy

@mauve @Azure @alcinnz @loke an issue with this is that html is too low level and tools are too inconsistent for this to be reliable, the current ways we do it are by relying on manual aria attribs and lots of heuristics

1
Mauve 👁💜
Follow

@lunch @Azure @alcinnz @loke Yeah agreed. For HTML I was thinking that limiting to what's defined in the ARIA accessibility tree would be a good place to focus.

for more complex data semantic web schemas could give us more options on how to interpret data.

· · Tusky · 1 · 1 · 2
alcinnz

@mauve @lunch @Azure @loke There's also the `itemprop`, `itemid`, `itemref`, `itemscope`, `itemtype` attributes noone uses...

0
Sign in to participate in the conversation
Mauvestodon

Escape ship from centralized social media run by Mauve.

Resources

Developers

What is Mastodon?

mastodon.mauve.moe

More…

v3.5.10 · Privacy policy