Meeting minutes
<Joe_Humbert> zaxkim, agenda?
Apologies as I am rather new to the TF. Is there a set quorum that needs to be reached?
2.4.2 Page Titled updated proposal and Pull Request
<Joe_Humbert> w3c/
<Joe_Humbert> w3c/
joe_Humbert: taking the role of the chair. 2.4.2 discussions focused on definitions, the feasibility of visible page titles, and how titles can be supplied. Updated proposal now for disucssion.
Tanya: requested update based on the discussions, suggested that we wait on any decisions until this update has been merged.
3.1.1 Language of Page updated proposal and Pull Request
joe_Humbert: Requests TF members to thumb up if they are okay with the draft. Joe to put forward a new pull request.
Tanya: For 3.1.1 requested update based on the discussions, suggested that we wait on any decisions until this update has been merged.
<Joe_Humbert> w3c/
Tanya: highlighted updates, small changes based on the discussions, inclusive of the application to the platform level
joe_Humbert: For 3.1.1., requests TF members to thumb up if they are okay with the draft. Joe to submit a new pull request.
Tanya: will recreate two new PR for 2.4.2. and 3.1.1. and will share in the MATF Slack
ACTION: Tanya will recreate two new PR for 2.4.2. and 3.1.1. and will share in the MATF Slack
2.5.3 Label in Name updated proposal and Pull Request
<Joe_Humbert> w3c/
<Joe_Humbert> https://
joe_Humbert: 2.5.3. had limited updates in April. Discussions focuses on grouped elements, how hints (user turned on hints vs hints turned off for ATs). There were two polls (w3c/
reflects discussions on the accessible name, whether all visible text needs to be included or could it be included in other accessibility attributes.
<Joe_Humbert> https://
joe_Humbert: no discussion, moves to reviewing the current PR. Generated a new preview. Directs MATF member to submit a review using the options available through the Submit Review functionality in GitHub.
2.5.7 Dragging Movements updated proposal and Pull Request
<Joe_Humbert> w3c/
joe_Humbert: 2.5.7 discussion on the confusion about dragging vs pointer events, concerns on the term single pointer. Single pointer decided to stay as it is inherited from WCAG to ICT, WCAG 2.2. but discussion led to the suggestion to have a note to clarify. Proposal is to drop the original Note 1 and Note 2, keep Note 3 and 4 (which would become
Note 1 and 2). Suggestion to clarify single pointer; to keep consistent with other success criteria, single pointer to link to definition.
<Joe_Humbert> w3c/
joe_Humbert: reads the new 2.5.7 proposal and invites discussion. No discussion. moves to reviewing the current PR. Generated a new preview. Notes that there is a broken hyperlink as there a missing link for the definition for the underlying platform software, as we are still need to approve the definition. Directs MATF member to submit a review
using the options available through the Submit Review functionality in GitHub.
joe_Humbert: Will need a minor update. We can merge the link in the future as soon as the definition has been approved.
Software layer definitions
<shoobe01> https://
<Joe_Humbert> w3c/
shoobe01: Worked on the Miro with Rob. Utilized layers to visualize; the colours are meaningless. Will use a different tool for the final version with colour specified to each layer. Final diagram will be simple with just the layer with text definitions and links.
shoobe01: trying to make the content relevant and clear to consumers of the document and app builders, without being too explicitly accurate. There are two open issues: should the user be the top layer or should content be above the user? Currently, user is at the top.
Tanya: Is the mobile application that is being built fall under the definition of user agent?
shoobe01: We consider a browser to be the user agent since we're extending outside of browsers to native applications. It's like the same thing that for non-web content inside of an application. the user agent is the interpretive layer for that content.
Tanya: raises that that this would out of scope of WCAG,a nd would fall under the User Agent Accessibility Guideline.
joe_Humbert: This would mean that significant portions of the WCAG guidelines wouldn't apply to it
Tanya: Yes, as the user could be in control of how they build their mobile apps. If we say that an application is a user agent, there would be difficulties in interpreting the gudiance.
shoobe01: Took direct notes in the Miro. Maybe user agent is the wrong label for the layer.
shoobe01: Other open issues is on the definitions for assistive hardware or software. Are typical users going to consider the device as the whole package or the processor only? Keyboards, etc.
joe_Humbert: IMO, don't think most users would consider an external keyboard
shoobe01: Yes, but at point do we change from external keyboard being accessory to system? We just need a defintion.
joe_Humbert: tasks the MATF to comment in the Miro board or in the GitHub
<Joe_Humbert> https://
<Joe_Humbert> https://
Tanya: updated 2.4.2 and 3.1.1. github issues
joe_Humbert: tasks MATF members to review 2.4.2 and 3.1.1.
Meeting ended at 9:59 am ET
<Joe_Humbert> thank you sam-estoesta
Happy to scribe!