WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Starting my first accessibility testing

for

From:
Date: Sep 12, 2020 1:45AM

Hello Jared,

Thank you for your reply.

I followed up your recommendation to press on a code link to see the code.

But I have a question.

First, I need to say that i am an absolute beginner in q/a testing and I
decided to focus on accessibility, so my questions will be obvious.

As far as I understood to check what accessibility issues were found I
have to go to the details tab and there I can browse the errors by
categories.

I can find the error, an image of the error, it's explanation.

But what should I do next? What information do I need to pass about that
to the development team?

Do I understand right that when I am reporting a bug about accessibility
issue I have to look at the markup to tell the correct information?

When I look at the markup I see the whole code of the page.

How can I tell that way about the one concreet issue?

Thank you in advance.

--

Best regards,

Vsievolod


11.09.2020 16:50, Jared Smith пишет:
> Vsievolod -
>
> The WAVE presentation is highly visual with accessibility feedback injected into the existing web page layout via icons. Each WAVE icon has descriptive alternative text and describes an issue relevant to a page element either immediately before or after the WAVE icon. WAVE cannot fix the accessibility issues that are present, so sometimes the page inaccessibility makes it more difficult to explore the results, especially for pages that are very complex or have many accessibility issues.
>
> The WAVE sidebar provides an overview of the numbers and types of items that have been identified. There's also a "Code" button after the page (it's also defined as a landmark/region) that will open a code panel that presents the WAVE icons in conjunction with the relevant code.
>
> We'll be releasing a new update in the coming days that has a few accessibility enhancement, but WAVE can admittedly be a bit complex for anyone on some pages due to the page complexity and the number of accessibility items identified. We're very open to recommendations for improvement.
>
> Thanks,
>
> Jared
>
>
> > > >