search

department-of-veterans-affairs / va.gov-team

Public resources for building on and in support of VA.gov. Visit complete Knowledge Hub:
https://depo-platform-documentation.scrollhelp.site/index.html
281 stars 202 forks source link

[a11y Documentation] Platform Website: Modernized VA.gov Accessibility Strategy Page Updates #82918

Open sara-amanda opened 5 months ago

sara-amanda commented 5 months ago

CAIA A11y Support

[!TIP] DEFINITION OF DONE: Refer to the task list in this ticket, for actionable items.

Menu Selection

Work necessary for this ticket to be completed (select all that apply):

CAIA Assignee(s)

Team Info

Toggle to view team info - **Team name:** `Team name` - **OCTO product owner:** `OCTO product owner` - **Product name:** `Product name` - **Product manager:** `Product manager` - **Slack channel:** `Slack channel w/ link` - **Dedicated content writer on your team (if you have one):** `writer` - **Dedicated a11y specialist on your team (if you have one):** `a11y`

Description

I came across this page on the Platform site, which prompted me to send the following, since some items have seen progress as of late..

Details

What details are necessary for understanding the specific work or request tracked by this issue?

Toggle to view the description details ### No. 3 - Currently Reads #### ❌ Question 3. All product teams have the needed space, time, knowledge, and power to embed accessibility as part of their key responsibilities. **Problem this is meant to solve:** - Accessibility resources are currently scattered across VA.gov with little to no maintenance or organization. - Some teams don’t know where to get accessibility guidance, who to reach out to, etc. - Some teams may not be aware that accessibility is a part of their key responsibilities when launching products. (They may also be unaware of what those specific responsibilities are.) - Accessibility is not (yet) an organized practice. It is currently a loosely organized group of specialists collaborating on Slack. ### Update No. 3 **_❓ Can we update this since We Are Making Strides?_** #### Question 3. All product teams have the needed space, time, knowledge, and power to embed accessibility as part of their key responsibilities. `Can we instead show progress in this section? How it started? How it's going?` **Problem this is meant to solve:** - Accessibility resources are currently scattered across VA.gov with little to no maintenance or organization. - `We have the new landing page we could link to here to show progress towards this initiative? ` - Some teams don’t know where to get accessibility guidance, who to reach out to, etc. - `We have the plugs in TOT, the Slack handles, and Platform Governance CAIA Ticket Prompts, etc. Can we show progress towards this initiative in this section? ` - Some teams may not be aware that accessibility is a part of their key responsibilities when launching products. (They may also be unaware of what those specific responsibilities are.) - `This is shifting too. Brian told Naomi M. that he is finding less issues, which means our involvement is making a difference. Can we point to this progress here too, perhaps?` - Accessibility is not (yet) an organized practice. It is currently a loosely organized group of specialists collaborating on Slack. - `Is the needle moving here? What is a "firmly" organized group vs. a "loosely" organized group? `

Formatting (Optional)

Toggle to grab additional highlights to use in this ticket Formatting will contain colors when not enclosed in a toggle. > [!NOTE] > Highlights information that users should take into account, even when skimming. > [!TIP] > Optional information to help a user be more successful. > [!IMPORTANT] > Crucial information necessary for users to succeed. > [!WARNING] > Critical content demanding immediate user attention due to potential risks. > [!CAUTION] > Negative potential consequences of an action.

Definition of Done

### A11y Tasks
- [x] Internal request to OCTO on `5/13/2024`
- [x] Martha provided feedback `5/13/2024`
- [x] Run metrics exercise with wider a11y CoP to brainstorm
- [ ] Generate content to update the page
- [ ] Look into migrating to the DST per Martha
- [ ] Decision re: DST Migration for this page `TBD`
## Ticket Updates (CAIA Internal)
- [x] _Connect to an `Epic` or `Intake` (what body of work is this a part of?)_
- [x] _Label with `Originator/Team` (product team or stakeholder requesting support)_
- [x] _Label date in the `Open Date` field_
- [x] _Label with `Estimate` (level of effort expected for this ticket)_
- [x] _Add `Assignee(s)` name(s) to ticket_
- [x] _Add `Assignee(s) name(s) to each task` they will complete via handle tag (if known)_ 
- [x] _Select a `Priority Level`_
- [x] _Update date in `Last Checked` field_
- [ ] _Label with `Actual` (level of effort it took to complete this ticket)_
- [ ] _Update date in `Closed  Date`_
sara-amanda commented 5 months ago

Slack Update

Per @artsymartha68 via Slack on 5/13/2024 this may move to the DST site per conversations with Matt D.

cc: @coforma-jamie @coforma-terry

coforma-jamie commented 5 months ago

Structure

My thought is to organize the page by topic, and not by type of item (i.e. "Metric" or "Strategy"). That way, staff will know exactly what we're trying to accomplish and how we're trying to do it.

A structure could look something like this:

We could include a status of some sort on each strategy? Metric? Not sure.

Fundamental questions

Before we do this work, I think we need to answer some fundamental questions:

  1. What Metrics are related to what Strategies?
  2. Are any of the Metrics being monitored? How? Who has access to that info? Are we actively tracking these?
  3. Have we made any progress on Strategies 1, 2, and 4?
coforma-jamie commented 1 week ago

I ran a metrics exercise with the wider accessibility community of practice on 10/3/24 to solicit the group's "dream metrics," and how they fit into our broader strategies at VA.

@artsymartha68 is going to use the results of the exercise to help her craft a new accessibility goals document.