Meeting minutes
<Jem> https://
Setup and Review Agenda
Mike Pennisi (Bocoup)
Status of Site Updates
Matt_King: two things - APG Support tables and fixing broken links
AlexFlenniken: I've struggled with trying to tackle both of theses things concurrently.
AlexFlenniken: I'm going to fix the broken links and then I'll go back to the support tables and pick up that
AlexFlenniken: (technical notes on progress fixing broken links)
AlexFlenniken: As for redirects, I'd like to collect a formal list of "source" URLs and "destination" URLs, and hand that off to Dennis so that we can coordinate on including those in the next release of the application
AlexFlenniken: I want to take this as an opportunity to make the URLs more consistent
AlexFlenniken: I just updated this and I think it is ready to be merged
Matt_King: The upper-case file names are somewhat irregular, but if those particular pages are not going to cause problems during the build, then I suppose it's fine to leave it
AlexFlenniken: I expect to take on support tables next week
Pull Request Review
<Jem> w3c/
github: w3c/
jongund: I'll update the language as Matt_King has requested
Matt_King: Are there missing regression tests here?
jongund: We didn't have any tests for the condition where the previous or next date was not the current date. Should we add tests for that?
Matt_King: Are there any "page up"/"page down" tests at all?
jongund: There are a ton of unimplemented tests for certain keystrokes [lists specific keyboard keys]
Matt_King: We don't necessarily have to fix that gap with this pull request (though it is a great opportunity to do so)
jongund: I'm going to try to integrate some other test files in, along with their documentation
github-bot, end topic
github: w3c/
Listbox Examples: Update scrolling of listbox item with focus into view when page is magnified by jongund · Pull Request #2622 · w3c/aria-practices
<Github> w3c/
github: w3c/
Matt_King: The fact that we have multiple list boxes on one page is a problem, but we don't have to address that here
Jem: I'm adding a reviewer list to the pull request description, now
Matt_King: these examples were never reviewed on a mobile device as far as I know
Matt_King: I don't want to expand the scope of this pull request to include mobile bugs
github-bot: end subtopic
<github-bot> jugglinmike, Sorry, I don't understand that command. Try 'help'.
github-bot: end topic
<Jem> w3c/
Infrastructure: Update script that provides skipto menu on all pages to version 5.1 by jongund · Pull Request #2619 · w3c/aria-practices
<Github> w3c/
github: w3c/
Matt_King: I'll review copyright
jongund: I talked to someone at Paypal, and they told me that Paypal is ending support for a number of open source projects. The repository referenced in these comments has been abandoned.
Jem: I volunteer to perform a functional/visual review?
Matt_King: Depending on where this ends up on Friday, it may be possible to include for Monday
Matt_King: I don't think we need further legal advice on this one
<Jem> w3c/
github-bot: end topic
Landmark examples: Updated SkipTo script and configuration by jongund · Pull Request #2624 · w3c/aria-practices
<Github> w3c/
github: w3c/
jongund: We've been using a very old version of skipto
Matt_King: I'd like to hold off on this one for about a week. After that week, we may have to rebase or merge in the "main" branch
github-bot: end topic
ARIA TAB pattern and WCAG 1.4.10 Reflow
ARIA TAB pattern and WCAG 1.4.10 Reflow
ARIA TAB pattern and WCAG 1.4.10 Reflow
github: w3c/
CurtBellew: the short-term suggestion is to remove one or two of the tabs so that the content fits inside the frame and doesn't produce the scrollbars
CurtBellew: I found that scrollbars remained even after removing one of the tabs
CurtBellew: The solution might work, but we'll have to remove more than one tab
CurtBellew: As an alternative, we can produce verticle scrollbar, but one present only for the content which requires it (rather than for the entire document)
Matt_King: I'm wondering if tabs are the right user-interface design for this situation
Matt_King: We may need two examples. One for the "super-simple" case with a small number of tabs, and another that's more complicated and supports any number of tabs
jongund: We could use "overflow: hidden" with elipses so that as the text squeezes, you'll see just the beginning of each tab
JamesNurthen: I think a "simple" example like what Matt_King has proposed would help us write tests, but I don't think it's realistic for people to use that in the real world. Overflow occurs so commonly that an example which doesn't support it isn't very useful
Matt_King: Maybe the "simple" example should demonstrate the use of icons as table labels, since that is a more realistic application of a tab list which doesn't necessarily overflow
Jem: Chris Lane has a demo for "Overflow Tabs" which incorporates a drop-down to include tabs which would otherwise cause overflow
Jem: http://
JamesNurthen: I couldn't get this "menu button in a tab list" ready in time for APG version 1.3
Summary: We need proposals for icon tabs, and we need to open a separate issue for how we're going to handle overflow
github-bot: end topic
New About Section Content
Matt_King: I've done a lot of work on the content of the introduction page, and I have questions about what I've done. I'd like people to read it so we can discuss next time
github-bot: w3c/
<github-bot> jugglinmike, Sorry, I don't understand that command. Try 'help'.
github: w3c/