I’d post in one place with pointers from others that note “please go over there for discussions” to avoid having two or more (diverging) discussions.
I don’t know what the best way forward is.
The document is great because you can look at it and even without knowing much about WCAG you can see what the items are that need work. Then question then is “ok, what needs changing and what does it need to be changed to?” Following the link to https://www.w3.org/TR/WCAG20/#ensure-compat-rsv I’m still none the wiser as to which attributes or additional HTML elements need to be added or if that is even the thing to do.
Probably if you are an experienced in working on this you take one look and know what needs to be done. However that person will probably not have experience in how the notebook code is organised, so they’ll get stuck trying to work out where to change stuff.
The place I’d start is to take each of the items in the document, check if there is already an existing issue for it on the notebook repository, then create/add to an issue the description from the document with pictures. To do item: determine what HTML stuff needs to be added/removed/changed (the outcome would be something like “all
<input> items need a
<label> tag describing them, an example is link-to-an-example”). Now someone else can pick up the issue and either do it or figure out where the change needs to happen.
Divide and conquer with the goal that each “to do” takes a few minutes for a person with the right skills. Then if we advertise it people can pick off onne or two when they have a short amount of free time. “Ah, I’ll do something nice for the project, I’ll go and update some HTML by following the instructions left in the issues” or “I’ll do something nice for the project and translate human words describing a problem into concrete changes needed”.
The other thing that would be helpful for items like the “change in notebook state isn’t announced” is to expand the “how to reproduce” instructions. Right now it says “perform any of the tasks while using VoiceOver”. I have no idea how or what voice over is :-/ which means in a short break I won’t try and work on this because I don’t know how to “see” (in this case hear…) the problem.
The hard part isn’t that people can’t find out if they invest enough time but that people don’t have the time to invest. Which is why I think breaking down the tasks into “5 minute” tasks will be helpful. Even though it feels like spoon feeding.