Search

Items tagged with: HTML









I find that web developers need to implement inputmode more often (to customize virtual keyboard for phone, email, etc). Hey Safari, why don't you support it?! developer.mozilla.org/en-US/do… #safari #browsers #html #forms #usability




#Development #Outlooks
The end of front-end development · Things are going to change, but not in the scary way people are saying ilo.im/11t8v2

_____
#Job #AI #GPT4 #ChatGPT #ChatBot #WebDevelopment #WebDev #Code #Frontend #HTML #CSS #JavaScript #Skills #Productivity





Glad <dialog> focus is finally being implemented/defined in a reasonable way after a torturous years long, largely pointless, discussion.

“1. Make the dialog focusing steps look at sequentially focusable elements instead of any focusable element.

2. Make the dialog element itself get focus if it has the autofocus="" attribute set.

3. Make the dialog element itself get focus as a fallback instead of focus being reset to the body element.”

#HTML #WebStandards #a11y

github.com/whatwg/html/commit/…






I make games. I often have the requirement to quickly build a dialog or a window of some kind. Using native HTMl here makes sense to me, so I'm implementing a bunch of components that implement the most common features I need in my UI.
Now they have to be accessible, so read well with screen readers, and be fully keyboard navigable. This includes things like lists, tab bars, menus, etc.
So here's the problem. I have some things that need to be inside a container. A list for example. So you have the list container, and then the list items inside it.
When you tab around, I want the container to be tabbable, not the list item. So you don't tab through the list, you tab to the list, and then use the arrows to move around.
Now here's the problem. When the container is tabbable, and not the list item, when you tab to the container, it either:
* reads something like "List title section" and then nothing, not even the item you have selected. Or
* Reads all the list items at once.
Either of those are not great obviously. Ideally, I'd like it to read the list title, then list, and then the selected item.
So the way I get it to do this is by detecting when you tab/focus the list container, and then immediately set the focus to the selected list item instead.
Now this works fantastic. You can tab around, and it automatically puts you right on the list item you have selected, and it even gets read.
But somehow, when you don't just tab around, but also shift tab around, this shift tab lands you back on the list container. And that automatically moves your focus back inside the list. So effectively, once you're in a list, you're trapped.
Does anyone have an idea how to get around this without doing ugly hacks like stealing tab and shift tab and implementing tab order myself? I want to use as many native browser features as possible so if there's another way to do this, please feel free to tell me.
#HTML #JavaScript #accessibility





📝 Upgrade Your HTML IV:

My new book is out! It’s about #HTML #minimization and #optimization, the theme of the respective book series.

“Apart from discussing the appropriate use and the subtleties of HTML elements, this edition covers general topics like conformance, maintainability, and the balancing of optimization vectors. It also covers topics like attribute minimization, void elements, metadata, table buttons and button links, and even CSS art.”

meiert.com/en/blog/upgrade-you…





Hi, I'm treefit, a #foss dev working on #deltachat. I'm responsible for the desktop client together with @jikstra.
My favorite coding language is #rustlang, but I "speak" #typescript, #javascript, #html, #css, too.
I'm also capable in #python and #swift, but not as much.

I'm new to the mastodon/toot style of communication (never used Twitter, either), so I'm still learning of how this all works.

My goal is to give you some behind-the scenes peeks onto the DeltaChat development.

#introduction


#html #web