RE: Buttons out of context

Sounds like a pretty poor design in the first instance and cobbled together by an indifferent developer or a rubbish software package by my reckoning … if I understand your example correctly, there is a heading and a button an no other content … 

 

at the risk of revisiting a well worn topic, is a control that is programmatically a button the right control for allowing the download of a linked resource? Isn’t this what hyperlinks were intended for? 

 

I’d recommend replacing both the heading and button with a hyperlink and possibly even indicate in the screen text what type of resource is linked to (assuming that it is not a web page).

 

The issue is likely that your input is being sought after the fact and once something has been built rather than in design … 

 

 

 

From: Tom Shaw <tom-shaw@hotmail.com> 
Sent: Thursday, November 17, 2022 10:17 PM
To: 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) 🙂