Meeting minutes
<Detlev> Welcome Jatin!
User Agent definition
<JJ> JJ: This is an example
<JJ> Recap of 28 January
<JJ> First attempt of diagram: w3c/
<pauljadam> web view still can allow pinch to zoom
<JJ> JJ: Summarized discussion about the diagram and remarks about WebViews + User Preferences in context of EN 301 549
Detlev: software should take underlying system settings for text size etc, but unclear how this works for web views. If setting not on layer below then this may not apply - this could be a get out for developers.
<Detlev> agree!
<shoobe01> +1. Miro good idea for e.g. allowing inline comments etc. I will be adding dozens more I think :)
<JJ> JJ: Thinks that its not unreasonable to expect app developers to make web content fully accessible, e.g. considering user preferences. If not able, they can open the web content in browser, or use native components, or pass user preferences using headers / url parameters / etc.
<JJ> RobW: Explaining the Miro diagram from technical perspective
<JJ> quintinb: Added comment about adding a layer after Platform Software for frameworks like React Native and Flutter
<JJ> Comment 1: Does assistive tech in mobile fall under application software?
<JJ> Comment 2: on Application software level -> The browser is the underlying layer for User Agent (UA) based presentation, this might need different definition
<JJ> For further comments, lets reply on Miro.
<pauljadam> miro might actually be accessible, I've seen them present on the topic and was impressed
Detlev for web you can use any authoring tools to create the software that is rendered by the browser. Native may be different, but maybe the distinction of platform software is unhelpful
<shoobe01> Discussion of SVG a11y in W3C Slack in last 2ish weeks. It's more fraught than it should be, may take some manual work, so keep in mind for effort when time to make production graphics.
shoobe01 we should output a diagram in addition to text
<JJ> Example of WCAG-EM 2.0 with graphics: https://