Meeting minutes
<Jemma> Meeting agenda: https://
<mck> can someone unmute me?
PR burndown - Code viewer slider
<jongund> I am not
MK: March 9th CSUN
MK: We will have meeting on Mrach 9th
<CurtBellew> For some reason the call details link isn't working for me
MK: Experiancing VO problems or browser problems
The focus seems to change in response to some of the keyboard events
MK: Can any one dig these issues?
MK: VO doesn't have own command to go to first or last value
JK: When tested with slider with VO, it worked well
MK: iOS/VO ignores grouping stuff
MK: gesture is getting registered when scrolling the page instead of scrolling slider
JN: See some strange things going on with VO
JN: So I mean know what you know just map but yeah there's this, there's some particularly strange things going on when you use a mixture of voiceover interaction models and standard tab navigation and worth it. Yeah. It's like voiceovers getting confused and thing. So, so, I mean the one that's particularly weird for me is if I'm interacting with the green slider and moving up and down using voiceover controls and then I press tab and go to the b[CUT]
JN: Is it deliberate design decision to have double focus ring?
JN: It is rarely used to use double focus indicator, it may cause confusion.
JN: One around the thumb, one entirely the label and slider
MK: Having focus around the thumb might be good?
JN: Sometimes you worry about how noticeable the differences but yeah so I mean, looking at native input type course range it just puts one around this, the slider control itself not the label that's associated with it, and not having one on the thumb.
CM: Ask Joe to look at Focus indicator?
JN: Suggest to remove focus around the entire slider and have focus on thumb
<mck> From Accessibility Features: • Use of SVG enables high contrast support by providing a means for text and rect element to adapt to high contrast colors using the currentColor value
<mck> for the stroke and fill properties.
PR burndown - Disclosure navigation menu with top-level links
MK: Can you translate the bullet with SVG?
JN: we are using current color property to match the system colors
MK: Can you update the document so that user can understand without looking at code?
CM: can you add word inline?
CM: I will take care of that part of documentation
MK: Pointer events main benefit is touch based AT can enable the keyboard event. It is worth to mention it in the Pointer bullet
MK: I will work on the wording for the pointer bullet
JK: Support Matt's view
MK: WOrk on pointer wording piece, JK work on visual review, Jon will work on SVG bullet point
<Jemma> https://
Plan file directory treeview updates for aria-at
MK: disclosure navigation menu
PR burndown - Disclosure navigation menu with top-level links
SH: Matt you had a question about where focus was moved on that one. Yes. Can I put it on the container is because, like, as opposed to the other examples that are actually supposed to handle focus. This one isn't actually supposed to handle focus at all. The only reason it does is because code pen had that issue with the links. So it's trying to just fake like default link behavior. Ah, sort of like what would happen as the body, were to receive [CUT]
MK: Is fine on how it looks
SH: The other changes should be there and figuring out why there's like a get like a GitHub check do now but otherwise I think it would be ready.
JK: Focus line goes out of the border box
SH: This is same as other disclosure navigation examples
JN: In terms as visual design review, Focus ring is too thick and is going out the border
SH: Didn't made any changes to focus styles.
SH: It is same as the one without top level links
JN: Focus styling is different on menubar and navigation preview
MK: It is fine to have different focus stylings as long as it is useful.
CM: Escape key comment
MK: is this escape behavior still necessary because of WCAG and I, I am pretty sure you know when I read the WCAG. Success Criterion that it doesn't apply.
SH: I think that was just in there because it was in the other example, which didn't happen. So the menu bar one goes up hover.So I removed it
MK: question regarding the why don't menu role is not used
<Jemma> "Note: Although this example uses the word menu in the colloquial sense to refer to a set of navigation links, it does not use the WAI-ARIA menu role."
JN: How to help people to distinguish between aria menu example and not aria menu example?
MK: Added a second sentence explaining bit more regarding the difference
Plan file directory treeview updates for aria-at
<Jemma> Prioritize next steps in Tree and Treegrid Pattern and Examples Development Project
<Jemma> Issues to discuss:
<Jemma> Consider removal of File Directory Treeview Example Using Computed Properties | WAI-ARIA Authoring Practices 1.2
<Jemma> Update declared properties version to better illustrate need for declaring setsize and posinset
<Jemma> Tree View examples do not use aria-selected · Issue #666 · w3c/aria-practices
<Jemma> Treeview images need to be hidden from screen readers · Issue #1768 · w3c/aria-practices
<Jemma> mck:Tree View examples do not use aria-selected · Issue #666 · w3c/aria-practices