WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: priority accessibility issues

for

From: glen walker
Date: Apr 13, 2022 8:08AM

I think that might be too broad of a question although some generalities I
follow are:

high - blocker type issues, a user can't accomplish a task
med - non-blocking but still frustrating but a workaround might exist
low - technical wcag failure but might not have too adverse of an effect

A high bug might be an image button that doesn't have alt text or a label
so the user doesn't know what the button does, or an interactive element
that does not allow keyboard selection.
A medium bug might be an inconsistent or missing heading structure.
A low bug might be a color contrast of 4.4:1, just below the minimum.

I have been playing with a format that has high and medium as true WCAG
failures and then using low for UX bugs that don't fail WCAG but still
cause problems for users. For example, a "learn more" link that is
embedded in a paragraph with its context technically passes 2.4.4 but I
recommend making the link text make sense on its own (2.4.9). If there are
multiple links in a row that go to the same destination, I recommend
combining the links or "unlinking" some of the text if it's appropriate.
If there's a character in button label that is decorative but it's still
announced, such as a greater than sign, it doesn't make the button unusable
but sounds a little funny.


On Wed, Apr 13, 2022 at 7:49 AM Nathan Clark < <EMAIL REMOVED> >
wrote:

> Dear list,
> When doing accessibility audit on a website, what do you all consider
> to be low, medium or high priority accessibility bugs?
>
> Thanks.
> Sincerely,
> Nathan Clark
>
> --
> Nathan Clark
> QA Automation Analyst Tech team
> Accessibility assistant
> CPACC
> cell: 410-446-7259
> email: <EMAIL REMOVED>
> 101 Village Blvd
> Princeton, NJ 08540
> SMBE & Minority Owned Business
>
> --
>
>
>
> > > > >