loading...

re: Tell us what your top unpopular tech opinion is 😈 VIEW POST

FULL DISCUSSION
 

This is nuclear: I love to use HTML and CSS in a multi page application, the way they did it in the 2000s. It's simple, easy and fast for the user.

I can make buttons without JavaScript by using <form action="nextpage.html">, and Netlify Analytics doesn't require any JavaScript to be included in the page. Javascript is render blocking, but HTML is fast and beautiful. It's pretty easy for me to maintain a 100 on Lighthouse, PageSpeed, Pingdom etc. with an HTML first philosophy.

 
 

I don't get why use <form> to make buttons? You can just style a <a> with css to look like a button and not break accessibility.

 

I run my website through the wave test for checking accessibility and it’s never said form action to change pages is a problem. Can you explain why this breaks accessibility in your view? I’d love to learn something new.

I'm not an accessibility expert. But the simpler the better for screen-reader.

<form action="page.html">
    <button type="submit">Click</button>
</form>

vs

<a href="page.html">Click</a>

What's make you prefer the former one ?

 

I really like this approach. No overhead whatsoever!

code of conduct - report abuse