Accessibility Statement for mySidewalk Shared Documents

mySidewalk Inc. is committed to ensuring digital accessibility for people with disabilities. Our Shared Documents - including Reports, Dashboards, and Embeddable Assets all in their shared, reading friendly formats - have the widest audience. We are continually improving the user experience for everyone, and applying relevant accessibility standards.

Measures To Support Accessibility

mySidewalk Inc. takes the following measures to ensure accessibility of mySidewalk Shared Documents:

  • Provide continual accessibility training for our staff.

  • Assign clear accessibility targets and responsibilities.

  • Employ formal accessibility quality assurance methods.

  • Communicate the results of accessibility audits and evaluations for transparency.

Conformance Status

The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. mySidewalk Shared Documents is fully conformant with WCAG 2.0 level AA. Fully conformant means that the content fully conforms to the accessibility standard without any exceptions.

Feedback

We welcome your feedback on the accessibility of mySidewalk Shared Documents. Please let us know if you encounter barriers:

  • E-mail: [email protected]

  • Postal address: 304 W 8th St, Kansas City, MO 64105

  • Twitter: @mySidewalkHQ

Technical Specifications

Accessibility of mySidewalk Shared Documents relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:

  • HTML

  • WAI-ARIA

  • CSS

  • JavaScript

These technologies are relied upon for conformance with the accessibility standards used.

Limitations And Alternatives

Despite our best efforts to ensure accessibility of mySidewalk Shared Documents, there may be some limitations. Below is a description of known limitations, and potential solutions. Please contact us if you observe an issue not listed below.

Known limitations:

  1. Inline Data Tables provided by FancyGrid: Aria role attributes are not properly applied to the cells of the FancyGrid table. The table can be downloaded as a CSV or Excel and includes an accessibility description. We rely on a complex third party component with functions closer to "software" than a "website" for this content but are working with the third party developer to improve the accessibility features of the Inline Data Tables provided by FancyGrid. Please use the download buttons directly beneath the table for more direct use of the data.

Assessment Approach

mySidewalk Inc. assessed the accessibility of mySidewalk Shared Documents using the following:

  • Self-evaluation

  • Automated evaluation: pa11y

  • Automated evaluation: lighthouse

  • Automated evaluation: WAVE

Evaluation Report

In order to evaluate the accessibility of mySidewalk, Inc’s Shared Documents, we assembled a document with every possible component configuration in every possible organization/navigation configuration. This is a three page document with ~20 component configurations in 4 organization/navigation configurations. Linked below are relevant automated audits of this representative Shared Document along with descriptions of the results.

  • Lighthouse Automated Reports - Perfect scores on all configurations, including optional suggestions

  • Pa11y Automated Reports - 3 false positives

    • 1 false positive for an inactive internal chat tool

    • 1 false positive error per chart regarding a reference to a missing element
      Third party library includes a link to an optional data table that is not created until clicked. This is a desired optimization with less overhead for the client browser.

    • 1 false positive error per chart regarding missing text in a heading
      Third party library includes a heading with no text. The element is visually hidden and has appropriate text for accessibility devices only. Pa11y has a different interpretation than the third-party library of WCAG 2.0 Guideline Principle 1 Guideline 3.1.

This statement was created on 21 February 2019 and updated on 16 May 2019.