On 29 October 2014 14:15, R. Tyler Croy <[email protected]> wrote: > (replies inline) > > On Wed, 24 Sep 2014, [email protected] 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. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
