Bug 1785941 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

There are a number of US government agencies who use Bugzilla internally (NASA is a publicly visible example).  New US government projects have to comply with the new accessibility guidelines in Section 508 of the Communications Act, so if we want them to be able to upgrade we need to comply (at least in our newer versions).  See https://section508.gov/ . There is a template for a compliance statement at https://www.section508.gov/sell/vpat/ .

This is the master bug for a compliance audit.  Violations of Section 508 can be files as dependencies of this bug.

I am looking for a volunteer who could audit the 5.2 and harmony branches for compliance, file bugs for things that are violations as dependencies of this bug, and figure out how much of the VPAT we can actually provide at this point.  Even if we're not compliant yet (I suspect we aren't) I would love to be able to provide a statement with the 5.2 release saying how compliant we are, and listing what's left to be fixed to make us compliant.
There are a number of US government agencies who use Bugzilla internally (NASA is a publicly visible example).  New US government projects have to comply with the new accessibility guidelines in Section 508 of the Communications Act, so if we want them to be able to upgrade we need to comply (at least in our newer versions).  See https://section508.gov/ . There is a template for a compliance statement at https://www.section508.gov/sell/vpat/ .

This is the master bug for a compliance audit.  Violations of Section 508 can be filed as dependencies of this bug.

I am looking for a volunteer who could audit the 5.2 and harmony branches for compliance, file bugs for things that are violations as dependencies of this bug, and figure out how much of the VPAT we can actually provide at this point.  Even if we're not compliant yet (I suspect we aren't) I would love to be able to provide a statement with the 5.2 release saying how compliant we are, and listing what's left to be fixed to make us compliant.

Back to Bug 1785941 Comment 0