Summary of Github issue (Part 1) - access to Google Docs

Hello,
I am reviewing the response from Janina in Github, and am working through the issues discussed in the thread.
This email is about the access issue to the Google Doc.

  *   I have responded to Janina to ask more about the access issue.
  *   I began some testing on our Google Docs.
One issue I have noticed: some of our Google documents require permissions to access, while others do not.
Do we have a decision making location that discusses how we decide this?
Example: in the post by Lisa on Github 2 weeks ago:

  *   2 documents do not require permissions to view: inclusive meetings, issues using W3C tools and processes from coga.
  *   1 document requires permissions to view: how to work with COGA.
And once decided, where are the documents that get public access stored so they provide this access?
Recommendation is to have 2 Google Shared Drive folders:

  *   Rename the current COGA Task Force Shared Drive (WCAG)
     *   Suggestion: Members only COGA Task Force Shared Drive (WCAG)
  *   Add a second folder:
     *   Suggested name: Public access COGA Task Force Shared Drive (WCAG)
I welcome your discussion on this.
Jennie

Jennie Delisi, MA, Certified Professional in Web Accessibility (CPWA)
Accessibility Analyst | Office of Accessibility
Minnesota IT Services | Partners in Performance
658 Cedar Street
St. Paul, MN 55155
O: 651-201-1135
Information Technology for Minnesota Government | mn.gov/mnit<http://mn.gov/mnit>
[Minnesota IT Services Logo]
[Facebook logo]<https://www.facebook.com/MN.ITServices>[LinkedIn logo]<https://www.linkedin.com/company/minnesota-it-services/>[Twitter logo]<https://twitter.com/mnit_services>

Received on Monday, 13 February 2023 15:54:26 UTC