-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This is a review of Collaboration_Tool_Accessibility by COGA #11
Comments
please send feedback in an email to the coga list and cc me, so we can track this |
Thanks, Lisa. Unfortunately, we've been unsuccessful trying to read the Google Doc you point to. Usually, downloading a Google Doc into word helps low vision and screen reader users, but not this time for some reason we haven't identified. So, let me ask a quick question before working harder to access your text: Is this an update of the document already referenced in this Editor's Note of the FPWD? |
@JaninaSajka: I am going to follow up in different posts to ensure I understand the issues you are discussing. This post is about the access to the Google Doc. You said: I want to resolve this issue, but need to understand more about it. If email is easier, please reach out using that method. Please clarify if the issue accessing the Google Doc is due to:
Ensuring those that need access to COGA's documents is very important to the group. My goal is to get this issue resolved quickly. Thank you. |
HI
I understood this had been sent to APA last year. We tried to do this quickly to be inline with you end of year deadline. Jennie is away at the moment so I am trying to pick up this thread. I apologize for any redundancy.
review of Collaboration_Tool_Accessibility by COGA
Let us know if you need this to be entered in more detail
more details are here
inclusive meetings - Other teams working with COGA
Issues using W3C Tools and Processes from coga and
how to work with COGA
The text was updated successfully, but these errors were encountered: