All too often I have seen developers reach for JavaScript to solve a problem when they do not need to. Welcome to *Use Less JavaScript* - an irregular series on native HTML5 elements you can use instead!

https://thomasrigby.com/posts/use-less-js-accordion/

#javascript #semanticHTML #frontend #development

At his presentation on ARIA at CSUN, Mark Steadman of Fidelity Investments mentioned that he's seeing an increase in websites using a <div> tag with the ContentEditable attribute, when an <input> or <TextArea> tag would do.

#HTML #SemanticHTML #a11y #CSUNATC2023

“ARIA should only be used to supplement HTML. If semantic HTML does a good enough job then ARIA should not be used. The hope is that HTML will eventually develop to sufficiently cover all accessibility needs without the need for ARIA.” — Emma Dawson

_____
#WebDevelopment #WebDev #Frontend #HTML #SemanticHTML #Accessibility #A11y #ARIA #Quote

“HTML has so many cool accessibility features. Too bad it is often left out of education and guides.” — @Pixdigit

_____
#WebDevelopment #WebDev #Frontend #Accessibility #A11y #HTML #SemanticHTML #Quote

Playing around with the #Mastodon #API I tried to see what was the simplest possible Mastodon client I could write.

So far I've only implemented reading of public feeds (federated, local, and hashtags), but I found I was able to implement that in about 300 lines of JavaScript and a small amount of custom #HTML and #CSS.

To keep things simple, I stuck as closely as possible to #SemanticHTML.
https://github.com/eobrain/simplodon

“Reduced usage of ARIA will, ironically, greatly increase accessibility.” — Dennis E. Lembrée https://ilo.im/zhqld

#webdevelopment #techniques
#accessibility #a11y #ARIA #markup #semanticHTML #HTML

“Reduced usage of ARIA will, ironically, greatly increase accessibility.” — Dennis E. Lembrée https://ilo.im/zhqld

#webdevelopment #techniques
#accessibility #a11y #ARIA #markup #semanticHTML #HTML

“Reduced usage of ARIA will, ironically, greatly increase accessibility.” — Dennis E. Lembrée

#webdevelopment #techniques
#accessibility #a11y #ARIA #markup #semanticHTML #HTML

RT @WalterStephanie
#SemanticHTML
Link or Button? Use an anchor element (link) when you need to connect two sources, use a button element when you need to let user perform a programmable action (like submitting a form, opening a dialog). As simple as that! by @AshleeMBoyer https://ashleemboyer.com/blog/should-i-use-a-button-or-a-link?utm_source=stephaniewalter.design&utm_medium=weeklylinks

@syntax
On second thought you may not need to break #semanticHTML if your webpage container is after the #checkboxHack?

So in #SASS it might be (very roughly):
.themeSwitcher[:checked] + #webpageContainer {
// test for what
// @aymm
// mentioned and have styles
// accordingly?
}

Do a small test first, perhaps?

@syntax
Great discussion here.

Break all #html semantics and put your entire webpage inside a #checkboxHack. Combine with what @aymm said to invert the default and the button operation. :)

Partly joking just because we'd like to see this attempted (there's possibly a #semanticHTML way to do it).