Søkeresultater
  1. 1. des.

    Good to know some folks think that creating accessible, usable content isn’t their responsibility 🙄

    Screenshot of email exchange; highlighted portion reads: “Sorry, it is not on my radar screen and I don’t think should be SME’s responsibility. We have enough problems getting documents finalized, let alone dealing with accessibility issues.”
    Screenshot of email exchange: “Actually, I want to push back on this. All of the SMEs (Subject Matter Experts) have more than enough to do in pulling together the information, getting the data, and getting something through clearance. And most do not create reports that require alt text more than. 1 or 2 times a year, if that. So I don’t think it should be our responsibility. Our responsibility is to try and write complex policies, etc. in plain language that people can understand. I think it is reasonable to expect that our communications experts take responsibility for any other accessibility issues with our public documents. I will not remember something I only do once a year. Sorry, I like to be a team player, but I also think there needs to be appropriate division of responsibilities.”
    2 svar 2 retweets 2 liker
  2. 6. des.

    Really nice post on the tab key as a powerful test tool.

    8 retweets 12 liker
  3. 3. des.

    Let’s talk about variable fonts. I’ll try to show how they help with , and why users, designers, and frontend engineers all win with them. Please, retweet the thread if it’s useful.

    2 svar 9 retweets 14 liker
    Vis denne tråden
    Vis denne tråden

Ingen treff.

Lastingen ser ut til å ta sin tid.

Twitter kan være overbelastet, eller det kan ha oppstått et midlertidig problem. Prøv igjen, eller se Twitters status for mer informasjon.