Re: Buttons out of context

So follwing on from this I have the following statement:@

<button>Download</button>

<button>Download</button>

<button>Download</button>

These fail 2.4.6 as they are not descriptive (in context or out of context).



Let's add to the visible label:

maths papers <button>Download</button>

geography papers <button>Download</button>

physics papers <button>Download</button>



The visible labels here are:

Maths papers Download

Geography papers Download

Physics papers Download

The labels are now descriptive, so they do not fail 2.4.6. However, the labels are not programmatically associated, so they are not clear ‘out of context’.



This is where 1.3.1 comes in. These now fail 1.3.1 as there are visible associations which are not programmatically determinable.



This is why it says 2.4.6 needs to be used in conjunction with 1.3.1, (where labels are programmatically associated), for the labels to be clear out of context:



<button> maths papers Download</button>

<button> geography papers Download</button>

<button> physics papers Download</button>



________________________________
From: Tom Shaw <tom-shaw@hotmail.com>
Sent: 17 November 2022 11:16
To: w3c-wai-ig@w3.org <w3c-wai-ig@w3.org>
Subject: Buttons out of context

Hi all.

I'd like to quickly discuss button and specifically out of context. I quote the following from WCAG 2.4.6

"When headings and labels are also correctly marked up and identified in accordance with 1.3.1: Info and Relationships<https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships>, this Success Criterion helps people who use screen readers by ensuring that labels and headings are meaningful when read out of context, for example, in an automatically generated list of headings/table of contents, or when jumping from heading to heading within a page."


maths papers
<button>Download</button>

geography papers
<button>Download</button>

physics papers
<button>Download</button>

So, what I'm reading from that is that it fails 2.4.6, but is there an argument that this may also fail 1.3.1, too? As the visible labels that help you identify the purpose of the fields are not programmatically associated?

As always thank you for your time I appreciate it!

Tom

(I will provide more context for my previous link issue later today) 🙂