Re: progresive enhancement, and wcag guides?

Hi Karen,

WCAG does not demand progressive enhancement. It’s not important how you meet a success criterion.

You can use native interactive HTML elements (like buttons or links) elements or a div and use complex techniques to make it behave like a button.

In most cases it makes more sense to use a working wheel instead of reinventing it…

Also WCAg is not only for blind people. If you get information, that obviously wrong, try to read the guideline yourself. It’s not really a lot of text, but sometimes hard to understand. 

The understanding documents can help. 

--
Mit freundlichen Grüßen

Marc Haunschild - he / him - #gernPerDu
Qualifizierte und autorisierte Prüfstelle im BIK-BITV-Prüfverbund

Marc Haunschild Accessibility Consulting
Sonnenhof 32
53119 Bonn

Telefon: 0170 8 64 00 63
Web: https://Accessibility.Consulting https://haunschild.de 
Email: Marc.Haunschild@Accessibility.Consulting

> Am 07.05.2024 um 15:35 schrieb Karen Lewellen <klewellen@shellworld.net>:
> 
> Hi all,
> I am hoping that there is a link to well anything, guidance material for example, that provides  wisdom around progressive enhancement design.
> how, as I understand it, working from this foundation  creates broader access, can, in theory, get one closer to wcag compliance?
> I am encountering far too many folks who either believe that wcag only applies to sight loss, or that it *mandates* certain tools must be used legally...and some of that comes from the u. s. state department.
> Thanks,
> Karen
> 
> 
>