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

Status and Updates too wordy #12

Closed
nitedog opened this issue Feb 8, 2017 · 8 comments
Closed

Status and Updates too wordy #12

nitedog opened this issue Feb 8, 2017 · 8 comments
Assignees
Labels

Comments

@nitedog
Copy link

nitedog commented Feb 8, 2017

  1. "Last updated" could be a single line, no need for a full sentence. Actually, we might have "last updated" for every entry as it is ambiguous on the page level.
  2. We should have a button/link to an input form for updates, like we have on the tools list. Maybe also here have an additional link for every item that would pre-fill the form for easier updating
@bakkenb
Copy link

bakkenb commented Feb 8, 2017

Agree with Shadi on the first point here. If I see that there was a new 'last updated' date since I last visited, I would have no idea of what content was last updated. It would be nice to know if a specific country or state/province was updated, and would be more relevant to what information I am looking for.

Maybe the paragraph could work better this way:

This page is updated on a regular basis as new information is received. You will see a "last updated" date for each country to inform you of how current the data is. Know of new or changed laws or policies not listed, or corrections needed, [submit updates to Web Accessibility Policies(link)].

@shawna-slh
Copy link
Contributor

Agree to delete "This page was updated on 03 Feb 2017 and will be updated on a regular basis as new information is received."

See also #7

@yatil
Copy link
Contributor

yatil commented Feb 10, 2017

You can make edits to the texts here: https://github.com/w3c/wai-policies-prototype/tree/gh-pages/_help

@yatil
Copy link
Contributor

yatil commented Feb 10, 2017

@nitedog I’ll put your point number 2 into a separate issue so it is easier to follow.

@dboudreau
Copy link

dboudreau commented Feb 10, 2017

+1 for the shortest, most straightforward wording possible.

The last updated date could be dynamically generated based on the last update to the document. No maintenance required.

@maryjom
Copy link
Collaborator

maryjom commented Feb 10, 2017

To clarify, this is about the Status and Updates section at the top of the page since update information will be throughout the page. Remove that section, and simply have a button/link to submit updates somewhere toward the top of the page. See tools page for info for ideas on where to put the button, and potentially have a way to request to update existing entries where the submission form is pre-loaded with today's info to update.

@iamjolly iamjolly self-assigned this Feb 10, 2017
@shawna-slh
Copy link
Contributor

Discussion in 10 Feb telecon

@maryjom
Copy link
Collaborator

maryjom commented Mar 30, 2017

The status and updates part has been edited to shorten it significantly. The headings are going to be collapsed into one heading with the pertinent information for the page which is being tracked with issue #13 and the addition of a working submission button is being tracked with issue #18. I'll copy over comments about potentially having a submit updates button on individual country parts to pre-fill the submission form into Issue #18 to keep these issues more distinct.

@maryjom maryjom closed this as completed Mar 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants