Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update and Reformat Page: Request support from the VA Section 508 Office #99495

Open
7 tasks
jknipes opened this issue Dec 19, 2024 · 0 comments
Open
7 tasks
Labels

Comments

@jknipes
Copy link
Contributor

jknipes commented Dec 19, 2024

Pain Point

The page Request support from the VA Section 508 Office has many formatting errors. It was last updated in February 2024.

Issue Description

Per a recent Slack discussion among our team, the following points were raised:

this page could use work in, at least, the following areas:

  • Page needs a Date Stamp.
  • This page doesn't have an intro that provides context to the user. It defines the product but doesn't contextualize the information on the page.
  • This page is not very well formatted. The processes and steps could be labeled and formatted more clearly.
  • There are too many #1s and letter "A's" and sub-steps within steps within steps. It is a Russian Nesting Doll of steps and could be formatted much more clearly, imo.
  • There is a lack of continuity on the page. The "Audit Request" section provides screen captures but the "Document Review" section does not...
  • And even within the Audit Request section: Why do some steps get screen captures and others do not?
  • Why are those screen captures so small, were they taken in 1998?
  • Why does there appear to be a line-break in the captions?
  • Would a video of someone filling out this form be a better, clearer way to pass this info onto the user? (just a thought)
  • And finally, for some reason there are two divider lines at the end of the doc with a large space between then (see pic). That needs to get fixed too.
  • What does the page author mean by "Platform?" Page say Doc review is "out of scope" for "Platform." That type of wording is precisely the type of wording that leads to confusion about the Platform website vs. the Platform contract, vs. VA platform, and a generic product platform.
  • Lastly: the final section of the page is titled "after your request" -- does this info apply only to the Audit section? or does it apply to the Doc section as well? Re-wording this subheading title would help clarify things for the user.
  • The steps formatting in the "Document review" and "Audit request" sections is inconsistent. Some are bolded in quotation marks, while others are not, which looks confusing. This needs to be reformatted so the whole document has consistency and a clear structure.

Tasks

  • Make changes according to Description

Acceptance Criteria

  • tasks completed

How to configure this issue

  • Attached to a Milestone (when will this be completed?)
  • Attached to an Epic (what body of work is this a part of?)
  • Labeled with Team (product support, analytics-insights, operations, service-design, Console-Services, tools-fe)
  • Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
  • Labeled with Type (bug, request, discovery, documentation, etc.)
@jknipes jknipes added the needs-refinement Identifies tickets that need to be refined label Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant