@yatil@yatil.social
@yatil@yatil.social avatar

yatil

@yatil@yatil.social

he/him/his

Accessibility Advocado

http://yatil.net

Outline Consulting · Axess Lab
formerly: Knowbility, W3C/WAI

Views are my own.

Ⓥ he/him/his

#accessibility #a11y #humanrights #germany #ebiking #webdev #design #typography #fedi22

This profile is from a federated server and may be incomplete. Browse more on the original instance.

joelanman, to accessibility
@joelanman@hachyderm.io avatar

It's unclear whether it passes wcag but from our research I think it's much clearer to mark optional fields as 'optional' than have asterisks or 'required' next to every field and have optional fields implied by the lack of them.

If you're asking for data, the default should be it's because it is required. This is part of GDPR

yatil,
@yatil@yatil.social avatar

@siblingpastry @joelanman My feeling would be that having required fields announced in screen readers the same way across websites makes those fields easier to recognize.

It’s totally fine to have optional fields marked visually (and/or in the label) and still ensure required fields have aria-required set to true.

yatil,
@yatil@yatil.social avatar

@siblingpastry @joelanman In an optimal state, aria would allow you to set aria-requiredstate="required"/"optional" and users could set their preference in what is announced. But how it is currently, not having aria-required set is ambiguous because there are so many forms out there that don’t use it at all.

yatil,
@yatil@yatil.social avatar

@siblingpastry @joelanman How is it inconsistent?

Name, textbox, required
Email (optional), textbox

Feels pretty consistent to me.

yatil,
@yatil@yatil.social avatar

@joelanman @siblingpastry That’s the argument for marking required fields programmatically even if you visually only mark optional fields. (4.1.2 does not care about what’s visible.)

yatil,
@yatil@yatil.social avatar

@siblingpastry @joelanman But they do match. 🙂

yatil,
@yatil@yatil.social avatar

@joelanman @siblingpastry In context, it’s clear. The visual label does not only depend on the isolated UI element.

yatil, to random
@yatil@yatil.social avatar

If your pitch is “X but accessible” you’re building features. That’s cool, but maybe you don’t need to build the X part.

Use an API to get the information from the less accessible places, provide an alternative UI that is easy to use. Help to make the content accessible where people go now instead of making a third place “for people with accessibility needs”.

To make “X but accessible” succeed, you need to be the best “X” compared existing solutions, which is almost impossible. Zoom did it.

yatil,
@yatil@yatil.social avatar

@bobschi Yes.

aleen, to random
@aleen@wandering.shop avatar

It's an auspicious day!

yatil,
@yatil@yatil.social avatar

@aleen I hope there is no misty stepping away!

joelanman, to javascript
@joelanman@hachyderm.io avatar

given delete is a keyword in JavaScript, what word do you use for a function that deletes in your own code? del, destroy, other?

yatil,
@yatil@yatil.social avatar

@joelanman EXTERMINATE.

Of course!

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • megavids
  • modclub
  • DreamBathrooms
  • mdbf
  • magazineikmin
  • InstantRegret
  • Durango
  • Youngstown
  • slotface
  • thenastyranch
  • love
  • kavyap
  • GTA5RPClips
  • normalnudes
  • tester
  • khanakhh
  • ngwrru68w68
  • everett
  • osvaldo12
  • rosin
  • ethstaker
  • Leos
  • anitta
  • cubers
  • tacticalgear
  • cisconetworking
  • provamag3
  • JUstTest
  • All magazines
    •