Select to view content in your preferred language

Allow Administrators to Enforce Accessibility Requirements for ArcGIS Online Applications

258
2
4 weeks ago
Status: Open
BrandonBackman
Occasional Contributor

ArcGIS Online currently does not provide a way for administrators to define or enforce accessibility standards for applications published within their organization.

This can lead to inconsistent accessibility across applications and creates risk when sharing content with groups, the organization, or the public.

Proposed enhancement:

Allow administrators to configure accessibility requirements for applications created and published through ArcGIS Online tools such as StoryMaps, Dashboards, Experience Builder, and Instant Apps.

Administrative settings could include:

  • Defining minimum accessibility thresholds (such as WCAG A, AA, or AAA levels, or a platform-defined score)
  • Requiring that accessibility checks be completed prior to publishing
  • Restricting sharing (for example, to organization or public) if accessibility requirements are not met
  • Providing administrators with visibility into accessibility status across applications, possibly through an organizational dashboard

To support real-world workflows, administrators should also have the ability to override restrictions when necessary, such as in cases of false positives or when accessibility has been verified through manual review.

This capability would enable organizations to establish and maintain consistent accessibility standards, reduce legal and compliance risk, and ensure that publicly shared content meets defined accessibility expectations.

Together with an automated accessibility checker, this would create a scalable, platform-level approach to improving accessibility across ArcGIS applications.

2 Comments
MichaelVolz

Brandon - Do you know of any automated accessibility checkers?

BrandonBackman

@MichaelVolz So far, I’ve primarily used tools like Lighthouse in a manual capacity, but there are established options for integrating it into automated workflows:
https://developer.chrome.com/docs/lighthouse/overview

I don’t have direct hands-on experience implementing it in an automated pipeline yet, but tools like IBM Equal Access Accessibility Checker are also designed to support automated testing scenarios:
https://www.ibm.com/able/toolkit/verify/automated/

Additionally, there are several axe-core-based solutions that can be incorporated into automated workflows as well.

Edit - there's another idea I submitted specifically about building the automated checkers into various publishing workflows. This idea was focused on general administrative controls that could be in place to improve accessibility and could theoretically be enhanced by automated checkers.