V2 Screen Reader Spec Validation

[bbertucc]

Posting @azdak's comments and my replies:

Step 1: Adding pages: on initial screen, unclear if we're adding a single page or an entire site. Adding pages is core to the product and needs to be integrated

Done: https://equalifyeverything.github.io/equalify-v2/1-home.html

Step 2: No way to see what pages are included in Audit

You can group by pages on the audit.

Q: what is the distinction between "active" and "qualified"?

I don't see "qualified". But "Equalified" basically means fixed. The reason it is branded that way is because fixing an issue in the accessibility space can mean lots of things. We qualify fixes by saying they're "Equalified". "Active" is not fixed. No users have been confused on the meaning of this, so I don't think it needs to be spelled out further.

Q: What are the use cases for sorting by Equalified Items (Most to Least), Equalified Items (Least to Most), Ignored Items (Most to Least), Ignored Items (Least to Most)

Good point. Removed: https://equalifyeverything.github.io/equalify-v2/3-audit_details-ran.html?

It says "All Page Items" but is it actually related to a page, we're on the audit screen, no?

Only if you're grouping by page.

Step 5: Group by Page groups/rows appear to be headed by html page title? We don't currently have that in the system, it would have to be added, and even then would only work after an initial scan

This was a requested feature, so I'm just going to leave it in the mockup for now. The mockup does show it appearing after the scan.

Step 6: Axe-core Checks and Editorially sections should probably have a "select all" option for each

Done: https://equalifyeverything.github.io/equalify-v2/7-audit_editor.html

Considering we anticipate like large numbers of pages being added, I think we're going to need a more robust treatment for selecting/adding pages (also like there's no way to add URLs). Also feel like pages section should go first on this screen?

Done: https://equalifyeverything.github.io/equalify-v2/7-audit_editor.html

Step 10: Is there no way to actually just execute an audit on this screen?

I err on the side of simplicity. If folks complain, we can add I guess.

Step 13: It seems like "View options saved." could be a good bit more verbose, and just for simplicity sake should be the same as what's logged?

Made the view options more verbose, but saving view options isn't a log item: https://equalifyeverything.github.io/equalify-v2/15-audit_details-tagged.html

AI assistant button is non-functional (and unclear on what it'd do if it was)

Replaced it with a "Generate Ticket" button: https://equalifyeverything.github.io/equalify-v2/6-audit_details-page_groups.html

Missing menu items: Home and Account are the only menu items. Pages, Audits, and Logs(?) should all be in the header. In general this comp feels optimized for a single, very particular use case, with less thought given to general or day-to-day use

Folks can group by page/issue to see page/issue content. I can't imagine a use case when they need to look at all logs. Logs need to review when an audit does something weird. Like "why is that issue ignored?"

Bigger picture, as a functional comp it feels very maze-y right now, and doesn't work at all if steps are not taken in exactly the correct order. I feel like this may cause problems for even simple testing/review

Updated the README to focus on the fact that this is a guided demo. It would be a pain in the ass to make all links clickable and keep content with continuity. Plus, at this point it's good to hear exactly what people are thinking: https://equalifyeverything.github.io/equalify-v2/

[bbertucc]

@azdak do you see any new red flags from my updates/comments? Your final sanity check is appreciated before we take it to the next step.