as a designer who can do HTML and CSS, it’s nice to read that there are some orgs who appreciate this. but I still try to avoid JS and use chatgpt or something when I must write JS. sorry not sorry
When I work with real developers I engage with them to show them designs for feasibility, timelines, accessibility. But when I have worked with designers who don’t have these skills, and I have to break the news to them about their dribbbly designs, I have largely had success by starting from web standards and accessibility. So, in your example with the input, I’d tell them that a standard <input> comes with out-of-the-box accessibility for people who must use some sort of assistive tech but that custom stuff, even with all of the extra dev work done to satisfy the browser’s accessibility tree, is still unproven, which means we could actually hurt some users. That’s usually where I would add putting the user first means sticking as much as possible to standard HTML elements. But if it were a business, I’d make the argument from a liability stand point and use the DOJ’s recent guidance about websites are covered under the ADA.
Now for the unreasonable designers, I would just say no and email them, the project owner, with references links to DOJ and WCAG. That’s covering your ass and being an advocate for the assistive technology users at the same time. I once got designs from a print designer who didn’t know anything about web standards, etc., and when I brought up this stuff, they angrily retorted “I can do this in SquareSpace so why do we need you?” So, that’s when I first used the tactic I am telling you, which aligns closely with others’ responses here about sending emails. I would add a BCC to your own personal email too.
For me, it’s a combination of reading, more reading, and often re-reading to squeeze out more understanding or to be thorough. at first, idk when too much is too much because i have no domain knowledge on the subject. Then it’s using the knowledge to explain it to someone else or use it in a work project.
A few reasons, but I admit that doing so is becoming less attractive as tools grow in capability.
1. to think through information architecture and content structure, especially for accessibility
2. to stay familiar with the basics and foundations of what I do
3. semantics
Designer here, mostly in the same boat. Begin small moves to have your data in other, non Apple sources. Maybe put calendars in Google or Outlook, for example. Put Notes entries in Markdown files (there’s apps for that). I don’t know the extent of your hurdles, but I feel the same and started small migrations.
i suppose that "possible" depends on the denomination or sect, as their beliefs differ as to whether things or ideas can be transmitted across such a divide. But, if you're asking this because of a loved one you've lost, i am sorry for your loss.
i suppose that "possible" depends on the denomination or sect, as their beliefs differ as to whether things or ideas can be transmitted across such a divide. But, if you're asking this because of a loved one you've lost, i am sorry for your loss.