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

Was the accessibility statement generator, viewed and commented by lawyer(s) #103

Open
DavidMacDonald opened this issue Nov 29, 2018 · 3 comments · May be fixed by #161
Open

Was the accessibility statement generator, viewed and commented by lawyer(s) #103

DavidMacDonald opened this issue Nov 29, 2018 · 3 comments · May be fixed by #161
Labels
content Issues related to content change enhancement New feature or request question Further information is requested
Milestone

Comments

@DavidMacDonald
Copy link

There appears to be quite a variety of opinions about accessibility statements and liability in the US where there is particularly a lot of litigation. I'm not sure that an organization would want to say

"You are entitled to escalate a complaint to the national authority, should you be dissatisfied with our response to you."

Why would an organization say that? It seems to be "leading with the chin". I'm wondering if lawyers that regularly represent defendants have contributed and commented.

@nitedog
Copy link
Contributor

nitedog commented Nov 29, 2018

Thank you for your feedback @DavidMacDonald

Yes, we are aware of the issues across different regions. This is why nothing is required by the tool. Please see the additional information about this particular item, which says:

In some situations you may want to or may be required to provide information about a formal complaints procedures. For example, a quality management process within your organization may require you to establish a formal complaints procedure with clear escalation paths. The EU Web Accessibility Directive foresees EU countries to have legal “enforcement procedures” when users are not satisfied with the responses from public bodies. Inform users about any such formal complaints procedures. This may also motivate them to provide you with valuable feedback about the accessibility of your content.

Please re-open the issue if that does not address your concern.

@nitedog nitedog closed this as completed Nov 29, 2018
@DavidMacDonald
Copy link
Author

DavidMacDonald commented Nov 29, 2018

@nitedog I think it should be vetted by a lawyer involved in the defence of organizations that normally would post this type of information. I would also put a disclaimer on the tool

"this tool is not providing legal advice [blah blah blah], if you have questions please consult a qualified attorney."

@nitedog nitedog reopened this Nov 30, 2018
@nitedog nitedog added help wanted Extra attention is needed question Further information is requested labels Nov 30, 2018
@nitedog nitedog added this to the First Release milestone Dec 6, 2018
@rvantonisse rvantonisse added enhancement New feature or request content Issues related to content change labels Mar 28, 2019
@nitedog nitedog removed the help wanted Extra attention is needed label Jan 27, 2021
@shawna-slh
Copy link
Contributor

Hi @DavidMacDonald

Shadi says the statement that you quote in the beginning of this issue was in a draft and is not in the final published work. (after I spent time searching for it! ;-)

I think that at least one lawyer was involved this work. And at least one actively supports it:

NEW: Check out the Accessibility Statement Generator from the Web Accessibility Initiative (WAI) of the World Wide Web Consortium (W3C). It’s part of a great new page of information titled “Developing an Accessibility Statement.” [reference]

This resource (and others) are covered by the W3C disclaimer, which is available from a link in the footer:

COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE DOCUMENT OR THE PERFORMANCE OR IMPLEMENTATION OF THE CONTENTS THEREOF. [reference]

I spent some time considering additional disclaimer wording that we might want to add to this resource. I haven't convinced myself that it is needed or even particularly useful. Can you provide use case(s) / scenarios that you think we might want to address?

Or, does the info above compel you to say OK and close this issue? :-)

nitedog pushed a commit that referenced this issue Jul 26, 2021
Closes #103 per suggestion from @shawna-slh
@nitedog nitedog linked a pull request Jul 26, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Issues related to content change enhancement New feature or request question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants