Online Resource

Hayden Library - QL785.27.W33 2019

Hayden Library - QL757.S48 2018

Dewey Library - PR6116.R525 W43 2019

The advisory was issued by the Ministry of AYUSH to support the efforts of all as a measure towards enhancing immunity.

Eberhardt, Jennifer L. (Jennifer Lynn), author

Thomas, Craig, 1969-

Listen to stories on how plants know when to take risks, confirmation that the ozone layer is on the mend, and genes that come alive after death, with Online News Editor David Grimm.   Science news writer Jon Cohen talks with Julia Rosen about South Africa’s bid to end AIDS.   [Image: J.Seita/Flickr/Music: Jeffrey Cook]  

This week, we chat about some of our favorite stories—is Bhutan really a quake-free zone, how much of scientific success is due to luck, and what farming changed about dogs and us—with Science’s Online News Editor David Grimm. Plus, Science’s Alexa Billow talks to Katelyn Gostic of the University of California, Los Angeles, about how the first flu you came down with—which depends on your birth year—may help predict your susceptibility to new flu strains down the road.   Listen to previous podcasts.     [Image:monkeybusinessimages/iStockphoto; Music: Jeffrey Cook]

This week, we chat about kissing communication in ants, building immune strength by climbing the social ladder, and a registry for animal research with Online News Editor David Grimm. Plus, Science’s Alexa Billow talks to Bjorn Emonts about the birth of stars in the Spiderweb Galaxy 10 billion years ago.   Related research on immune function and social hierarchy.   Listen to previous podcasts.   [Image: Lauren Brent; Music: Jeffrey Cook]

Sarah Crespi talks to Sam Smits about how our microbial passengers differ from one culture to the next—are we losing diversity and the ability to fight chronic disease? For our books segment, Jen Golbeck talks with Vyvyan Evans about his book The Emoji Code: The Linguistics Behind Smiley Faces and Scaredy Cats. Listen to previous podcasts. [Image: Woodlouse/Flickr; Music: Jeffrey Cook]

David Grimm—online news editor for Science—talks with Sarah Crespi about two underwater finds: the first sharks shown to survive off of seagrass and what fossilized barnacles reveal about ancient whale migrations. Sarah also interviews Staff Writer Adrian Cho about what happens after quantum computing achieves quantum supremacy—the threshold where a quantum computer’s abilities outstrip nonquantum machines. Just how useful will these machines be and what kinds of scientific problems might they tackle? Listen to previous podcasts.  [Image: Aleria Jensen, NOAA/NMFS/AKFSC; Music: Jeffrey Cook]

Armed with new data, archaeologists are revealing that mind-altering drugs were present at the dawn of the first complex societies some 5000 years ago in the ancient Middle East. Contributing writer Andrew Lawler joins Sarah Crespi to discuss the evidence for these drugs and how they might have impacted early societies and beliefs. Sarah also interviews Sarah Hobbie of the University of Minnesota about the fate of plants under climate change. Will all that extra carbon dioxide in the air be good for certain types of flora? A 20-year long study published this week in Science suggests theoretical predictions have been off the mark. This week’s episode was edited by Podigy. Listen to previous podcasts. [Image: Public domain Music: Jeffrey Cook]

Wild polio has been hunted to near extinction in a decades-old global eradication program. Now, a vaccine-derived outbreak in the Democratic Republic of the Congo (DRC) is threatening to seriously extend the polio eradication endgame. Deputy News Editor Leslie Roberts joins host Sarah Crespi to talk about the tough choices experts face in the fight against this disease in the DRC. Sarah also talks with Online News Editor David Grimm about when dogs first came to the Americas. New DNA and archaeological evidence suggest these pups did not arise from North American wolves but came over thousands of years after the first people did. Now that we know where they came from, the question is: Where did they go? Read the research. This week’s episode was edited by Podigy. Download a transcript of this episode (PDF) Listen to previous podcasts. About the Science Podcast [Image: Polio virus/David Goodsell/RCSB PDB; Music: Jeffrey Cook]

Yes, humans are the only species with language, but how did we acquire it? New research suggests our linguistic prowess might arise from the same process that brought domesticated dogs big eyes and bonobos the power to read others’ intent. Online News Editor Catherine Matacic joins host Sarah Crespi to talk about how humans might have self-domesticated themselves, leading to physical and behavioral changes that gave us a “language-ready” brain. Sarah also talks with Micah Edelson of the University of Zurich in Switzerland about his group’s research into the role that “responsibility aversion”—the reluctance to make decisions for a group—might play when people decide to lead or defer in a group setting. In their experiments, the team found that some people adjusted how much risk they would take on, depending on whether they were deciding for themselves alone or for the entire group. The ones who didn’t—those who stuck to the same plan whether others were involved or not—tended to score higher on standardized tests of leadership and have held higher military rank. This week’s episode was edited by Podigy. Download a transcript of this episode (PDF) Listen to previous podcasts. [Image: Scaly breasted munia/Ravi Vaidyanathan; Music: Jeffrey Cook]

A small isolated town in Colombia is home to a large cluster of people with fragile X syndrome—a genetic disorder that leads to intellectual disability, physical abnormalities, and sometimes autism. Spectrum staff reporter Hannah Furfaro joins host Sarah Crespi to discuss the history of fragile X in the town of Ricaurte and the future of the people who live there. Also this week, we talk about greening up grass. Lawns of green grass pervade urban areas all around the world, regardless of climate, but the cost of maintaining them may outweigh their benefits. Host Meagan Cantwell talks with Maria Ignatieva of The University of Western Australia in Perth and the Swedish University of Agricultural Sciences in Uppsala about how lawns can be transformed to contribute to a more sustainable future. This week’s episode was edited by Podigy. Download a transcript of this episode (PDF) Listen to previous podcasts. About the Science Podcast [Image: Adam Kerfoot-Roberts/Flickr; Music: Jeffrey Cook]

Getting into an MRI machine can be a tight fit for just one person. Now, researchers interested in studying face-to-face interactions are attempting to squeeze a whole other person into the same tube, while taking functional MRI (fMRI) measurements. Staff Writer Kelly Servick joins host Sarah Crespi to talk about the kinds of questions simultaneous fMRIs might answer. Also this week, Sarah talks with Igor Grossman, director of the Wisdom and Culture Lab at the University of Waterloo, about his group’s Science Advances paper on public perceptions of the difference between something being rational and something being reasonable. This week’s episode was edited by Podigy. Read a transcript (PDF) Listen to previous podcasts. About the Science Podcast

Ranbir Kapoor and his father -- the late Rishi Kapoor -- shared a turbulent relationship.

International instances back higher tax liabilities for the rich at times of exigencies.

Join the tax lawyers of Dentons Canada LLP for an instructive overview and update of the tax rules in respect of foreign affiliates. Cross border holdings and debt require special consideration in tax filing, and Canada’s foreign affiliate tax regime has undergone some significant changes in the past couple of years. This webinar will examine the basics of Canada’s foreign affiliate taxation regime - as it applies to small and medium enterprises (SMEs) – who already carry an international presence, or are considering expansion abroad.

Available Sessions for this Seminar:

January 21, 2015 12:00 PM - 2:00 PM EST

Online Resource

Dewey Library - HD30.28.Z425 2018

Dewey Library - HD30.2.W4514 2018

National Teacher Day honors teachers for the lasting contributions they make to students’ lives.

A physician answers five common questions.

‘Chosen Spirits’ is neither simple dystopic science-fiction nor straightforward political satire, but a call for freedom in an age of puppy adoption shows.

The lockdown has not ‘killed’ the virus and was never going to. We will have to learn to live with Covid-19, possibly until 2022.

All publishing will fight fascism. Autofiction will auto-destruct after reading. The author will be killed again so the text may live.

Dr David Kerr on when it might be the right decision to tell patients that you believe they're pursuing the wrong treatment.
Medscape Oncology

Rotch Library - GF75.W375 2020

Rediff readers sent us these pictures to show how their kids are making the most of the lockdown.

Amy Hupe prepares a four bird roast of tasty treats so we can learn how the needs of many different types of users can be served through careful implementation of components within a design system.

Design systems help us to make our products consistent, and to make sure we’re creating them in the most efficient way possible. They also help us to ensure our products are designed and built to a high quality; that they’re not only consistent in appearance, and efficiently-built, but that they are good. And good design means accessible design.

1 in 5 people in the UK have a long term illness, impairment or disability – and many more have a temporary disability. Designing accessible services is incredibly important from an ethical, reputational and commercial standpoint. For EU government websites and apps, accessibility is also a legal requirement.

With that in mind, I’ll explain the four main ways I think we can use design systems to promote accessible design within an organisation, and what design systems can’t do.

1. Bake it in

Design systems typically provide guidance and examples to aid the design process, showing what best practice looks like. Many design systems also encompass code that teams can use to take these elements into production. This gives us an opportunity to build good design into the foundations of our products, not just in terms of how they look, but also how they work. For everyone.

Let me give an example.

The GOV.UK Design System contains a component called the Summary list. It’s used in a few different contexts on GOV.UK, to summarise information. It’s often used at the end of a long or complex form, to let users check their answers before they send them, like this:

Users can review the information and, if they’ve entered something incorrectly, they can go back and edit their answer by clicking the “Change” link on the right-hand side. This works well if you can see the change link, because you can see which information it corresponds to.

In the top row, for example, I can see that the link is giving me the option to change the name I’ve entered because I can see the name label, and the name I put in is next to it.

However, if you’re using a screen reader, this link – and all the others – will just say “change”, and it becomes harder to tell what you’re selecting. So to help with this, the GOV.UK Design System team added some visually-hidden text to the code in the example, to make the link more descriptive.

Sighted users won’t see this text, but when a screen reader reads out the link, it’ll say “change name”. This makes the component more accessible, and helps it to satisfy a Web Content Accessibility Guidelines (WCAG 2.1) success criterion for links which says we must “provide link text that identifies the purpose of the link without needing additional context”.

By building our components with inclusion in mind, we can make it easier to make products accessible, before anyone’s even had to think about it. And that’s a great starting point. But that doesn’t mean we don’t have to think about it – we definitely do. And a design system can help with that too.

2. Explain it

Having worked as the GOV.UK Design System’s content designer for the best part of 3 years, I’m somewhat biased about this, but I think that the most valuable aspect of a design system is its documentation.

(Here’s a shameless plug for my patterns Day talk on design system documentation earlier this year, if you want to know more about that.)

When it comes to accessibility, written documentation lets us guide good practice in a way that code and examples alone can’t.

By carefully documenting implementation rules for each component, we have an opportunity to distribute accessible design principles throughout a design system. This means design system users encounter them not just once, but repeatedly and frequently, in various contexts, which helps to build awareness over time.

For instance, WCAG 2.1 warns against using colour as “the only visual means of conveying information, calling an action, prompting a response or distinguishing a visual element”. This is a general principle to follow, but design system documentation lets us explain how this relates to specific components.

Take the GOV.UK Design System’s warning buttons. These are used for actions with serious, often destructive consequences that can’t easily be undone – like permanently deleting an account.

The example doesn’t tell you this, but the guidance explains that you shouldn’t rely on the red colour of warning buttons to communicate that the button performs a serious action, since not all users will be able to see the colour or understand what it signifies.

Instead, it says, “make sure the context and button text makes clear what will happen if the user selects it”. In this way, the colour is used as an enhancement for people who can interpret it, but it’s not necessary in order to understand it.

Making the code in our examples and component packages as accessible as possible by default is really important, but written documentation like this lets us be much more explicit about how to design accessible services.

3. Lead by example

In our design systems’ documentation, we’re telling people what good design looks like, so it’s really important that we practice what we preach.

Design systems are usually for members of staff, rather than members of the public. But if we want to build an inclusive workplace, we need to hold them to the same standards and ensure they’re accessible to everyone who might need to use them – today and in the future.

One of the ways we did this in my team, was by making sure the GOV.UK Design System supports users who need to customise the colours they use to browse the web. There are a range of different user needs for changing colours on the web. People who are sensitive to light, for instance, might find a white background too bright. And some users with dyslexia find certain colours easier to read than others.

My colleague, Nick Colley, wrote about the work we did to ensure GOV.UK Design System’s components will work when users change colours on GOV.UK. To ensure we weren’t introducing barriers to our colleagues, we also made it possible to customise colours in the GOV.UK Design System website itself.

Building this flexibility into our design system helps to support our colleagues who need it, but it also shows others that we’re committed to inclusion and removing barriers.

4. Teach it

The examples I’ve drawn on here have mostly focused on design system documentation and tooling, but design systems are much bigger than that. In the fortuitously-timed “There is No Design System”, Jina reminds us that tooling is just one of the ways we systematise design:

…it’s a lot of people-focused work: Reviewing. Advising. Organizing. Coordinating. Triaging. Educating. Supporting.”

To make a design system successful, we can’t just build a set of components and hope they work. We have to actively help people find it, use it and contribute to it. That means we have to go out and talk about it. We have to support people in learning to use it and help new teams adopt it. These engagement activities and collaborative processes that sit around it can help to promote awareness of the why, not just the what.

At GDS, we ran workshops on accessibility in the design system, getting people to browse various web pages using visual impairment simulation glasses to understand how visually impaired users might experience our content. By working closely with our systems’ users and contributors like this, we have an opportunity to bring them along on the journey of making something accessible.

We can help them to test out their code and content and understand how they’ll work on different platforms, and how they might need to be adjusted to make sure they’re accessible. We can teach them what accessibility means in practice.

These kinds of activities are invaluable in helping to promote accessible design thinking. And these kinds of lessons – when taught well – are disseminated as colleagues share knowledge with their teams, departments and the wider industry.

What design systems can’t do

Our industry’s excitement about design systems shows no signs of abating, and I’m excited about the opportunities it affords us to make accessible design the default, not an edge case. But I want to finish on a word about their limitations.

While a design system can help to promote awareness of the need to be accessible, and how to design products and services that are, a design system can’t make an organisation fundamentally care about accessibility.

Even with the help of a thoughtfully created design system, it’s still possible to make really inaccessible products if you’re not actively working to remove barriers. I feel lucky to have worked somewhere that prioritises accessibility. Thanks to the work of some really brilliant people, it’s just part of the fabric at GDS. (For more on that work and those brilliant people, I can’t think of a better place to start than my colleague Ollie Byford’s talk on inclusive forms.)

I’m far from being an accessibility expert, but I can write about this because I’ve worked in an organisation where it’s always a central consideration. This shouldn’t be something to feel lucky about. It should be the default, but sadly we’re not there yet. Not even close.

Earlier this year, Domino’s pizza was successfully sued by a blind customer after he was unable to order food on their website or mobile app, despite using screen-reading software. And in a recent study carried out by disability equality charity, Scope, 50% of respondents said that they had given up on buying a product because the website, app or in-store machine had accessibility issues.

Legally, reputationally and most importantly, morally, we all have a duty to do better. To make sure our products and services are accessible to everyone. We can use design systems to help us on that journey, but they’re just one part of our toolkit.

In the end, it’s about committing to the cause – doing the work to make things accessible. Because accessible design is good design.

About the author

Amy is a content specialist and design systems advocate who’s spent the last 3 years working as a Senior Content Designer at the Government Digital Service.

In that time, she’s led the content strategy for the GOV.UK Design System, including a straightforward and inclusive approach to documentation.

In January, Amy will continue her work in this space, in her new role as Product Manager for Babylon Health’s design system, DNA.

More articles by Amy

Dewey Library - HV6626.2.S59 2019

Dewey Library - JF801.S694 2020

Online Resource

Dewey Library - HV9950.K34 2018

Hayden Library - HV6558.A295 2018

Dewey Library - JC311.R35313 2018

After 684 deaths, countless tests, several visits by experts are no closer to getting the answer.

With Phailin expected to make a landfall on Saturday, NDMA provides measures to be followed.

The BJP PM candidate questioned the silence of Manmohan and Sonia over rising prices.

Justice Ganguly is serving as chairman of the West Bengal Human Rights Commission.

Gunter, Michael M., 1969- author

Romm, Joseph J., author

Emanuel, Kerry A., 1955- author

Panel:

• AJ O’Neal
• Aimee Knight
• Joe Eames
• Charles Max Wood

Special Guests: Chris Heilmann

In this episode, the panel talks with programmer, Chris Heilmann. He has written books about JavaScript, in addition to writing a blog about it and is an educator about this program.  He currently resides in Berlin, Germany. Let’s welcome our special guest and listen to today’s episode!

Show Topics:

2:19 – Chuck talks.

2:41 – Chris: He has talked about JavaScript in Berlin upon an invitation. You can get five different suggestions about how to use JavaScript. The best practices, I have found, are on the projects I am on now. JavaScript was built in ten days. My goal is to help people navigate through JavaScript and help them feel not disenfranchised. 

5:47 – Aimee: The overall theme is...

5:54 – Panelist: I really like what you said about helping people not feeling disenfranchised.

6:47 – Chris: There is a lot of peer pressure at peer conferences

7:30 – Aimee chimes in with some comments.

7:50: Chris: I think we need to hunt the person down that put...

8:03 – Panelist: A good point to that is, I try to avoid comments like, “Well, like we ALL know...”

8:27 – Chris: There are things NOT to say on stage. It happens, but we don’t want to say certain things while we are teaching people. We are building products with different groups, so keep that in mind.

9:40 – Aimee: My experience in doing this is that I have found it very rewarding to share embarrassing experiences that I’ve had. My advice would to tell people to let their guard down. It’s encouraging for me.

10:26 – Chris: It helps to show that you are vulnerable and show that you are still learning, too. We are all learning together. 90% of our job is communicating with others.

11:05 – Chuck: Now, I do want to ask this...

11:35 – Chris answers.

12:24 – What makes you say that? (Question to Chris)

12:25 – Chris answers.

13:55 – Chuck: The different systems out there are either widely distributed or...

You will have to work with other people. There is no way that people can make that on their own. If you can’t work with other people, then you are a hindrance.

14:31 – Aimee chimes in.

14:53 – Chris: They have to be very self-assured. I want to do things that are at the next level. Each developer has his or her own story. I want to move up the chain, so I want to make sure these developers are self-assured.

16:07 – Chris: Back to the article...

18:26 – Chuck: Yes, I agree. Why go and fight creating a whole system when it exists.

18:54 – Chris chimes in with some comments.

19:38 – Panelist: I still use console logs.

19:48 – Chris: We all do, but we have to...

19:55 – Aimee: In the past year, I can’t tell you how much I rely on this. Do I use Angular? Do I learn Vue? All those things that you can focus on – tools.

10:21 – Chris: We are talking about the ethics of interfaces. Good code is about accessibility, privacy and maintainability, among others. Everything else is sugar on top. We are building products for other people.

22:10 – Chuck: That is the interesting message in your post, and that you are saying: having a deep, solid knowledge of React (that is sort of a status thing...). It is other things that really do matter. It’s the impact we are having. It’s those things that will make the difference. Those things people will want to work with and solves their problems.

23:00 – Chris adds his comments. He talks about Flash.

24:05 – Chris: The librarian motto: “I don’t know everything, but I can look “here” to find the answer.” We don’t know everything.

24:31 – Aimee: Learn how to learn.

24:50 – Chris: There is a big gap in the market. Scratch is a cool tool and it’s these puzzle pieces you put together. It was hard for me to use that system. No, I don’t want to do that. But if you teach the kids these tools then that’s good. 

24:56 – Chuck: Here is the link, and all I had to do was write React components.

26:12 – Chris: My first laptop was 5x more heavy then this one is. Having access to the Internet is a blessing.

27:24 – Advertisement

28:21 – Chuck: Let’s bring this back around. If someone has gone through boot camp, you are recommending that they get use to know their editor, debugging, etc.

Chris: 28:47 – Chris: Yes, get involved within your community. GitHub. This is a community effort. You can help. Writing code from scratch is not that necessary anymore. Why rebuild something if it works. Why fix it if it’s not broken?

31:00 – Chuck talks about his experience.

31:13 – Chris continues his thoughts.

Chris: Start growing a community.

32:01 – Chuck: What ways can people get involved within their community?

32:13 – Chris: Meetup. There are a lot of opportunities out there. Just going online and seeing where the conferences

34:08 – Chris: It’s interesting when I coach people on public speaking. Sharing your knowledge and learning experience is great!

34:50 – Chuck: If they are learning how to code then...by interacting with people you can get closer to what you need/want.

35:30 – Chris continues this conversation.

35:49 – Chris: You can be the person that helps with x, y, z. Just by getting your name known then you can get a job offer.

36:23 – Chuck: How do you find out what is really good content – what’s worth your time vs. what’s not worth your time?

36:36 –Chris says, “That’s tricky!” Chris answers the question.

37:19: Chris: The best things out there right now is...

38:45 – Chuck: Anything else that people want to bring up?

39:00 – Chris continues to talk.

42:26 – Aimee adds in her thoughts.

Aimee: I would encourage people to...

43:00 – Chris continues the conversation.

Chris: Each project is different, when I build a web app is different then when I build a...

45:07 – Panelist: I agree. You talked about abstractions that don’t go away. You use abstractions in what you use. At some point, it’s safe to rly on this abstraction, but not this one. People may ask themselves: maybe CoffeeScript wasn’t the best thing for me.

46:11 – Chris comments and refers to jQuery.

48:58 – Chris continues the conversation.

Chris: I used to work on eight different projects and they worked on different interfaces. I learned about these different environments. This is the project we are now using, and this will like it for the end of time. This is where abstractions are the weird thing. What was the use of the abstraction if it doesn’t have longevity? I think we are building things too soon and too fast.

51:04 – Chris: When I work in browsers and come up with brand new stuff.

52:21 – Panelist: Your points are great, but there are some additional things we need to talk about. Let’s take jQuery as an example. There is a strong argument that if you misuse the browser...

53:45 – Chris: The main issue I have with jQuery is that people get an immediate satisfaction. What do we do besides this?

55:58 – Panelist asks Chris further questions.

56:25 – Chris answers.

Chris: There are highly frequent websites that aren’t being maintained and they aren’t maintainable anymore.

57:09 – Panelist: Prototypes were invented because...

57:51 – Chris: It’s a 20/20 thing.

58:04 – Panelist: Same thing can be said about the Y2K.

58:20 – Panelist: Yes, they had to solve that problem that day. The reality is...

58:44 – Chris: We learned from that whole experience.

1:00:51 – Chris: There was a lot of fluff around it.

1:01:35 – Panelist: Being able to see the future would be a very helpful thing.

1:01:43 – Chris continues the conversation.

1:02:44 – Chuck: How do people get ahold of you?

1:03:04 – Twitter is probably the best way.

1:03:32 – Let’s go to picks!

1:03:36 - Advertisement

Links:

• JavaScript
• So you Learned Java Script, what now? – Article
• WebHint
• Article by James Sinclair
• Clank!
• Angular
• GitHub
• Meetup
• Chris Heilmann’s Twitter
• Chris Heilmann’s Website
• Chris Heilmann’s Medium
• Chris Heilmann’s LinkedIn
• Chris Heilmann
• Chris Heilmann’s GitHub
• Smashing Magazine – Chris Heilmann
• jQuery
• CoffeeScript
• React
• Elixir

Sponsors:

• Kendo UI
• Sentry
• Digital Ocean
• Cache Fly
•  

Picks :

Amiee

• Hacker News -  How to deal with dirty side effects in your pure functional JavaScript

AJ

• KeyBase

Joe

• Framework Summit
• Clank
• ASMR

Charles

• Get a Coder Job Course
• The Iron Druid Chronicles
• Framework Summit

Chris

• Web Unleashed Toronto
• Kurzgesagt
• It Is Just You, Everything’s Not Shit