The app on your phone tells you the weather for the next 10 days—that’s the furthest forecasters have ever been able to predict. In fact, every decade for the past hundred years, a day has been added to the total forecast length. But we may be approaching a limit—thanks to chaos inherent in the atmosphere. Staff writer Paul Voosen joins host Sarah Crespi to talk about how researchers have determined that we will only be adding about 5 more days to our weather prediction apps. Also this week, host Meagan Cantwell interviews Trygve Fossum from the Norwegian University of Science and Technology in Trondheim about his article in Science Robotics on an underwater autonomous vehicle designed to sample phytoplankton off the coast of Norway. The device will help researchers form a better picture of the base of many food webs and with continued monitoring, researchers hope to better understand key processes in the ocean such as nutrient, carbon, and energy cycling. This week’s episode was edited by Podigy. Download the transcript (PDF) Listen to previous podcasts About the Science Podcast [Image: Joshua Stevens/NASA Earth Observatory; Music: Jeffrey Cook]

New archaeological evidence suggests the same black plague that decimated Europe also took its toll on sub-Saharan Africa. Host Sarah Crespi talks with Contributing Correspondent Lizzie Wade about diverse medieval sub-Saharan cities that shrank or even disappeared around the same time the plague was stalking Europe. In a second archaeological story, Meagan Cantwell talks with Gustavo Politis, professor of archaeology at the National University of Central Buenos Aires and the National University of La Plata, about new radiocarbon dates for giant ground sloth remains found in the Argentine archaeological site Campo Laborde. The team’s new dates suggest humans hunted and butchered ground sloths in the late Pleistocene, about 12,500 years ago. This week’s episode was edited by Podigy. Download the transcript (PDF) Listen to previous podcasts. About the Science Podcast [Image: Ife-Sungbo Archaeological Project; Music: Jeffrey Cook]

The groundwater of Rockford, Michigan, is contaminated by per- and polyfluoroalkyl substances, chemicals found in everything from nonstick pans to dental floss to—in the case of Rockford—waterproofing agents from a shoe factory that shut down in 2009. Science journalist Sara Talpos talks with host Meagan Cantwell about how locals found the potentially health-harming chemicals in their water, and how contamination from nonstick chemicals isn’t limited to Michigan. Also this week, host Sarah Crespi talks with Shyamnath Gollakota of the University of Washington in Seattle about his work diagnosing ear infections with smartphones. With the right app and a small paper cone, it turns out that your phone can listen for excess fluid in the ear by bouncing quiet clicks from the speaker off the eardrum. Clinical testing shows the setup is simple to use and can help parents and doctors check children for this common infection. This week’s episode was edited by Podigy. Ads on this show: Science Rules! podcast with Bill Nye Download the transcript (PDF)  Listen to previous podcasts. About the Science Podcast [Image: Dennis Wise/University of Washington; Music: Jeffrey Cook]

Chemists have long known how to convert carbon dioxide into fuels—but up until now, such processes have been too expensive for commercial use. Staff Writer Robert Service talks with host Sarah Crespi about using new filters and catalysts to close the gap between air-derived and fossil-derived gasoline.   Also this week, host Sarah Crespi talks with Nitish Padmanaban of Stanford University in Palo Alto, California, about replacing bifocals with “autofocals.” These auto-focusing glasses track your eye position and measure the distance to the visual target before adjusting the thickness of their liquid lenses. The prototype glasses have an onboard camera and batteries that make them particularly bulky; however, they still outperformed progressive lenses in tests of focus speed and acuity. This week’s episode was edited by Podigy.   Download a transcript (PDF) Listen to previous podcasts.   About the Science Podcast  

After two mysterious earthquake swarms occurred under the Sea of Galilee, researchers found a relationship between these small quakes and the excessive extraction of groundwater. Science journalist Michael Price talks with host Sarah Crespi about making this connection and what it means for water-deprived fault areas like the Sea of Galilee and the state of California. Also this week, Sarah talks with graduate student Adrian Baez-Ortega from the University of Cambridge in the United Kingdom’s Transmissible Cancer Group about the genome of a canine venereal cancer that has been leaping from dog to dog for about 8000 years. By comparing the genomes of this cancer from dogs around the globe, the researchers were able to learn more about its origins and spread around the world. They also discuss how such a long-lived cancer might help them better understand and treat human cancers. This week’s episode was edited by Podigy. Ads on this week’s show: Science Sessions podcast from the Proceedings of the National Academy of Sciences Download the transcript (PDF) Listen to previous podcasts. About the Science Podcast

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

On this week’s show, Staff Writer Robert F. Service talks with host Sarah Crespi about manipulating microbes to make them produce building materials like bricks—and walls that can take toxins out of the air. Sarah also talks with Paul Davids, principal member of the technical staff in applied photonics & microsystems at Sandia National Laboratories, about an innovation in converting waste heat to electricity that uses similar materials to solar cells but depends on quantum tunneling. And in a bonus segment, producer Meagan Cantwell talks with Online News Editor David Grimm on stage at the AAAS annual meeting in Seattle. They discuss how wildfires can harm your lungs, crime rates in so-called sanctuary states, and how factors such as your gender and country of origin influence how much trust you put in science. This week’s episode was edited by Podigy. Listen to previous podcasts. About the Science Podcast Download a transcript (PDF).

Coronavirus affects far more than just the lungs, and doctors and researchers in the midst of the pandemic are trying to catalog—and understand—the virus’ impact on our bodies. Staff Writer Meredith Wadman joins host Sarah Crespi to discuss what we know about how COVID-19 kills. See all of our News coverage of the pandemic here, and all of our Research and Editorials here. Also this week, Staff Writer Paul Voosen talks with Sarah about quantum diamond microscopes. These new devices are able to detect minute traces of magnetism, giving insight into the earliest movements of Earth’s tectonic plates and even ancient paleomagnetic events in space. This week’s episode was produced with help from Podigy. Listen to previous podcasts. About the Science Podcast Download a transcript (PDF).

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.

Cham : Springer International Publishing : Imprint: Springer, 2014

Bhatia, Parteek, author

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

Dewey Library - HD30.255.L46 2018

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

Mullen, Matthew, author

Barry, Bernice, author

Christensen, Joseph, author

Kennealy, Shona

Marozzi, Justin, 1970- author

Here are all the records broken by the Aussies on Tuesday.

Their children – a three-year-old son and a four-year-old daughter – survived.

The retired Supreme Court judge said the AK Patnaik committee report that investigated alleged manipulation of the court should be placed before the bench.

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.

The incident occurred on Friday night when the police team was carrying out an anti-insurgency operation.

He has been put on ventilator support.

In the past few days, social media users had pointed to pictures of him looking weak and speculated that he was sick.

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

Online Resource

Rotch Library - GF75.W375 2020

Barker Library - QH70.U62 N485 2019

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 - JK2316.T88 2019

Dewey Library - JF801.S694 2020

Online Resource