Skip to content
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

Specificity to terms and service guidelines #140

Open
ariadnebrazo opened this issue Jun 1, 2020 · 0 comments
Open

Specificity to terms and service guidelines #140

ariadnebrazo opened this issue Jun 1, 2020 · 0 comments

Comments

@ariadnebrazo
Copy link

ariadnebrazo commented Jun 1, 2020

The terms and service guidelines indicate the requirements that terms and conditions be easily understood. This is excellent and easily understood in and of itself. However, the purpose of a standard is to ensure companies/orgs are following specific guidelines across the board.

Can we update these guidelines to add some specificity to what "easily understood" means? Perhaps things such as

  1. Word count limits
  2. Accessible grade reading level (8th grade?)
  3. Standard titles of sections the ToS must address (such as whenever I check ToS on a website, I am familiar with what sections to look for because they are all the same)
  4. Explicit instructions on where ToS is located and what makes the locating of ToS easy
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant