[SERVER-25750] The VPAT (508 compliance) documentation is missing Created: 23/Aug/16  Updated: 19/Nov/16  Resolved: 03/Nov/16

Status: Closed
Project: Core Server
Component/s: Packaging
Affects Version/s: None
Fix Version/s: 3.4.0-rc3

Type: Improvement Priority: Trivial - P5
Reporter: Jason Pyeron Assignee: Ian Whalen (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Participants:

 Description   

The Voluntary Product Accessibility Template (VPAT) is a document which evaluates how accessible a particular product is according to the Section 508 Standards. It is a self-disclosing document produced by the vendor which details each aspect of the Section 508 requirements and how the product supports each criteria.

Creating this document ensures easier adoption by organizations and agencies which require software to comply the United States' Rehabilitation Act of 1973 aka section 508 compliance.



 Comments   
Comment by Githook User [ 03/Nov/16 ]

Author:

{u'username': u'jpyeron', u'name': u'Jason Pyeron', u'email': u'jpyeron@pdinc.us'}

Message: SERVER-25750: updated VPAT to remove obsolete contact information and methods

Signed-off-by: Ian Whalen <ian.whalen@gmail.com>
Branch: master
https://github.com/mongodb/mongo/commit/85da90453648d5d1d47a3f4d5aa45b58b526c4d4

Comment by Githook User [ 03/Nov/16 ]

Author:

{u'username': u'jpyeron', u'name': u'Jason Pyeron', u'email': u'jpyeron@pdinc.us'}

Message: SERVER-25750: added VPAT (508) documentation

Signed-off-by: Ian Whalen <ian.whalen@gmail.com>
Branch: master
https://github.com/mongodb/mongo/commit/a00ac5695ffa65b0f4fe3089eb1943ff51b07b58

Comment by Jason Pyeron [ 07/Oct/16 ]

@ian.whalen welcome to the ticket, please let me know if there is any thing we can do (e.g. freshen up the PR).

Comment by Jason Pyeron [ 25/Aug/16 ]

Agreement completed.

Comment by Daniel Pasette (Inactive) [ 24/Aug/16 ]

Thanks Jason, I think that's actually a pretty reasonable answer. If you will sign our contributor agreement I'll have someone review this PR.

Comment by Jason Pyeron [ 23/Aug/16 ]

This seemed like the best location to mitigate "policy" hurdles for your government adopters.

Is there a better location than the docs dir?

The lazy answer is that it works well here. A more philosophical answer would be it is like any other readme and a potential source for packaging during build. Additionally, this doc should be changed when the source changes in a way to make this document out of date.

Lastly, the website will never be 100% in sync with the source tree, and the 508 people will ask where is the VPAT for that version (commit). (I know this is not a reasonable argument, but bureaucrats are not always reasonable)

Comment by Daniel Pasette (Inactive) [ 23/Aug/16 ]

Hi Jason, thanks for the PR and the notification.
Although the public documentation clearly needs to be updated, do you think this should live on the website or directly in the mongodb server git repository?

Generated at Thu Feb 08 04:10:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.