3 ms·

A landing page with huge accessibility issues

scrollaway 6y ago
I wonder how you justify your use of the word "huge" here, given that it'll most likely be far better than most landing pages out there and not everyone will use the problematic components.
- forgotmypw17 6y ago
  I think this comment makes a pretty clear case for it: https://news.ycombinator.com/item?id=25168303 https://news.ycombinator.com/item?id=25168303 For me personally, the accessibility issues would be with elements used out of their usual role. For example: When I, blessed with being sighted at this time, but without a mouse, ask my browser to identify the clickable/actionable elements on the page, it mis-identifies both unclickable elements as clickable, and clickable elements as unclickable. I would call that a serious usability issue. And if I was not sighted, using a screen-reader, I would be very confused indeed by this landing page. I agree that whether this qualifies as a "huge" usability issue is indeed a matter of opinion. I would certainly argue that it is a huge usability issue.
  - ehnto 6y ago
    Using the software you've got, would using role attributes be a sufficient workaround?
noneeeed 6y ago
Accessibility is not something I know much about (I mostly work backend). What's the issue with this type of approach? I was tempted to use it as a starting point for a little side project, but Id rather not start with something with inherent accessibility issues.
- forgotmypw17 6y ago
  The biggest issue I noticed right away is that it uses elements outside of their traditional use cases. User agents rely on ``a`` elements being clickable, and ``span`` elements not being clickable, for example, to determine which actions to present to the user. When you use them outside of these use cases, the user agent has to do extra work to figure out whether something is actionable or not, and not all can do it adequately.
  - noneeeed 6y ago
    Thanks, that makes sense.
SippinLean 6y ago
The light grey text under "MVP.css works with the following HTML elements:" surely fails (WCAG2). `section` has an `h2`, but no `h1` for some reason. Other failures like this. Other than that what's wrong?
- darepublic 6y ago
  Is a lack of H1 a dock against accessibility?
  - ehnto 6y ago
    I think it would be, because a screen reader will try to call-out the topic of the document accurately and quickly. You don't want a user to have to dig through elements to find the real title of the page they're on.
    - darepublic 6y ago
      hm I've worked at plenty of places that touted accessibility, and we would often leave out h1 on a lander page (there might be a few h2 instead as the highest ranking headers)

I wonder how you justify your use of the word "huge" here, given that it'll most likely be far better than most landing pages out there and not everyone will use the problematic components.

forgotmypw17 6y ago
I think this comment makes a pretty clear case for it: https://news.ycombinator.com/item?id=25168303 https://news.ycombinator.com/item?id=25168303 For me personally, the accessibility issues would be with elements used out of their usual role. For example: When I, blessed with being sighted at this time, but without a mouse, ask my browser to identify the clickable/actionable elements on the page, it mis-identifies both unclickable elements as clickable, and clickable elements as unclickable. I would call that a serious usability issue. And if I was not sighted, using a screen-reader, I would be very confused indeed by this landing page. I agree that whether this qualifies as a "huge" usability issue is indeed a matter of opinion. I would certainly argue that it is a huge usability issue.
- ehnto 6y ago
  Using the software you've got, would using role attributes be a sufficient workaround?

noneeeed 6y ago

Accessibility is not something I know much about (I mostly work backend). What's the issue with this type of approach? I was tempted to use it as a starting point for a little side project, but Id rather not start with something with inherent accessibility issues.

forgotmypw17 6y ago
The biggest issue I noticed right away is that it uses elements outside of their traditional use cases. User agents rely on ``a`` elements being clickable, and ``span`` elements not being clickable, for example, to determine which actions to present to the user. When you use them outside of these use cases, the user agent has to do extra work to figure out whether something is actionable or not, and not all can do it adequately.
- noneeeed 6y ago
  Thanks, that makes sense.

SippinLean 6y ago

The light grey text under "MVP.css works with the following HTML elements:" surely fails (WCAG2). `section` has an `h2`, but no `h1` for some reason. Other failures like this. Other than that what's wrong?

darepublic 6y ago
Is a lack of H1 a dock against accessibility?
- ehnto 6y ago
  I think it would be, because a screen reader will try to call-out the topic of the document accurately and quickly. You don't want a user to have to dig through elements to find the real title of the page they're on.
  - darepublic 6y ago
    hm I've worked at plenty of places that touted accessibility, and we would often leave out h1 on a lander page (there might be a few h2 instead as the highest ranking headers)