Spike: UX improvements - Githubissues

Extended Description As a user, I would like an attractive and friendly user interface.

Pursue multiple avenues to improve UX as part of a time-boxed spike.

Acceptance Critera

[x] Tasks, below, considered
[x] Follow-up tickets created

Story Tasks

These are ideas to consider - implement, discard, or create follow-up tickets:

[x] Counts on radio button filters
[x] Style assertion messages better - code blocks or links? See: #226
[x] Clarity that on rule status - unprocessed, loading, error, processed
[x] Add labels to radio buttons
[x] Nested tree view for all assertion content. See: #226
[ ] ~Style details/summary `::marker'~
[x] Line number in XML source code view. See: #227
[x] Consider tagging assertion diagnostic messages for presentation. NOTE: considered, but path forward not determined
[x] Sticky filter form on top of page
[ ] ~Drop down for roles filter~

Definition of Done

[x] Acceptance criteria met - Each user story should meet the acceptance criteria in the description
[x] Unit test coverage of our code > 90% (from QASP) this may be fuzzy and hard to prove
[x] Code quality checks passed (from QASP)
[x] Accessibility: (from QASP) as we create guidance or documentation and reports (semantic tagging including aria tags): demonstrate with 0 errors reported for WCAG 2.1 AA standards using an automated scanner and 0 errors reported in manual testing
[x] Code reviewed - Code reviewed by at least one other team members (or developed by a pair)
[x] Source code merged - Code that’s demoed must be in source control and merged
[x] Code must successfully build and deploy into staging environment (from QASP): this may evolve from xslt sh pipline into something more
[ ] ~Security reviewed and reported - Conduct vulnerability and compliance scanning. threat modeling?~
[x] Code submitted must be free of medium- and high-level static and dynamic security vulnerabilities (from QASP)
[ ] ~Usability tests passed - Each user story should be easy to use by target users (development community? FedRAMP FART team)~
[x] Usability testing and other user research methods must be conducted at regular intervals throughout the development process (not just at the beginning or end). (from QASP)
[x] Code refactored for clarity - Code must be clean, self-documenting
[x] No local design debt
[ ] ~Load/performance tests passed - test data needed - saxon instrumentation~
[ ] ~Documentation generated - update readme or contributing markdown as necessary.~
[ ] ~Architectural Decision Record completed as necessary for significant design choices~

18F / fedramp-automation

Spike: UX improvements #216