Re: 1.3.1

Indeed, the progressive enhancement pattern we all worked hard towards seems to have fallen by the wayside.

Semantic HTML to provide meaning
ARIA to add support for AT where required
CSS to enhance presentation
JS to add functional interaction

Unfortunately ARIA is used as a backstop for when Accessibility is an afterthought.
________________________________
From: David Woolley <forums@david-woolley.me.uk>
Sent: 25 April 2025 15:11
To: w3c-wai-ig@w3.org <w3c-wai-ig@w3.org>
Subject: Re: 1.3.1

On 25/04/2025 11:29, Ms J wrote:
> For example, if parts of the page have been marked up with list mark up
> that aren't lists.

Unfortunately that cause was probably lost two decades ago.  The way
that people, trying for compliance, now do it is to use ARIA to provide
the true semantics, and HTML and CSS, to achieve the visual result they
want.

Personally, I like the idea that you start with semantic HTML, then
define a house style, in CSS, but I think most web page designers go for
the visual appearance, with any tool available, and then add ARIA to
pass the accessibility audit.  In many cases it is actually the tools
they are using those, based on standard formats.

I think your proposed wording is changing the meaning, rather than
clarifying it.


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________