Map Andi to WCAG

[wbpagenewbie]

I love Andi and find it helpful, however, new Developers and Testers like how WAVE provides the error, alert, and warning, and provides the WCAG Succes Criterion (SC). Are there plans to display or provide the SC for each issue found when using ANDI?

Thank you for your consideration. I am just trying my best to get them to make things 508 compliant.

[JohnCotterSSA]

ANDI fills a niche in that it is designed to be agonistic to an organization’s test method.

From the ANDI team's perspective, WCAG mappings should be done at the test method or checklist level. It is up to the tester (the ANDI user) to determine if an ANDI alert is truly an accessibility problem, and which WCAG guideline the problem fails.

For now, the need for flexibility to organizations outweighs the convenience factor a tester might gain with WCAG mappings. Put another way, we find that tools that do provide WCAG mappings, confuse our testers since the reported mappings often conflict with our own test method and checklist.

Part of the reason ANDI is successful with experienced testers like you and users who are new to accessibility testing is that its interface is simple and doesn't refer to complex WCAG guidelines. As I'm sure you know, WCAG is very complex, and there is a lot of "fine print" one must read to fully understand every nuance of the guideline. ANDI tries to make manual accessibility testing as easy as possible and tries to explain issues and present solutions in simple terms.

[seattleguitarman]

Well said, John. I use ANDI, WAVE, NVDA screen reader and manual testing all to compliment each other. I've recently shown ANDI to a lawyer with the Office for Civil Rights as she had been using a set of other bookmarklets so she'd have another tool to add to her toolkit in explaining things to higher education institutions like the ones I have worked for. Doug Hayman

…

________________________________ From: John Cotter ***@***.***> Sent: Wednesday, June 7, 2023 8:23 AM To: SSAgov/ANDI ***@***.***> Cc: Subscribed ***@***.***> Subject: Re: [SSAgov/ANDI] Map Andi to WCAG (Issue #207) ANDI fills a niche in that it is designed to be agonistic to an organization’s test method. From the ANDI team's perspective, WCAG mappings should be done at the test method or checklist level. It is up to the tester (the ANDI user) to determine if an ANDI alert is truly an accessibility problem, and which WCAG guideline the problem fails. For now, the need for flexibility to organizations outweighs the convenience factor a tester might gain with WCAG mappings. Put another way, we find that tools that do provide WCAG mappings, confuse our testers since the reported mappings often conflict with our own test method and checklist. Part of the reason ANDI is successful with experienced testers like you and users who are new to accessibility testing is that its interface is simple and doesn't refer to complex WCAG guidelines. As I'm sure you know, WCAG is very complex, and there is a lot of "fine print" one must read to fully understand every nuance of the guideline. ANDI tries to make manual accessibility testing as easy as possible and tries to explain issues and present solutions in simple terms. — Reply to this email directly, view it on GitHub<#207 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQTKK75U3DE2LUWNA3JJGGDXKCMHFANCNFSM6AAAAAAY5BTXCY>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[wbpagenewbie]

John,
Thank you so much for your response. I was hoping this would be the answer, as I believe ANDI helps people learn and understand WCAG SC much better than WAVE. I can use your response to help support my recommendations.