• 0 Posts
  • 51 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle

  • Definitely not. NoJS is not better for accessibility. It’s worse.

    You need to set the ARIA states over JS. Believe me, I’ve written an entire component library with this in mind. I thought that NoJS would be better, having a HTML and CSS core and adding on JS after. Then for my second rewrite, I made it JS first and it’s all around better for accessibility. Without JS you’d be leaning into a slew of hacks that just make accessibility suffer. It’s neat to make those NoJS components, but you have to hijack checkbox or radio buttons in ways not intended to work.

    The needs of those with disabilities far outweigh the needs of those who want a no script environment.

    While with WAI ARIA you can just quickly assert that the page is compliant with a checker before pushing it to live.

    Also no. You cannot check accessibility with HTML tags alone. Full stop. You need to check the ARIA tags manually. You need to ensure states are updated. You need to add custom JS to handle key events to ensure your components work as suggested by the ARIA Practices page. Relying on native components is not enough. They get you somewhere there, but you’ll also run into incomplete native components that don’t work as expected (eg: Safari and touch events don’t work the same as Chrome and Firefox).

    The sad thing is that accessibility testing is still rather poor. Chrome has the best way to automate testing against the accessibility tree, but it’s still hit or miss at times. It’s worse with Firefox and Safari. You need to doubly confirm with manual testing to ensure the ARIA states are reported correctly. Even with attributes set correctly there’s no guarantee it’ll be handled properly by browsers.

    I have a list of bugs still not fixed by browsers but at least have written my workarounds for them and they are required JS to work as expected and have proper accessibility.

    Good news is that we were able to stop the Playwright devs from adopting this poor approach of relying on HTML only for ARIA testing and now can take accessibility tree snapshots based on realtime JS values.


  • No, if you click a link that brings you to or from a site your IP is logged

    No, clicked links that bring to a site do not log your IP. For that you would have to add some sort of JavaScript to intercept the click and then have some JavaScript execute a HTTP Request that passes that information (eg: HTTP POST). Then the IP can be grabbed via that request by the receiving server. Or more importantly, a tracking cookie.

    When clicking a link, the browser may add to Origin header on the HTTP request (HTTP HEAD/GET) that goes to the link’s server. Or the link itself can have UTM parameters, but there’s no guarantee that ever gets back to the original server.

    But the point is if you have a page with 1000 links on it, the server that serves you the page doesn’t know which one you clicked without JavaScript or reframing the link to go elsewhere, which is why this post exists.


  • I suggest against it. Just use JSDocs syntax and typescript (the CLI and VSCode checker) will check it. No need to use transcompiler anymore. It was more useful when JS itself was more ES5 based and CommonJS.

    Using something like esbuild will get you minification if you want it, but it’s only for deployment, not actually needed for runtime. Having pure JS code is much easier to work with and debug.


  • Connections
    Puzzle #624
    🟨🟨🟦🟨
    🟩🟦🟩🟨
    🟨🟨🟦🟨
    🟨🟨🟨🟨
    🟪🟪🟪🟪
    🟩🟩🟩🟩
    🟦🟦🟦🟦

    Affording to the bot 55% of first attempts got yellow wrong. That’s what happens when you put 5 words that mean the same thing. Bad puzzle today.

    28% picking the wrong 4 and 20% another wrong 4. And 16% getting the correct 4. 4% and 3% for the final variations.

    Edit: Though I guess, to be fair, I was supposed to avoid the category and come back to it later. But yellow is supposed to be the freebie.


  • I didn’t think it was actually going to be the solution. Usually the obvious ones are just tongue-in-cheek phrases, but the words don’t actually relate to each other.

    This is the first time I’ve seen Connections actually ask you to build a sentence with the words.

    How to Play
    Find groups of four items that share something in common.






  • Wordle 1,231 6/6*

    ⬛⬛⬛🟩⬛
    ⬛🟩⬛🟩🟩
    ⬛🟩⬛🟩🟩
    ⬛🟩⬛🟩🟩
    ⬛🟩⬛🟩🟩
    🟩🟩🟩🟩🟩

    This kinda shows how broken gradle is. After the second guess there were only 4 words left and they were all of equal possibility. But gradle still ranks them as poor.

    #Wordle1231 6/6* Grade: C

    ⬜⬜⬜🟩⬜ D
    ⬜🟩⬜🟩🟩 A
    ⬜🟩⬜🟩🟩 F
    ⬜🟩⬜🟩🟩 D-
    ⬜🟩⬜🟩🟩 A+
    🟩🟩🟩🟩🟩 A+

    https://gradle.app/#alHqEA1698HlFpqrwIOWW1DeYSUgn

    NYT bot ranks all the last 4 as 99 because they’re equality 1/4.


  • ShortFuse@lemmy.worldtoRPGMemes @ttrpg.networkFix This
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    9 months ago

    This is actually a thing in JoJo’s Bizarre Adventure (Crazy Diamond). It’s fun to see how they can make up cool scenarios with it:

    Feats of this nature include trapping an enemy by restoring pieces of a broken crate around him; exposing a Stand formerly bound to an object; and tracking by restoring a severed hand, forcing it to seek out and reattach itself to the body from which it was cut off.

    https://jojowiki.com/Crazy_Diamond




  • Don’t use JSON for the response unless you include the response header to specify it’s application/json. You’re better off with regular plaintext unless the request header Accept asked for JSON and you respond with the right header.

    That also means you can send a response based on what the request asked for.

    403 Forbidden (not Unauthorized) is usually enough most of the time. Most of those errors are not meant for consumption by an application because it’s rare for 4xx codes to have a contract. They tend to go to a log and output for human readers later, so I’d lean on text as default.


  • Daily Quordle 938
    8️⃣4️⃣
    6️⃣3️⃣
    m-w.com/games/quordle/
    ⬜⬜⬜⬜🟨 ⬜⬜⬜⬜⬜
    ⬜⬜🟨🟨⬜ ⬜⬜🟩🟨🟨
    ⬜🟨⬜🟨⬜ ⬜🟩⬜🟨⬜
    ⬜🟨🟨⬜⬜ 🟩🟩🟩🟩🟩
    ⬜🟩🟨🟩⬜ ⬛⬛⬛⬛⬛
    ⬜⬜⬜⬜⬜ ⬛⬛⬛⬛⬛
    🟨🟩⬜🟩🟩 ⬛⬛⬛⬛⬛
    🟩🟩🟩🟩🟩 ⬛⬛⬛⬛⬛

    ⬜🟨⬜🟨⬜ ⬜⬜🟨🟨⬜
    ⬜🟨⬜⬜🟨 🟨⬜🟨🟨⬜
    ⬜⬜🟨⬜⬜ 🟩🟩🟩🟩🟩
    🟩⬜⬜⬜⬜ ⬛⬛⬛⬛⬛
    ⬜⬜⬜⬜⬜ ⬛⬛⬛⬛⬛
    🟩🟩🟩🟩🟩 ⬛⬛⬛⬛⬛




  • I just recently started working with ImGui. Rewrite compiled game engines to add support for HDR into games that never supported it? Sure, easy. I can mod most games in an hour if not minutes.

    Make the UI respond like any modern flexible-width UI in the past 15 years? It’s still taking me days. All of the ImGui documentation is hidden behind closed GitHub issues. Like, the expected user experience is to bash your head against something for hours, then submit your very specific issue and wait for the author to tell you what to do if you’re lucky, or link to another issue that vaguely resembles your issue.

    I know some projects, WhatWG for one, follow the convention of, if something is unclear in the documentation, the issue does not get closed until that documentation gets updated so there’s no longer any ambiguity or lack of clarity.