Skip to main content

Search

Items tagged with: webDev


I wrote an article about how to make hastags accessible. Did some #ScreenReader testing with #JAWS, #NVDA, #VoiceOver and #Narrator, which was fun!

Pretty long one though, contains a bunch of tables for comparison. Enjoy the ride!

stevefrenzel.dev/posts/easy-we…

#accessibility #a11y #html #JavaScript #WebDev #frontend


nginx (by F5) forked as freenginx by long time core developer Maxim Dounin 👀

freenginx.org/pipermail/nginx/…

phoronix.com/news/Nginx-Forked…

#freenginx #nginx #webdev #selfhosting #opensource


🤡 The wrong way to use aria-roledescription to call out someone as a fascist:

html5accessibility.com/stuff/2…

#a11y #webDev #politics #ARIA
[share author='stevef' profile='https://html5accessibility.com/stuff/author/stevef/' avatar='' link='https://html5accessibility.com/stuff/2020/10/06/micro-note-on-aria-roledescription/' posted='2020-10-06 13:28:50' guid='81daf735-8b2361906e7d629a-214181df' message_id='https://html5accessibility.com/stuff/2020/10/06/micro-note-on-aria-roledescription/']aria-roledescription is not a label

It is an alternative expression of the Aural UI of the role of an element.

inappropriately using aria-roledescription may inhibit users’ ability to understand or interact with an element.
ARIA 1.1

The wrong way to use aria-roledescription and call out someone as a fascist:

code

<img aria-roledescription="fascist" src="dt.PNG"
alt="Donald Trump">

This is wrong because you are not identifying the subject of the image as a fascist, you are overwriting the <img> element role so it effectively becomes a <fascist> element. Also, there is no explicit text identification of the subject as a fascist.

A much better way to achieve the aim of identifying a fascist (and not misusing aria-roledescription):
Example of a fascist
code
<figure>
<figcaption>Example of a fascist</figcaption>
<img src="dt.PNG" alt="Donald Trump">
</figure>

html5accessibility.com/stuff/2…


Introduction to web sustainability—learn how you can contribute to building a greener and sustainable web. developer.mozilla.org/en-US/bl… #webdev #webperf #environment #eWaste #goGreen


You Don't Need ARIA For That [HTMHell 2022] htmhell.dev/adventcalendar/202… #a11y #aria #webdev #html #tips


CSS + Accessibility: Inclusion Through User Choice
noti.st/cariefisher/1gWjQz/css…
Presentation slides from WordPress Accessibility Day by Carie Fisher
#css #a11y #webdesign #webdev


"The Decision to Leave Tech" — I'm sure many of us, including myself, have very similar feelings. 🥴 toddl.dev/posts/the-decision-t… by @todd #tech #a11y #burnout #webdev


+1000 "the community remains in solid denial about the disastrous consequences of an over-reliance on JavaScript" infrequently.org/2024/01/perfo… #webdev #javascript #webperf


Wanted: Staff Manager, Software Engineering, Accessibility at GitHub; remote, US; via LinkedIn linkedin.com/jobs/view/3792420… #webdev #a11y #jobs #github #dev #mgr


🍦 New Article: The decline of React gomakethings.com/the-decline-o… #WebDev #FrontEndDeveloper #100DaysOfCode #CodeNewbie


16 Lesser Known Accessibility Issues [and Tips]

toward.studio/latest/16-lesser…

"12. Don’t hide labels. Ever."

#a11y #accessibility #webdev #webdesign #tips #UIDesign #forms


React community appears to be finally starting to see how maybe, just maybe, things are a little overwrought and oversold for an abstraction that ultimately derives HTML.

dev.to/matfrana/react-where-ar…

#webdev #frontend #strugglestack


I needed to test support for dynamic accessible descriptions recently, so I made a blog post reference in case it's helpful for others.

darins.page/articles/dynamic-a…

#accessibility #a11y #html #webdev #ux #screenreader


Absolutely. "A lot of what people use React for would be better handled with vanilla JavaScript" gomakethings.com/a-lot-of-what… #webdev #reactJS #javascript #tips


Reprise: "On the <dl>" by @ben benmyers.dev/blog/on-the-dl/ #webdev #html


Getting started with Web Performance 🚀 [Tip 3: As little JavaScript as possible] htmhell.dev/adventcalendar/202… #webperf #webdev #webdevelopment #javascript #js


This is pretty cool 👉 [Star] Rating Slider Example by WAI w3.org/WAI/ARIA/apg/patterns/s… #webdev #ixd #a11y


Why web performance tools should be reporting website carbon emissions: calendar.perfplanet.com/2023/w… #webperf #webdev #environment #goGreen


loco-rs: releasing a framework inspired by Rails on Rust

loco.rs/

Discussions: discu.eu/q/loco.rs/

#programming #rails #ruby #rustlang #webdev


Front end devs really don't understand accessibility [learning HTML would also help very much] gomakethings.com/front-end-dev… #a11y #webdev #webdevelopment #accessibility


I have a question regarding a semantic HTML construct, and I'd like to know what the current consensus is (if there is one). So here goes:

Should navigation links be placed in an unordered list in a <nav>?

The spec doesn't recommend anything, but examples from MDN (developer.mozilla.org/en-US/do…) and WHATWG (html.spec.whatwg.org/multipage…) consistently use lists unless the contents are written in prose. Is this still the preference more broadly?

I have some other questions in this area. Safari removes list semantics if you remove the bullets (with exceptions, such as if the list is a child of "nav"), due to alleged "list-itis". At what point do lists become inappropriate? If I have a list of blog posts, and I format them as cards, with a heading, publish date, summary, and an image, is that too much content for each <li>?

Also, MDN and WHATWG point out not all links should be contained in navs (such as footer links), and "nav" should instead signal major blocks of navigation links. Would my prior example of a list of blog posts count as a major block? Should I enclose my list of blog posts in a nav? Does that extend to all section, category, and tag pages listing pages in that section/category/tag?

Feel free to respond if you have opinions, but keep it civil, and boosts are appreciated.

#HTML #semanticHTML #WebDev #website #accessibility #a11y


Answers to common (web) accessibility questions 👉 hidde.blog/a11y-faq/ #a11y #accessibility #webdev #webdesign


Inspecting websites and web views on iOS devices yatil.net/blog/inspect-web-ios by Eric Eggert #ios #webdev #dev #tips


Happy Firefox 120 release for those who celebrate 🎉

This comes with a couple important Debugger fixes and a bunch of accessibility improvements in the toolbox.

Grab your drink of choice and read through the full update fxdx.dev/firefox-devtools-news…

#Firefox #a11y #webdev


My colleague discovered this really solid collection of cheat sheets on application security topics:
cheatsheetseries.owasp.org/

#webdev #security


Related: 4 examples of web-accessible date pickers...

WAI: w3.org/WAI/ARIA/apg/patterns/d…

Deque: dequeuniversity.com/library/ar…

U.S. Web Design System
designsystem.digital.gov/compo…

Tommy Feldt: fymmot.github.io/inclusive-dat…

#date #calendar #UIDesign #webdesign #webdev #a11y


I just donated to the PHP Foundation. If you use PHP, like most of the Web, please consider donating. opencollective.com/phpfoundati… #php #webdev #donate


"Everything about SEO is obnoxious"
chriscoyier.net/2023/11/08/eve… Yes! #webdev #webdevelopment #webdesign #SEO


Web developers need to read this, and study it really well. "Foundations: HTML semantics" tetralogical.com/blog/2022/10/… #html #webdev #webdevelopment


Yup!!! "Web developers don't know HTML anymore" reidmore.online/post/accessibi… #webdev #webdevelopment #fail #html


Accessible Chips demo — "modified to use the HTML datalist element instead of a custom autosuggest". Nice! kindhearted-meal.glitch.me/ By @mfairchild365 (and inspired by me 😁 ). This demo is actually 4 years old! Browser support (for datalist) is better. #webdev #html #a11y


Say NO to broken browsers! ⛔

The EU is preparing a very dangerous law that would undermine the security of every browser.

Speak up now! 🗣️

@Jeremiah has more on how you can help to protect the web! 💪

jeremiahlee.com/posts/2023-eu-…

#EU
#privacy
#security
#webdev
#eIDAS