• 0x1C3B00DA@fedia.io
    link
    fedilink
    arrow-up
    1
    ·
    5 days ago

    Nearly every web app that uses an input calculates and displays some result based on those inputs. It’s clearly useful.

      • 0x1C3B00DA@fedia.io
        link
        fedilink
        arrow-up
        1
        ·
        4 days ago

        Yes exactly. Which is reason enough to use it, unless you purposefully want worse accessibility.

        You could make the same argument about p, h1 - h6, label, etc.

        • FizzyOrange@programming.dev
          link
          fedilink
          arrow-up
          1
          ·
          4 days ago

          All those other elements give some benefit apart from accessibility which is why they are universally used and output isn’t.

          Expecting all devs to test their sites with screen readers is unrealistic.

          • 0x1C3B00DA@fedia.io
            link
            fedilink
            arrow-up
            1
            ·
            4 days ago

            Expecting all devs to test their sites with screen readers is unrealistic.

            I disagree with this but its not what we’re talking about. You said output is useless and I’m saying its obviously not. There’s zero cost to using it instead of a div so the only reason not to use it is to purposefully screw users who need accessibility features.

            All those other elements give some benefit apart from accessibility

            Maybe for label but p and h1 - h6 only differ from div in styles, which is another argument in my favor. If you’re willing to swap a div for one of those for visual users, swapping a div for output should be just as easy of a change.

            • FizzyOrange@programming.dev
              link
              fedilink
              arrow-up
              1
              ·
              4 days ago

              You said output is useless

              No I said it’s not very useful.

              There’s zero cost to using it instead of a div so the only reason not to use it is to purposefully screw users who need accessibility features.

              No, the main reason is because people don’t know about it, because it’s an extra thing to remember for little benefit. Same reason other semantic-only tags like article get very little use.

              only differ from div in styles

              Err yeah the “only” do a really useful thing that lots of people want.

              If output came with some nice styling and maybe animations… maybe a built in copy-to-clipboard option… then people would have used it.

              • 0x1C3B00DA@fedia.io
                link
                fedilink
                arrow-up
                1
                ·
                3 days ago

                the main reason is because people don’t know about it

                But you know about it now and you’re still arguing against it.

                it’s an extra thing to remember for little benefit the “only” do a really useful thing that lots of people want.

                The benefit you see in those tags is the same level of benefit that users who use accessibility features get from output and other semantic tags. But your argument seems to boil down to “I dont need accessibility features so i don’t care about enabling them for ppl who do”. That’s very disappointing and continuing this debate seems pointless so i’m gonna stop here