It's always so frustrating when all the web accessibility content only talks about text heavy websites and forms. Like yes, I get it, I should have alt text on images. But there's so little information about how to build accessible web apps. What do I do if 80% of my page is a WebGL canvas and the other 20% is all buttons/sliders? How do I structure this if there is basically no "regular text" on the entire page?
@aardrian I have seen a few of your articles in the past, I'm so thankful that you provide fairly specific examples. So much of accessibility stuff is too abstract. "Only use this feature in this vague situation", "It depends on your content", "Go read these 100+ lines of ARIA guidelines".
I really wish that someone would make a "Let's build Figma like program from an accessibility point of view" course. I would buy that in a heartbeat.
@peterreeves A big reason you have to wade through so much intro cruft is because a lot of folks (including practitioners) don’t know much beyond that (if that, even). UIs move faster than the patterns, and host platforms impose some limits.
But yeah, I would also love to see a ground-up build course. The catch, of course, is that even those platforms get it wrong in a lot of ways, so that would be a big lift to write (assuming a client didn’t already pay for one and NDA it).
Yes CSS is more then only a design and colors and have today cool functions to select specific HTML components and pleace web designer think in different screen spaces.
Now that I realize it, I would love to take a break for a few months… Just live my life and not solving luxus problems of other people day by day. Just doing my own thing for some time.
Unfortunately, I don't have rich parents, nor have I inherited wealth from anyone else. So that remains a dream...
Once I thought, what if there was a CSS file that makes the document look like it is a command line interface... So I made one, but I really don't know what it could be used for :) #webdev#css
Your boss, manager or client will never ask you to take time to refactor your code. They'll never ask you to set up a test suite for the code you wrote. They'll never ask you to upgrade your framework.
Do these things every day. Make them a part of your process. You don't need permission.
Should I use ::after pseudo-element to add a sort order indicator?
It feels like it's not very accessible because the semantic HTML content doesn't actual contain the sort indicator... but the way I'm conditionally adding it is by reading the aria-sort attribute so maybe that's the accessible part of things and the ::after content doesn't need to be SR-friendly 🤷
@aardrian@goulet Ah yeah if the browser doesn't support it then that will invalidate the whole line. Am I right in thinking once browser support for that syntax improves (it should be in Safari now at least) then it will be okay to use?
I would say it depends on the percentage reference. In some cases, we cannot resolve the percentage so the 100% will fall to auto and you can see a different behavior.
Django 5.1 alpha 1 is now available. It represents the first stage in the 5.1 release cycle and is an opportunity for you to try out the changes coming in Django 5.1.
This alpha milestone marks the feature freeze. The current release schedulecalls for a beta release in about a month and a release candidate about a month from then. We'll only be able to keep this schedule if we get early and often testing from the community. Updates on the release schedule are available on the Django forum.
As with all alpha and beta packages, this is not for production use. But if you'd like to take some of the new features for a spin, or to help find and fix bugs (which should be reported to the issue tracker), you can grab a copy of the alpha package from our downloads page or on PyPI.
The PGP key ID used for this release is Natalia Bidart: 2EE82A8D9470983E.
@cferdinandi it may be working for me because all my mutations are sourced from the UI components, as a result of user actions. The models connect to each other but rarely (never?) mutate themselves. That constraint makes the design simpler, while also ensuring the models never have to worry about their properties becoming proxies (which I believe had some ill effects when I stringified to JSON).