Skip to content

SPIKE - investigate VPAT accessibility comments and provide solutions #1694

@mkdir-washington-edu

Description

@mkdir-washington-edu

We're about to receive our 2026 VPAT from our partners (Inclusive Design Research Centre (IDRC)) who help us assess our accessibility every year. See: https://web.hypothes.is/accessibility/.

Here's last year's VPAT.
And our response document. The response doc links out to github issues where we proposed solutions to the issues raised by the IDRC. You can see how we approached the issues where we were marked as "Partially Supports", and the approaches we took to fixing those issues.

Commonly when we get a new VPAT we review it as a team, identify fixes for any "partially supports" items (we've never had a "doesn't support" item, but we would prioritize those first if we did), and attempt to roll those fixes out quickly. We have an unspecified, but short, amount of time to ask the IDRC to re-review our app in light of fixes, which can help us get a better review.

In 2026 many of our school partners are going to be more stringent than they have in the past with regards to accessibility. We have always done an excellent job with accessibility and creating a new batch of fixes, if needed, will be high priority for us.

Once we get our new 2026 VPAT from the IDRC I'll add a link to it in the comments.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions