Add Simple Accessibility (Sa11y) QA tool to GovCMS

[ihacpa]

GovCMS Module Request

Please provide the Drupal.org URL for the module
https://www.drupal.org/project/sa11y

What value does this module/package add to GovCMS?

• compliance with the AGA content management policy requirements: Align business, operational, and technological needs; Adhere to reuse principles.
• compliance with WCAG standards and Digital Inclusion Standard crit 4 Make It Accessible.
• support it's mission to create and host websites and digital services which are secure, scalable, and accessible.
• provide its 115+ clients / 350+ websites an efficient and inclusive method of assessing and meeting the mandatory standards.

Is the module Drupal 11 compatible?
Yes

Please provide a brief outline of what this module does.
Sa11y is an accessibility quality assurance assistant that visually highlights common accessibility and usability issues. It acts as an in-page accessibility checker that identifies and offers fixes for 80+ developer and content issues in line with WCAG standards.
It allows content editors to to deftly and expertly identify accessibility issues at the source, including build capacity and confidence for those new to the space.
While the existing guidance suggests tools like Monsido and SiteImprove, these may be suitable for high volume/impact websites but do not consider the needs and limitations of small-medium agencies who would benefit from a simple, powerful and free tool such as Sa11y.

Who does this module benefit:
[X] end users
[X] content editors
[ ] site builders
[ ] themers
[ ] developers
[X] website owners <-- new

How could you provide/replicate the functionality of this module using alternative methods, eg in your theme?
The current process is to use third party tools such as Word and Acrobat. While these are capable of performing some accessibility content checks (ie. presence of alt text, headings and structure, readability, tables), other critical content checks are missed (semantics, links, quality of alt text, colour and contrast, embedded content).
Further, they do not consider developer checks (page structure and meta tags, buttons, inputs, hidden focusable elements) - these checks need to be done manually.
Another key limitation of this method is that issues can occur during content population. Having an integrated in-platform tool will deliver greater efficiency and WCAG compliance assurance for content editors.

If this module styles or alters HTML or JavaScript output, can the functionality be provided via the theme? What alternatives have you considered.
Sa11y does not alter the original HTML source code or JavaScript output of a website. As a client-side tool, it reads the DOM, highlights issues with CSS, and injects tooltips, but acts as a passive inspector, not a content management system (CMS) editor. It is designed to visually flag issues in the browser for content authors, there are no code changes.

What is the maintenance and support status of the module. Describe the issue queue activity.
It is currently maintained. There are 3 active issues.

What permissions are needed to utilise the module (and are any new permissions provided by the module)?
Specified user roles to enable the widget while using the site.

Does the module modify the database structure and/or store additional metadata on nodes or other entities? If so, why? What are the risks for future updates?
As a client-side, JavaScript-based accessibility tool it does not modify the database structure or store data on a server. As a client-side plugin, it operates entirely within the browser, using only local web storage to manage user preferences, such as enabling optional rulesets.
No risks identified.

Is the module designed to capture anonymous user data?
It scans for content issues, allowing for CSV/HTML export of reports. These results are not stored on the server. It does not collect personal data.

Is the output of the module typically fully cacheable? Would the inclusion of this module potentially render pages uncacheable.
As far as I can see, it is designed to run in real-time as an in-page, editor-facing tool and generally not designed to be fully cached for end-users. It does not interfere with server-side caching mechanisms so there shouldn't be any risk of rendering pages uncacheable. As it doesn't collect personal data, tracking, or use third-party content this should eliminate any overhead that might typically disrupt caching.

What is your assessment of the quality of this module, the contribution history of the module's maintainers, and the uptake of the module within the Drupal community?
None identified through my desktop research. I welcome all feedback and contributions.

Additional information
In the spirit of the Digital Service Standard crit 6 Don't reinvent the wheel, your clients are required to build once, use many times and design for a common, seamless experience!
Similar to the resources and guardrails offered by the AGA for creating digital solutions, GovCMS in its capacity as Aus gov website host extraordinaire might consider endorsing an accessibility checker module such as Sa11y and support agencies to efficiently and confidently deliver performance, accessibility and usability capabilities that are consistent, interoperable, reduce risk, maximise value for government and a provide a quality experience for users.

Thanks in advance for your consideration.