Publish Accessibility Conformance Report for LocalGov Core and Microsites

[msayoung]

[msayoung]

In discussion with @FrazerGNom and Nomensa about the best route towards this.

In summary, we'll probably produce an Accessibility Conformance Report linking to open issues in Github.

More detail coming soon.

[willguv]

Nomensa will provide reports sometime around Global Awareness Day

[willguv]

@msayoung heard anything from Gain? Thanks

[willguv]

@msayoung shared that Gain has scheduled this work for August

[msayoung]

Mike Gifford has pointed me to a few tools resources which we should consider

• https://github.com/CivicActions/Drupal-ACR
• https://github.com/mgifford/github-scanner

He's also recommended that we publish our ACR in an OpenARC format. https://acreditor.section508.gov/

As I understand it, this is a version of the report in a machine readable and HTML format (as opposed to a PDF) .

The idea would be that it references our issue queue, so we have transparency and accountability for the issues that need fixed.

The tools above do the following

Drupal ACR

• Extracts issues from Drupal.org
• Generates AI summaries (using Gemini)
• Uses AI to write a report
• Converts it to OpenACR format

Github Scanner

The second script generates a csv for issues in github (as we aren't on drupal.org yet).

We do still have the task of manually tagging the issues with success criteria, which is not insignificant. We may be able to get AI to help with this.

[willguv]

@msayoung said Gain promised work by the next governance meet (mid September)

[willguv]

Will be covered at 24th September accessibility group

[msayoung]

All the github issues are going to be migrated to D.O , so we'll need to consider that in the plan . We may be blocked until that's the happen.