Meeting minutes
<janina> /join #rqtf
matatk: Worthwhile to investigate keyboard shortcuts across platforms - synching this has been tried 15-ish years ago. We may want to try again. On Mac, it should be Command-Shift A.
Agenda Review & Announcements
matatk: Announcement: Call next week, 12th Feb, will be format change.. first half is focused on FAST/task force as well as chairs/Fredik. For more info on FAST and specs that generate good A11y, recommend attendance.
<matatk> https://
<janina> The Framework for Accessible Specification of Technologies (FAST) Task Force develops and maintains an inventory of both user and functional needs; develops best practices guidance describing the features that web
<janina> +technologies should provide to ensure accessible content can be created; and maintains the self-assessment tool used by W3C Working Groups during the W3C accessibility horizontal review process.
Janina: Note that this is also used by horizontal review groups
APA Re-chartering
<matatk> File in repo: https://
Janina: No additional news on charter - continue working on task forces, their description, approvals, etc. Roy will return soon and time and resources will be spent on making all the changes we want to make.
<matatk> HTML preview: https://
New on /TR
DIDs
<matatk> w3c/
<matatk> History: https://
<matatk> Revision history of DIDs doc: https://
matatk: New TR (Technical Recommendation) track on GitHub (used to be on the wiki). After future reviews, updates and versioning will be captured - 1.0 is a recommendation in 2022 (July), public working draft is now out to allow commentary as early as possible. Shift left reviews on public drafts encouraged to avoid excessive comments at the
point of horizontal review.
matatk: There are some improvements to the format of the spec itself. This group is agreeable to A11y changes or improvements. Would anyone like to review since last update (Revision history- about 10 changes)
niklasegger: I would like to review as would JonCohn
matatk: For review items of concern, draft a comment and bring to one of these meetings to decide if it's worth creating a comment to that group.
matatk: Will provide recommended format for comments to see if this 'new' format is worthwhile using
String Searching
<matatk> APA longitudinal tracking issue: w3c/
<matatk> Paul's proposed comment: w3c/
matatk: Review of fuzzy matching comment - any comments or questions?
janina: any COGA concerns here?
Eric_hind: I think it's worth a COGA review. I wonder how best to take it to COGA?
janina: It's up to you :-).
Eric_hind: I'll take it to COGA and we can raise any issues.
matatk: Spec is linked in issues/8 - there is no discussion in that issue. The proposed comments are where we discuss it.
matatk: Issue 222 is where we talk about Pauls' comment only. This is where we decide on pushing this forward to the main issue or not.
matatk: In this case, for COGA, do we like this comment in relation to string searching? We (COGA) may want to deep dive, we may be OK with it, we may want to broaden the commentary in the A11y review repository. Each problem becomes a separate issue. Otherwise, COGA can just comment on the issue 222 thread (COGA comments). If COGA is OK with
it, then it gets converted into a real issue
matatk: This process to convert from prospective comment to committed comment is fairly easy and will be fully documented
matatk: Some items on agenda are delayed waiting for people.. will bring up in future meeting.
Other business
Eric_hind: I was asked if there are any recordings of using GitHub with a screen reader, to see how to use it?
janina: I can point you to some power users. A lot of power users love the command line interface (gh, the repo is cli/cli). Some use the web UI.
Fredrik: I use GitHub via the web. It's powerful, but I don't find it complicated.
… Reach out to me if you have any questions!
<Zakim> mike_beganyi, you wanted to discuss naming FAST presentation
<Fredrik> That is neat!
mike_beganyi: q+ "to" feature is very helpful.
mike_beganyi: Suggest The FAST and the Curious for presentation title :-).
<Fredrik> WAI in...?
janina: It's a really important opportunity to provide input to WCAG 3
Janina: We should reinvite the group of guests from the work coming out of Adapt. very useful and fascinating