Jenkins CI and the accessibility of it's UI

[laura1...@gmail.com]

I’m not sure if this is the right forum for this request, but I was hoping someone might be able to point me in the right direction…

I was hoping someone might be able to provide a Voluntary Product Accessibility Template (VPAT) or similar
accessibility statement for Jenkins CI.  I have included a blank VPAT for reference.

What is a VPAT?
The VPAT is a tool used to document a product's conformance with the
accessibility standards under Section 508 of the Rehabilitation Act. The
purpose of the VPAT is to assist Federal contracting officials and other
buyers in making preliminary assessments regarding the availability of
commercial "Electronic and Information Technology" products and services with
features that support accessibility.

What is Section 508?
Section 508, an amendment to the United States Workforce Rehabilitation Act
of 1973, is a federal law mandating that all electronic and information
technology developed, procured, maintained, or used by the federal government
be accessible to people with disabilities. Technology is deemed to be
"accessible" if it can be used as effectively by people with disabilities as
by those without.

Thank you in advance for all of your help.

[doughansen08]

Did you ever get a response?  Is Jenkins ADA/508 compliant?

[R. Tyler Croy]

(replies inline)

On Wed, 24 Sep 2014, laura1...@gmail.com wrote:

>
>
> I?m not sure if this is the right forum for this request, but I was hoping
> someone might be able to point me in the right direction?

>
> I was hoping someone might be able to provide a Voluntary Product
> Accessibility Template (VPAT) or similar
> accessibility statement for Jenkins CI. I have included a blank VPAT for
> reference.

What's the goal of such statements? Not being too informed on software
accessibility challenges and requirements, I'd like to have an understanding of
the cost/benefit for the Jenkins project to release/publish such a statement.


I would recommend adding this discussion to the next project governance
meeting's agenda:
<https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda>



- R. Tyler Croy

------------------------------------------------------
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>

% gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
------------------------------------------------------

[Laura1fxjunk]

No I never received a response. 

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/yrcSJUOp2AU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[James Green]

On 29 October 2014 14:15, R. Tyler Croy <ty...@monkeypox.org> wrote:

(replies inline)

On Wed, 24 Sep 2014, laura1...@gmail.com wrote:

>
>
> I?m not sure if this is the right forum for this request, but I was hoping
> someone might be able to point me in the right direction?
>
> I was hoping someone might be able to provide a Voluntary Product
> Accessibility Template (VPAT) or similar
> accessibility statement for Jenkins CI.  I have included a blank VPAT for
> reference.


What's the goal of such statements? Not being too informed on software
accessibility challenges and requirements, I'd like to have an understanding of
the cost/benefit for the Jenkins project to release/publish such a statement.

It's fairly narrow for Jenkins I think. A commercial provider might consider it for large government contracts.

Given Jenkins itself is API accessible and otherwise has a convenient web interface, adoption of WAI guidelines is probably sufficient.

Half the time these statement requirements boil down to less than a page. It's there to ensure the supplier is aware of their responsibilities.