Meeting minutes
Announcements
Mary Jo is out next week.
We will meet next Thursday - Chris will lead.
Work statement has been merged into main, there were some last minute tweaks to links and other details.
Not sure if it is live yet - will check. Work statement will then be publicly available.
EN 301 549 - there is a new public draft for review.
https://
shadi: multiple updates during a few days. Minor updates with references. latest v12 should be stable for 4 weeks while in review. Not all WCAG2ICT aspects have been incorporated yet (e.g. in section 11 on software).
shadi: If you spot any gaps then post in GitLab - this should be the last public draft. Next one should be end of April - which should be the last update that then gets approved and published.
… timing of comments for EN: now set for 6th March (1 month from now).
Sam: Are we as WCAG2ICT going to provide feedback on EN 301 549? Should we?
mitch11: No official answer on this - but Mitch is happy to trade notes to avoid duplication of effort on this in making comments. Mitch is going to do what he can to give input on outstanding WCAG2ICT issues.
maryjom: Have been creating spreadsheets in Google Drive -could then use one to track who is reviewing which part of the document.
… ITI comments are confidential - so these can't be distributed.
EN GitLab is publicly viewable so you can search and see if anyone else has already made the comment.
Suggestion: Add in title WCAG2ICT for any new issues in GitLab to make it easy to find outstanding issues.
Sam: Are they taking WCAG2ICT verbatim, or are there modifications?
shadi: An example 1.4.12 : line height. We provided notes in WCAG2ICT. The essence of these notes was put into a precondition into the EN draft.
… EN took notes from WCAG2ICT and made it more explicit.
shadi: Does need careful review.
Sam: Could be an overqualification of requirements - if we suggested that these were not globally applicable. Worth reviewing.
… WCAG2ICT is not prescriptive, but EN is.
Explainer
SC analysis kickoff
[Mary Jo sharing above spreadsheet via Zoom]
2 separate analysis spreadsheets.
SC language changes: https://
Technology-specific notes: https://
On Technology-specific notes: table at the top is to suggest what we might cover.
Mobile is an obvious inclusion. Input taken from JJ.
JJ happy to collaborate
Considered other technologies that are covered in the EAA, Section 508 and other standards.
If you have anything you think should be considered, add to that first table
Sam: Don't have permission to view document. If anyone else does not have access, then email Daniel to request access.
… What is difference between pre-installed software on laptops, and any other software?
Software that you buy & install after purchase of the laptop - is not covered by EAA, whereas software that is already installed at point of purchase of laptop is.
mitch11: Saw somebody had added e-reader, but think we need to also consider ebooks (content) independent of a hardware device.
Same could be said for media terminals - e.g. content on a smart TV, not the device itself. We mean the software aspects of these devices.
Direct link may work
Mary Jo to add to work for the week wiki links
shadi: we should be careful not to reinvent or step on others toes (e.g. epub).
<ShawnT> I know there was limitation access when you use Microsoft documents like (.docx and .xlsx) on Google Drive.
<bruce_bailey> ePub probably has a mapping document, and if not, we could do one
<Zakim> bruce_bailey, you wanted to ask for spreadsheet URL and to discuss thanks to having both ebooks and reader
Need to coordinate with epub team.
bruce_bailey: Thanks for breaking out ereaders from ebooks. Love that WCAG2ICT that we defer to other groups like epub, but there may be a mapping that we could reference directly.
… may also have to repeatedly state software on hardware every time we reference hardware.
mitch11: Had forgotten epub standard!
mitch11: EAA could also include PDF and other formats, not just epub
for ebooks, EAA will not rely on EN 301 549 - there will be a separate specification coming from the Commission.
Could de-prioritise ebooks if it is covered elsewhere
<bruce_bailey> https://
Mary Jo to put out survey so we can vote on priorities
<bruce_bailey> and https://
<bruce_bailey> https://
Have a separate spreadsheet for the SC language changes
Look at any SCs where we might want to replace existing language. E.g. consistent identification. Any that might benefit from suggesting language tweaks that better suit for non-web technology
Email has been sent to entire task force asking for input.
Also want a separate focused meeting to work through the detail of these analyses.
Those who would like to meet, reply to email giving availability.
Mary Jo looked at changes in WCAG 2.2 in the December publication, now in the process of looking at what has changed, then editors to look & see if any of that language needs to be updated in WCAG2ICT.
… Final step would then be to make a pull request with all these changes for all to review.
Explainer
We are still working on the content in this.
Introduction has been worked on. Instructions that will disappear are highlighted in blue
Some draft content in intro
Who develops & background & dev history still to be worked on
Goals: not sure if we need it - the intro may contain this
Who WCAG2ICT for - nice approach.
What WCAG2ICT does not do - several bullets added. Please review.
Question. Should we add EN standards from other regions? e.g. Canada, India, Kenya, Japan?
PhilDay: Not sure why we add Canadian ATM standards, and not other ATM standards from other countries.
mitch11: Good point - instead of just saying informative references - give some preamble to state that these are documents that we used / referenced in the writing of this.
<shadi> https://
mitch11: What is the latest on WAI laws & policies. Should be added as a reference.
<Sam> how about EN 301 549, S508 and others
mitch11: WAI may be out of date.
shadi: Difficult to maintain list of policies, but also difficult to maintain this list of informative references. So maybe don't include here in a separate list, and have it added to WAI.
Sam: Seems it will always be problematic to list them all - just list the 2-3 most popular then say others...
mitch11: Like the idea of adding to WAI and linking to that, if we have the permissions suitable to allow changes & additions.
Mary Jo to follow up with W3C staff
mitch11: If the answer is maintain/improve - that is good. If not, think we need to add a few references in our document.
shadi: My understanding that there is a staff person who keeps documents up to date - so expect they will be happy with us giving input & suggestions.
<bruce_bailey> Apologies, I have to drop to set up wcag3 subgroup call.
Work is moving slowly. If you can help with any of the sections in the Explainer, that would be greatly appreciated.
Have a good amount of work ahead of us on the analyses and explainer doc
<mitch11> PhilDay do you have a minute to stay on?