Disable irrelevant sections for the user

GSA / openacr

OpenACR is a digital native Accessibility Conformance Report (ACR). The initial development is based on Section 508 requirements. The main goal is to be able to compare the accessibility claims of digital products and services. A structured, self-validated, machine-readable documentation will provide for this.

https://gsa.github.io/openacr/

Other

83 stars 18 forks source link

Disable irrelevant sections for the user #265

Closed danid123 closed 2 years ago

danid123 commented 2 years ago

[x] Add checkboxes in About to disable which sections the user needs to fill out.
[x] When checked the fields on those pages are disabled but the user can still fill out notes at the top.
[x] The user is shown the disable/enable checkbox on the page as well and they can uncheck it to re-enable the fields.
[x] On the report page any disabled sections will have the tables be hidden from the HTML but still show the title and any notes.
[x] Add copy in the About that explains this is what is happening.

Separate ticket for "Add a bullet point to the Overview that explains that we will disable sections based on how the user answers."

mgifford commented 2 years ago

This might look like this:

WCAG ACR elements

ACR elements

danid123 commented 2 years ago

The labels should match the navigation labels/page headings:

[ ] Web
- [ ] A
- [ ] AA
- [ ] AAA
[ ] Functional Performance Criteria (FPC)
[ ] Hardware
[ ] Software
[ ] Support Documentation and Services

Can the A levels only show appear once Web is selected?

mgifford commented 2 years ago

I'm actually wondering if we should build it so that web is the only check box. A & AA will always be required with web. There is no ACR right that I know of that is looking for single A. AAA is always just optional, but I don't know if we should bother enabling/disabling it.

[ ] Web (A, AA and AAA)
[ ] Functional Performance Criteria (FPC)
[ ] Hardware
[ ] Software
[ ] Support Documentation and Services

dmundra commented 2 years ago

My two cents here is that these changes are going to be significant work to implement. I think once you have a desired approach then we can either create a new issue for implementation or move this issue to the sprint where we want to implement this. I don't we can accomplish the changes in this sprint.

dmundra commented 2 years ago

Made on progress on this. Created a storage place to track the values of the checkboxes separate from the OpenACR evaluation.

dmundra commented 2 years ago

@danid123 and @mgifford I need a review of the help text I added and then new text for the overview page. I can also create a separate ticket if that is better.

dmundra commented 2 years ago

Thanks @danid123 closing this ticket as a new one will focus on content.