Meeting minutes
2025 update
<julianmka> JJ: Recaps 2024 activities: SC discussed and guidance drafted; Group Note title determined; editor's draft published. In 2025, more SCs to discuss/determine guidance for. Currrently revising the working statement for approval by AGWG.
<julianmka> JJ: Any other reflections or thoughts about what we've done so far?
<julianmka> julianmka: We need to divide and conquer the remaining SCs and other related issues outside of meetings, not just during.
1.4.10 Reflow
<julianmka> JJ: Recaps discussion on 1.4.10 to date (Issue #4 at Github).
<julianmka> ...WCAG2ICT says that 1.4.10 applies to non-web, replacing "web content" with "content" and adding some notes.
1.4.10 Understanding draft: https://
<julianmka> Illai: Mobile has limited "real estate" so our guidance should be a bit more tolerant in light of that.
<julianmka> JJ: Shared Understanding draft linked previously. It gives an example of a horizontal scrolling area that would meet 1.4.10 provided the content of each panel in the scrolling area fits within 320px. Still very web based; apps are different with small mobile hardware.
<julianmka> Jamie: Should consider identifying if the pixel widths specified assume that that content is at 100% zoom. This question has come up before in the workplace.
<julianmka> JJ: Testing this is something we need to address. To address Jamie's question in Github, my understanding of orientation is just to check if the content rotates, nothing else.
<julianmka> JJ: Brings up Detlev's comment linked in another repository, which will refer to MATF's decision.
ACTION: Make decision about the viewport requirements
ACTION: Define testing steps for 1.4.10
ACTION: Investigate how internationalization relates to 1.4.10
1.4.13 Content on Hover or Focus
ACTION: Research usage of a mouse on Android / iOS
<julianmka> JJ: Recaps discussion until now on 1.4.13. (Github issue #6). Initially, we thought this SC would have small variation from WCAG2ICT but after discussion, moved it to medium variation instead because of additional research.
ACTION: Research how tooltips behave on mobile web with touch input
ACTION: Research how assistive touch works on mobile devices
<julianmka> julianmka: Tooltips on the web could mean almost anything, what scope does that research have?
<julianmka> JJ: Native web tooltips, like the title attribute.
<AlainVagner> could we refer to the tooltip pattern of the APG? https://
<julianmka> JJ: also the abbreviation tag shows a tooltip on desktop web
<Joe_Humbert> +1 AlainVagner in addition to title attribute
<AlainVagner> seems to be still a work in progress, sorry about this
Sample page for tooltips: https://
<Joe_Humbert> mdn example doesn't load on my chrome android :-(
close the queue
<julianmka> Aash: Links with tooltips don't work on mobile, but buttons with hover effects generally work.
<julianmka> Illai: Looking at Heydon Pickering's example, there is no definition of "tooltip", or even more widely on the web. Perhaps we should define what it means in the scope of native mobile.
ACTION: The phrase "tooltip" needs to be defined