WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Descriptive label for Read more button

for

From: Sumit Patel
Date: Apr 25, 2023 12:06AM

Thanks for your response.

But, is it somethikg which need to be marked as a failure ?
Because I feel the impact or the importance is really less as the
name of the person here is not at all important .
We'll choose whether we need to read more or not based on the visible
part of the review content.
The name here does not influence the user anyhow to do that .

If the persons were someone who is established in this field and their
name has the ability to influence the user to read the complete
review, then I think the name is important.

Else, it might be a good practice, not a failure.

This is just my perception. I am just seeing how much important their
names or what benefit the screen reader user gets if the name gets
associated


On 25/04/2023, glen walker < <EMAIL REMOVED> > wrote:
> The issue Lisa mentioned would be covered under 2.5.3. If the visible
> label says "read more" but the aria-label is "read more about this review",
> then 2.5.3 is satisfied and a voice interface should allow "click read
> more" (although it'll highlight all the "read more" links).
>
> But I don't see "read more" as any more descriptive than "read more about
> this review". I still don't know which review I'm reading more about so I
> would still fail 2.4.4 (if it's a link) or 2.4.6 (if it's a button).
>
> Reviews often have the person's name, as you mentioned, and might include a
> short title for the review. Either one of those should be associated with
> the "read more". I like to use aria-labelled by rather than
> aria-describedby so that if the screen reader user brings up a list of
> links or a list of buttons, the context of the "read more" will appear in
> that dialog. Accessible descriptions aren't shown in those dialogs. But
> that's just my personal preference.
> > > > >