Self-driving cars are on their way to the UK, but the journey toward full autonomy still faces challenges.

This CSS code defines a custom font family called “Guardian Headline Full” with multiple font weights and styles. It specifies the font files in different formats (WOFF2, WOFF, and TrueType) and their locations on the server. The font weights range from light (300) to semibold (600), each available in both regular and italic styles.@font-face {
font-family: Guardian Headline Full;
src: url(https://assets.guim.co.uk/static/frontend/fonts/guardian-headline/noalts-not-hinted/GHGuardianHeadline-Bold.woff2) format(“woff2”),
url(https://assets.guim.co.uk/static/frontend/fonts/guardian-headline/noalts-not-hinted/GHGuardianHeadline-Bold.woff) format(“woff”),
url(https://assets.guim.co.uk/static/frontend/fonts/guardian-headline/noalts-not-hinted/GHGuardianHeadline-Bold.ttf) format(“truetype”);
font-weight: 700;
font-style: normal;
}

@font-face {
font-family: Guardian Titlepiece;
src: url(https://assets.guim.co.uk/static/frontend/fonts/guardian-titlepiece/noalts-not-hinted/GTGuardianTitlepiece-Bold.woff2) format(“woff2”),
url(https://assets.guim.co.uk/static/frontend/fonts/guardian-titlepiece/noalts-not-hinted/GTGuardianTitlepiece-Bold.woff) format(“woff”),
url(https://assets.guim.co.uk/static/frontend/fonts/guardian-titlepiece/noalts-not-hinted/GTGuardianTitlepiece-Bold.ttf) format(“truetype”);
font-weight: 700;
font-style: normal;
}

@font-face {
font-family: Guardian Headline Full;
src: url(https://assets.guim.co.uk/static/frontend/fonts/guardian-headline/noalts-not-hinted/GHGuardianHeadline-RegularItalic.woff2) format(“woff2”),
url(https://assets.guim.co.uk/static/frontend/fonts/guardian-headline/noalts-not-hinted/GHGuardianHeadline-RegularItalic.woff) format(“woff”),
url(https://assets.guim.co.uk/static/frontend/fonts/guardian-headline/noalts-not-hinted/GHGuardianHeadline-RegularItalic.ttf) format(“truetype”);
font-weight: 400;
font-style: italic;
}@font-face {
font-family: Guardian Headline Full;
src: url(https://assets.guim.co.uk/static/frontend/fonts/guardian-headline/noalts-not-hinted/GHGuardianHeadline-RegularItalic.woff2) format(“woff2”),
url(https://assets.guim.co.uk/static/frontend/fonts/guardian-headline/noalts-not-hinted/GHGuardianHeadline-RegularItalic.woff) format(“woff”),
url(https://assets.guim.co.uk/static/frontend/fonts/guardian-headline/noalts-not-hinted/GHGuardianHeadline-RegularItalic.ttf) format(“truetype”);
font-weight: 400;
font-style: italic;
}

@font-face {
font-family: Guardian Headline Full;
src: url(https://assets.guim.co.uk/static/frontend/fonts/guardian-headline/noalts-not-hinted/GHGuardianHeadline-BlackItalic.woff2) format(“woff2”),
url(https://assets.guim.co.uk/static/frontend/fonts/guardian-headline/noalts-not-hinted/GHGuardianHeadline-BlackItalic.woff) format(“woff”),
url(https://assets.guim.co.uk/static/frontend/fonts/guardian-headline/noalts-not-hinted/GHGuardianHeadline-BlackItalic.ttf) format(“truetype”);
font-weight: 900;
font-style: italic;
}@font-face {
font-family: Guardian Headline;
src: url(https://assets.guim.co.uk/static/frontend/fonts/guardian-headline/noalts-not-hinted/GHGuardianHeadline-BlackItalic.woff2) format(“woff2”),
url(https://assets.guim.co.uk/static/frontend/fonts/guardian-headline/noalts-not-hinted/GHGuardianHeadline-BlackItalic.woff) format(“woff”),
url(https://assets.guim.co.uk/static/frontend/fonts/guardian-headline/noalts-not-hinted/GHGuardianHeadline-BlackItalic.ttf) format(“truetype”);
font-weight: 900;
font-style: italic;
}

#article-body>div .content–interactive-grid,
.content–interactive>div .content–interactive-grid,
#comment-body .content–interactive-grid,
[data-gu-name=body] .content–interactive-grid,
#feature-body .content–interactive-grid {
grid-column-gap: 0px;
grid-template-columns: 100%;
grid-template-areas: “media” “title” “headline” “standfirst” “lines” “meta” “body”;
}

@media (min-width: 30em) {
#article-body>div .content–interactive-grid figure.element–immersive figcaption,
.content–interactive>div .content–interactive-grid figure.element–immersive figcaption,
#comment-body .content–interactive-grid figure.element–immersive figcaption,
[data-gu-name=body] .content–interactive-grid figure.element–immersive figcaption,
#feature-body .content–interactive-grid figure.element–immersive figcaption {
padding: 0 20px;
max-width: 620px;
}
}

@media (min-width: 46.25em) {
#article-body>div .content–interactive-grid,
.content–interactive>div .content–interactive-grid,
#comment-body .content–interactive-grid,
[data-gu-name=body] .content–interactive-grid,
#feature-body .content–interactive-grid {
grid-template-columns: 100%;
grid-column-gap: 10px;
grid-template-areas: “title” “headline” “standfirst” “media” “lines” “meta” “body”;
}

#article-body>div .content–interactive-grid #maincontent,
.content–interactive>div .content–interactive-grid #maincontent,
#comment-body .content–interactive-grid #maincontent,
[data-gu-name=body] .content–interactive-grid #maincontent,
#feature-body .content–interactive-grid #maincontent {
padding-right: 80px;
}
}

@media (min-width: 61.25em) {
#article-body>div .content–interactive-grid,
.content–interactive>div .content–interactive-grid,
#comment-body .content–interactive-grid,
[data-gu-name=body] .content–interactive-grid,
#feature-body .content–interactive-grid {
grid-template-columns: 620px 300px;
grid-template-areas: “title right-column” “headline right-column” “standfirst right-column” “media right-column” “lines right-column” “meta right-column” “body right-column” “. right-column”;
}

@media (min-width: 71.25em) {
#article-body>div .content–interactive-grid,
.content–interactive>div .content–interactive-grid,
#comment-body .content–interactive-grid,
[data-gu-name=body] .content–interactive-grid,
#feature-body .content–interactive-grid {
grid-template-columns: 140px 1px 620px 300px;
grid-template-areas: “title border headline right-column” “. border standfirst right-column” “. border media right-column” “. border body right-column” “. border . right-column”;
}

#article-body>div .content–interactive-grid .content__standfirst,
.content–interactive>div .content–interactive-grid .content__standfirst,
#comment-body .content–interactive-grid .content__standfirst,
[data-gu-name=body] .content–interactive-grid .content__standfirst,
#feature-body .content–interactive-grid .content__standfirst {
padding-bottom: 0;
}

#article-body>div .content–interactive-grid figure.element–immersive figcaption,
.content–interactive>div .content–interactive-grid figure.element–immersive figcaption,
#comment-body .content–interactive-grid figure.element–immersive figcaption,
[data-gu-name=body] .content–interactive-grid figure.element–immersive figcaption,
#feature-body .content–interactive-grid figure.element–immersive figcaption {
/ Caption styles continue here /
}
}For interactive grid figures with immersive captions in specific content areas, the caption padding is set to 4 pixels at the top and 0 elsewhere.

In various content sections, elements named “lines” and “meta” within interactive grids are positioned in the grid area from row 2 to 5 and column 1 to 2. The “lines” elements have a maximum content height and a top margin of 5 pixels, while “meta” elements have an 18-pixel top margin.

On larger screens (81.25em and above), interactive grids in these sections use a five-column layout with specific widths: 219px, 1px, 620px, 80px, and 300px.

For iOS and Android devices, article headers have customized styles:
– Standfirst text uses specific font families with a medium weight.
– Section kickers are displayed as blocks with the first letter capitalized.
– Keylines have a top padding of 12 pixels.
– Author bylines use bold, serif fonts.
– Image figures have automatic height.
– Paragraphs following atomic elements have no top margin.

Additionally, the Guardian Headline Full font is defined with light and light italic variants, sourced from specific URLs in woff2, woff, and truetype formats.The Guardian Headline Full font family includes various styles and weights, such as regular, medium, semibold, and bold, each available in normal and italic versions. These fonts are hosted online and can be loaded in different file formats like WOFF2, WOFF, and TrueType for web use.@font-face {
font-family: ‘Guardian Headline Full’;
src: url(‘https://assets.guim.co.uk/static/frontend/fonts/guardian-headline/noalts-not-hinted/GHGuardianHeadline-Black.woff2’) format(‘woff2’),
url(‘https://assets.guim.co.uk/static/frontend/fonts/guardian-headline/noalts-not-hinted/GHGuardianHeadline-Black.woff’) format(‘woff’),
url(‘https://assets.guim.co.uk/static/frontend/fonts/guardian-headline/noalts-not-hinted/GHGuardianHeadline-Black.ttf’) format(‘truetype’);
font-weight: 900;
font-style: normal;
}

@font-face {
font-family: ‘Guardian Headline Full’;
src: url(‘https://assets.guim.co.uk/static/frontend/fonts/guardian-headline/noalts-not-hinted/GHGuardianHeadline-BlackItalic.woff2’) format(‘woff2’),
url(‘https://assets.guim.co.uk/static/frontend/fonts/guardian-headline/noalts-not-hinted/GHGuardianHeadline-BlackItalic.woff’) format(‘woff’),
url(‘https://assets.guim.co.uk/static/frontend/fonts/guardian-headline/noalts-not-hinted/GHGuardianHeadline-BlackItalic.ttf’) format(‘truetype’);
font-weight: 900;
font-style: italic;
}

@font-face {
font-family: ‘Guardian Titlepiece’;
src: url(‘https://assets.guim.co.uk/static/frontend/fonts/guardian-titlepiece/noalts-not-hinted/GTGuardianTitlepiece-Bold.woff2’) format(‘woff2’),
url(‘https://assets.guim.co.uk/static/frontend/fonts/guardian-titlepiece/noalts-not-hinted/GTGuardianTitlepiece-Bold.woff’) format(‘woff’),
url(‘https://assets.guim.co.uk/static/frontend/fonts/guardian-titlepiece/noalts-not-hinted/GTGuardianTitlepiece-Bold.ttf’) format(‘truetype’);
font-weight: 700;
font-style: normal;
}

@media (min-width: 71.25em) {
.content__main-column–interactive {
margin-left: 160px;
}
}

@media (min-width: 81.25em) {
.content__main-column–interactive {
margin-left: 240px;
}
}

.content__main-column–interactive .element-atom {
max-width: 620px;
}

@media (max-width: 46.24em) {
.content__main-column–interactive .element-atom {
max-width: 100%;
}
}

.content__main-column–interactive .element-showcase {
margin-left: 0;
}

@media (min-width: 46.25em) {
.content__main-column–interactive .element-showcase {
max-width: 620px;
}
}

@media (min-width: 71.25em) {
.content__main-column–interactive .element-showcase {
max-width: 860px;
}
}

.content__main-column–interactive .element-immersive {
max-width: 1100px;
}

@media (max-width: 46.24em) {
.content__main-column–interactive .element-immersive {
width: calc(100vw – var(–scrollbar-width));
position: relative;
left: 50%;
right: 50%;
margin-left: calc(-50vw + var(–half-scrollbar-width)) !important;
margin-right: calc(-50vw + var(–half-scrollbar-width)) !important;
}
}

@media (min-width: 46.25em) {
.content__main-column–interactive .element-immersive {
transform: translate(-20px);
width: calc(100% + 60px);
}
}

@media (max-width: 71.24em) {
.content__main-column–interactive .element-immersive {
margin-left: 0;
margin-right: 0;
}
}

@media (min-width: 71.25em) {
.content__main-column–interactive .element-immersive {
transform: translate(0);
width: auto;
}
}

@media (min-width: 81.25em) {
.content__main-column–interactive .element-immersive {
max-width: 1260px;
}
}

.content__main-column–interactive p,
.content__main-column–interactive ul {
max-width: 620px;
}

.content__main-column–interactive:before {
position: absolute;
top: 0;
height: calc(100% + 15px);
min-height: 100px;
content: “”;
}

@media (min-width: 71.25em) {
.content__main-column–interactive:before {
border-left: 1px solid #dcdcdc;
z-index: -1;
left: -10px;
}
}

@media (min-width: 81.25em) {
.content__main-column–interactive:before {
border-left: 1px solid #dcdcdc;
left: -11px;
}
}

.content__main-column–interactive .element-atom {
margin-top: 0;
margin-bottom: 0;
padding-bottom: 12px;
padding-top: 12px;
}

.content__main-column–interactive p + .element-atom {
padding-top: 0;
padding-bottom: 0;
margin-top: 12px;
margin-bottom: 12px;
}

.content__main-column–interactive .element-inline {
max-width: 620px;
}

@media (min-width: 61.25em) {
figure[data-spacefinder-role=”inline”].element {
max-width: 620px;
}
}

:root {
–dateline: #606060;
–headerBorder: #dcdcdc;
–captionText: #999;
–captionBackground: hsla(0, 0%, 7%, 0.72);
–feature: #c70000;
–new-pillar-colour: var(–primary-pillar, var(–feature));
}

.content__main-column–interactive .element.element-atom,
.element.element-atom {
padding: 0;
}

#article-body > div .element-atom:first-of-type + p:first-of-type,
#article-body > div .element-atom:first-of-type + .sign-in-ga {
/ No additional styles specified /
}For the first paragraph in various content sections, add a top padding of 14 pixels.

Apply a drop cap style to the first letter of these paragraphs using the Guardian Headline font family, bold weight, 111px size, 92px line height, floated left, uppercase text, with 8px right margin and colored using the specified variable.

Remove top padding for paragraphs following horizontal rules.

Set figure captions for showcase elements to be static, full width, and up to 620px wide.

Make immersive elements span the full viewport width minus scrollbar width.

On screens up to 71.24em wide, limit immersive elements to 978px maximum width and add 10px horizontal padding to captions.

Between 30em and 71.24em, increase caption padding to 20px horizontally.

Between 46.25em and 61.24em, maintain the 978px maximum width for immersive elements.For screens up to 738 pixels wide, adjust the layout for immersive elements by removing left and right margins and aligning them to the left edge.

On smaller screens (under 46.24em), immersive elements shift left with no right margin. For slightly larger small screens (between 30em and 46.24em), increase the left margin and adjust caption padding.

For wider screens (over 61.25em), use a grid layout with defined columns and rows for furniture components. Add a top border to headlines, position meta information with top padding, and style standfirst text with underlined links that change color on hover. Initially, add a top border to the first paragraph in standfirst, but remove it on even larger screens (over 71.25em).

Images in the furniture wrapper have no top or bottom margins and a left margin, with inline elements limited to 630 pixels wide.

On extra-wide screens (over 71.25em), expand the grid and add a decorative line above meta info. Remove top borders from standfirst paragraphs and insert a vertical line before standfirst content.

For the largest screens (over 81.25em), further adjust the grid columns and rows for optimal spacing.The CSS code defines styles for a webpage layout, particularly for article elements like headlines, meta information, and media. Headlines are set to a bold font with specific sizes and maximum widths that adjust on larger screens. Meta sections and social links have borders matching the header’s color, and some elements are hidden on certain devices.

For media, captions are positioned at the bottom with a background color and text styling, and a button to toggle caption visibility is included. On mobile screens, media elements span the full width. The layout also supports dark mode, adjusting colors based on user preferences or device settings.For iOS and Android devices, the first letter of the first paragraph in feature, standard, and comment articles is styled with a secondary pillar color. Article headers are hidden, and furniture wrappers have minimal padding. Labels use a bold, capitalized font in a specific color, while headlines are large, bold, and dark gray. Image figures are also included in the styling.For Android devices, images in standard and comment articles are positioned relatively, with a 14px top margin, no left margin, and a width that spans the full viewport minus the scrollbar width, while maintaining their aspect ratio.

On both iOS and Android, images and their inner elements in feature, standard, and comment articles have a transparent background, match the viewport width excluding the scrollbar, and automatically adjust their height.

The standfirst section in these articles on iOS and Android has 4px top padding, 24px bottom padding, and a negative 10px right margin. Text within uses the Guardian Headline or similar serif fonts, and links are styled with the new pillar color, underlined with a 6px offset, and have no background image or border.For iOS and Android devices, when hovering over links within the standfirst section of feature, standard, or comment articles, the text decoration color changes to the new pillar color.

Additionally, the meta section in these article types has no margin, and elements like byline, author names, and related links adopt the new pillar color for text.

The meta miscellaneous area has no padding, and any SVG icons within it are also styled accordingly.For Android devices, the stroke color of SVG icons in the meta section of furniture wrappers for standard and comment articles is set to the new pillar color.

On both iOS and Android, caption buttons in showcase elements within furniture wrappers for feature, standard, and comment articles are displayed as flex containers. They are centered with 5px padding, measure 28×28 pixels, and are positioned 14px from the right edge.

The article body for feature, standard, and comment articles on iOS and Android has 12px horizontal padding with no vertical padding.

Regular image elements (excluding thumbnails and immersive images) in article bodies on both platforms have no margin, a width calculated as the viewport width minus 24px and scrollbar width, and automatic height. Their captions have no padding.

Immersive image elements in article bodies span the full viewport width minus scrollbar width on both iOS and Android.

Blockquotes marked as quoted in article body prose display a colored marker using the new pillar color on both platforms.

Links within article body prose for feature and standard articles on iOS…For iOS and Android devices, links within article bodies are styled with a primary pillar color, an underline 6 pixels below the text, and no background image. When hovered over, the underline changes to a new pillar color.

In dark mode, article furniture wrappers adopt a dark gray background. Labels within them take on the new pillar color, while headlines and standfirst text use the header border color. Links in standfirsts and author bylines also follow the header border color for text.For iOS and Android devices, apply the following styles to feature, standard, and comment article containers:

– Set the stroke color of SVG icons in the meta section to the new pillar color.
– Use the dateline color for captions in showcase image figures.
– Apply the new pillar color to quoted text in article body prose.
– Use a dark background for main content areas, including article body, interactive content, feature body, and comment body.
– Style the first letter after atomic elements in article bodies and interactive content with appropriate typography.This CSS code targets the first letter of paragraphs that follow specific elements within various article containers on iOS and Android devices. It applies to different sections like the main article body, feature body, comment body, and interactive content areas, ensuring consistent styling for drop caps or initial letter formatting across the platform.For Android devices, the first letter of paragraphs in various article containers (feature, standard, comment) and their specific sections (article-body, feature-body, comment-body, content–interactive) will be styled with a color variable, defaulting to white. This applies to paragraphs following elements like .element-atom, .sign-in-gate, or #sign-in-gate, and includes those with a data-gu-name attribute set to body.

On iOS and Android in comment articles, the standfirst element within the furniture-wrapper has a top padding of 24 pixels and no top margin.

In prose, all h2 headings have a font size of 24 pixels.For iOS devices, the caption button in feature, standard, and comment articles has a top padding of 6px and 5px on the sides. On Android, it’s 4px all around.

In dark mode, text and icon colors adjust for better readability, using lighter shades for follow text and standfirst, while bylines and links adopt a dark mode pillar color.

When the furniture wrapper includes a Guardian organization logo, the branding element is always displayed.

Headlines, standfirst text, and labels in feature, standard, and comment articles on both iOS and Android use a medium font weight (500).

The page background is set to a light pink shade (#fff4f2) for weekend essays, which also applies to article sections and sub-meta backgrounds.

Lines are hidden in the layout.

The furniture wrapper is positioned relatively and uses a grid layout for larger screens, defining specific rows for title, headline, standfirst, meta content, and portrait.

Article headers or title sections have a fixed height of 70px (80px on larger screens) and contain content labels. A decorative book GIF appears in the bottom-right corner, sized at 70x70px or 110x110px on wider screens.

A horizontal line spans the width below the content labels on smaller screens, disappearing on medium to large displays.For screens wider than 81.25em, adjust the furniture-wrapper’s article header and title elements to a height of 125px. Also, set the headline’s top margin to -2px within the same wrapper.

Remove bottom padding from the headline’s inner divs. In the portrait main media headline wrapper, set the height to 100%, position it relatively, hide overflow, and add 24px bottom padding. Ensure that h1 and a elements inside have no maximum width and display a 2px thick underline with a 6px offset on hover.

Set the line height to 115%, font weight to 500, and font size to 36px for h1, a, and byline span elements in the headline wrapper. Increase the font size to 50px for screens wider than 71.25em.

Position the standfirst relatively with 4px top padding, removing it for screens wider than 61.25em and reducing to 2px for those over 71.25em.

Display the branding island in the meta container and position the main media relatively, assigning it to the ‘portrait’ grid area for screens over 61.25em. Ensure the main media’s direct div is positioned relatively.The furniture wrapper styles the main media elements to display as blocks and sets figures to full height with a left margin. Images and captions are sized to fit the viewport minus margins and scrollbar width, with auto height and padding. A decorative frame is added as a background image, positioned absolutely to cover the figure.

For medium screens and above, adjustments include removing the left margin on figures, setting fixed widths for images and captions, and repositioning the frame. The caption button is also moved to the right and bottom with specific spacing.

On larger screens, the layout is refined further: the frame, images, and captions are given narrower widths, margins are reduced or removed, and padding is adjusted for a cleaner look. The caption button’s position is fine-tuned for each breakpoint to maintain alignment and accessibility.

A no-media division is centered within the container, taking up the full width and aligning its content both horizontally and vertically.The CSS code defines styles for a furniture wrapper’s main media section, setting paragraph text to 24px size, bold weight, underlined, and a specific color. For interactive content columns on wider screens, it removes left margin and hides a preceding element. Supporting elements with blockquotes get a pinkish background, while the first letter of the first paragraph is styled lightly. Drop caps are large, uppercase, and floated left with a custom color. Headings are orange-red, 28px (32px on larger screens), and light, but bold if containing strong tags. Figures with iframes also have the pinkish background. On apps, follow buttons are displayed with 14px text, and media elements fit their content. In dark mode, backgrounds are dark gray, and a book image is used as a background for certain headers.For iOS and Android apps, the main media figure uses a white frame background image. The body background is set to white on these devices.

Labels and headlines in article containers have a medium font weight.

In light mode, the background color for iOS and Android is a custom weekend essay background or a light pink shade.

For iOS and Android, the opinion primary color is set to a dark orange, and the byline anchor uses this color.

In dark mode, the weekend essay background becomes dark gray, and the opinion primary color changes to a bright orange. Opinion article bodies and tags on iOS have their background reset.

Article containers on iOS and Android use the weekend essay background color.

On larger screens, the furniture wrapper in article containers uses a specific grid layout with defined columns and rows.

The title and GIF wrapper in article containers is displayed as a flexible row layout with space between elements and relative positioning.For iOS and Android devices, the content labels in the title and GIF wrapper of feature, standard, and comment article containers have a font size of 17 pixels, normal style, bold weight, and 115% line height.

Links within these labels use the new pillar color (defaulting to #c74600) and do not transform text.

GIF containers and their images in these sections are set to 70 pixels in both width and height.

White book GIFs are hidden, while standard book GIFs are only displayed in dark mode.This CSS code hides certain GIF elements with the class “book-gif” on iOS and Android devices for feature, standard, and comment article containers. Instead, it displays white versions of these GIFs with the class “book-gif-white”. It also adds a horizontal line at the bottom of the title and GIF wrapper on these devices, which spans the full viewport width on smaller screens but reduces to half the viewport width on screens larger than 61.25em.For dark color schemes on iOS and Android devices, the background color after the title and GIF wrapper in feature, standard, and comment article containers is set to #606060.

On screens wider than 61.25em, the portrait main media headline wrapper in these article containers for iOS and Android is assigned to the grid area named “headline.”

Headlines, bylines, and byline links in feature, standard, and comment article containers for both iOS and Android have a font size of 36px, normal style, medium weight, and 115% line height.

Additionally, the bylines and their links in these containers maintain the same font properties.For Android devices, the author’s name in comment articles is displayed in red.

In dark mode, the author’s name across all article types on both iOS and Android appears in a darker orange-red.

On both iOS and Android, author profile pictures are hidden in all article layouts.

Article headlines have no bottom margin or padding on both platforms.

Author bylines are shown in italic text, but the actual author names remain in normal font style.

The main media element in articles automatically adjusts its height while maintaining a 4:5 ratio and has a transparent background.For iOS and Android devices, the following styles apply to feature, standard, and comment article containers:

– The main media figure element has full height and no left margin.
– Its inner figure is positioned at the top-left corner.
– The element’s inner container has a transparent background, no padding, and visible overflow.
– Images within these elements are set to the viewport width minus 40 pixels, with 20 pixels left margin and 25 pixels top margin.
– For images directly inside the element’s inner container, the top margin is reduced to 13 pixels.
– Figure captions are also styled consistently across these contexts.For all devices, the figure captions in the main media section will have automatic height.

On iOS and Android devices, captions and their text within feature, standard, and comment articles are displayed as blocks with no maximum height, positioned relatively, and use a custom color for text (defaulting to #999).

For screens wider than 46.25em, figures in these sections on both iOS and Android will have no maximum width limit. A decorative element before each figure will span almost the full viewport width with small margins. Images inside these figures will occupy most of the viewport width with centered margins and top spacing.

On larger screens above 61.25em, similar adjustments apply to the decorative elements before figures.For iOS and Android devices, the main media figure elements in feature, standard, and comment articles have specific styles applied to their pseudo-elements and images.

The pseudo-element’s width is set to half the viewport width minus 20 pixels and any scrollbar width. Images within these elements have a width of half the viewport minus 40 pixels and scrollbar width, with a left margin of 18 pixels, auto height, no padding, and a top margin of 10 pixels.

On larger screens (min-width: 71.25em), the pseudo-element is positioned 4 pixels higher. For even wider screens (min-width: 81.25em), the pseudo-element shifts 20 pixels to the left, while images adjust to half the viewport width minus 90 pixels and scrollbar width, with a left margin of 12 pixels, negative top margin of 10 pixels, and top padding of 21 pixels.

In dark mode, the pseudo-element uses a white frame background image. Additionally, first images in these containers have distinct styling for both operating systems.For iOS and Android devices, the first image in the main media section of feature, standard, and comment articles has specific styling. On smaller screens, the image and its pseudo-element span the full viewport width minus 20 pixels and the scrollbar width, with the image having no left margin and 10px padding.

When the screen width reaches 61.25em or more, the image width becomes half the viewport minus 30px and the scrollbar width, with a 5px left margin, auto height, and 21px top padding. The container’s maximum width is set to 620px, and the pseudo-element adjusts to half the viewport minus 20px and the scrollbar width, filling the container’s height.

At 81.25em or wider, the image width reduces to half the viewport minus 70px and the scrollbar width, with an additional -10px top margin while keeping other properties consistent.For iOS and Android devices, the first image in feature, standard, and comment articles has a left offset of -20px.

On screens wider than 46.25em, the caption button in these articles is positioned 45px from the bottom.

For screens wider than 61.25em, the main media area in these articles is set to a portrait grid area with a maximum width of 620px and automatic height.

All figure elements in these articles are relatively positioned with no top margin. Their inner container is absolutely positioned 15px from the top and 20px from the left, spanning the viewport width minus 40px with automatic height. Images within fill their container completely while maintaining aspect ratio.

The caption button is placed 24px from the right and 20px from the bottom.

On screens wider than 46.25em, the figure’s inner container adjusts its positioning accordingly.For Android devices, the inner figure element in feature, standard, and comment article containers is set to 680px wide with automatic height, positioned 10px from the top and left edges. The caption button in these containers is placed 25px from the bottom on both iOS and Android.

On wider screens (over 61.25em), figures in these article containers adjust their width to half the viewport width minus 20px and the scrollbar width for both iOS and Android.

The standfirst section in these containers has no top margin, with 8px top padding and 10px right padding, and its decorative before element is hidden. Text elements within the standfirst (paragraphs, links, and list items) use a 20px font size, normal style, medium weight, 115% line height, and no bottom padding.

On larger screens (over 61.25em), the standfirst in feature articles…For iOS and Android devices, the standfirst section in feature, standard, and comment article containers is placed in the grid area named “standfirst.”

On these devices, the meta section in the same article types has no top padding and positions the published date relatively. A light gray horizontal line appears below the published date, spanning the full viewport width and extending slightly to the left.

On larger screens (over 61.25em wide), the meta section is displayed in the “meta” grid area, and the line below the published date shortens to half the viewport width.

For even wider screens (over 81.25em), the miscellaneous meta information has no left margin.

In dark mode, the line below the published date changes to a darker gray color.

Additionally, for iOS devices, the meta and keyline sections in feature, standard, and comment articles have a preceding element.For iOS and Android devices, the following styles apply:

– Hide meta and keyline elements before furniture wrappers in feature, standard, and comment article containers.
– Remove rich link elements from furniture wrappers in these containers.
– Eliminate cutout containers in comment headers across all article types.
– Set article and feature body backgrounds to a weekend essay color with a top margin of 6px.
– Style horizontal rules as 1px high, borderless lines with specific dimensions and spacing.
– Format the first letter of initial paragraphs (excluding those containing spans or following a horizontal rule) with distinctive typography: large uppercase letters in headline fonts, floated left with specific sizing and coloring.
– Apply medium font weight to strong or bold text within h2 headings in article and feature bodies.

In dark mode:
– Adjust horizontal rule colors to a darker shade.
– Change the color of drop caps following horizontal rules.
– Remove underlines from paragraph links.

Additionally, set the first letter following an initial atom element in article and feature bodies to medium font weight.The familiar question from the backseat remains just as relevant as a new age of self-driving technology approaches: are we almost there? For Britons, who have long been promised fully autonomous vehicles, the answer is still the same—yes, almost, but not quite.

Another significant milestone in the journey toward driverless cars is once again on the horizon. This week, Waymo, which operates robotaxis in San Francisco and four other U.S. cities, announced it will bring its vehicles to London.

Details are still limited, but the promise is striking: the pioneering Silicon Valley company stated it will introduce its fully autonomous service “across the pond, with plans to offer rides—without a human driver—by 2026. We’re excited to serve Londoners and the city’s millions of visitors next year.”

Those millions might want to keep an Oyster card handy for the London Underground, just in case. The UK government, eager to attract big tech, outlined plans this summer to accelerate the rollout of driverless cars, potentially allowing regulated public trials of robotaxis as early as spring 2026. However, the regulations aren’t fully set yet, and testing may involve a safety driver for some time.

British company Wayve, partnering with Uber, has announced a more measured “plan to develop and launch public-road trials of level 4 fully autonomous vehicles in London.”

While Americans relax and enjoy the self-driving experience, Britain’s path to autonomous cars has been filled with promises that have faded like pedestrians in the rain.In 2018, Addison Lee, once seen as the future of transport, joined forces with Oxford University scientists and promised to launch robotaxis by 2021.

Waymo, which already operates robotaxis in San Francisco and four other U.S. cities, announced plans to bring its vehicles to London. A year earlier, Nissan nearly succeeded in having one of its Leaf cars drive autonomously around Beckton in east London without incident. Chris Grayling, then transport secretary, predicted self-driving cars would be on the market within four years, envisioning small pods navigating autonomously around the O2 in Greenwich. In 2015, a British-designed vehicle, reminiscent of a Sinclair C5 and a Tardis, appeared in a Milton Keynes car park; then-business secretary Vince Cable claimed 100 of them would soon be ferrying passengers around town for £2 per ride.

However, abroad—especially in the U.S. and parts of China—autonomous taxi services are now a reality, making Waymo’s arrival seem more significant than earlier hype or hopes.

In its hometown of San Francisco, Waymo’s driverless cars have become a common sight, moving steadily through the city’s hilly streets at a careful but deliberate pace. Since their full launch in June 2024, they’ve joined electric scooters and municipal buses as part of the urban landscape. Riding in a Waymo has become a must-do tourist experience, much like taking a historic trolley car.

Mayor Daniel Lurie has supported their expansion to help revitalize downtown areas, where the sight of advanced AI-controlled cars passing by homeless people creates a stark contrast.

The converted white Jaguar I-Pace vehicles, equipped with fast-spinning cameras on each wing and one on the roof like a police siren, resemble surveillance equipment. They’re summoned via smartphone apps, similar to Uber or Lyft, but the absence of a human driver and the steering wheel moving on its own serve as reminders of the economic shifts they’re causing.

In 2010, Uber’s launch in San Francisco disrupted traditional taxi employment and introduced precarious gig work. Now, Uber drivers face a new wave of technological change.

According to data cited by the Economist, employment at San Francisco taxi firms grew by 7% in 2024, with pay rising 14%. Lyft CEO David Risher predicted that self-driving taxis would “actually expand the market.”

But not everyone on the front lines shares that optimism. In the Mission district, one Uber driver from Venezuela remarked, “I think I’ve got about a year left in this job.”

For passengers, riding in a Waymo means surrendering to the control of artificial intelligence. After hailing the car via the app, it pulls up gently, displaying the passenger’s initials on a roof-top screen. A tap on the app unlocks the doors, and a welcoming voice reminds riders to buckle up. A screen inside offers a variety of music to listen to behind tinted windows, creating a private space.

Pressing the “start ride” button on the touchscreen, the car merges confidently into traffic. The steering wheel, bearing a “please keep your hands off” sign, turns as if on a ghost train ride.

It doesn’t take long to feel at ease as the car navigates hazards and errs on the side of caution. Screens display scrolling street maps, tracking progress and updating arrival times.The “pull over now” button is a helpful feature that allows passengers to change their original destination, though it only stops when it’s safe to do so.

Riding in a Waymo can make customers feel as though they’re entirely at the mercy of artificial intelligence.

Waymo vehicles have sparked various public reactions. For instance, last month, three of them stalled at a busy intersection in the Marina district, seemingly confused with their lights flashing. Revelers cheered, and one man even performed backflips on the roof of one car. In July, a prankster gathered people on a dead-end street to order Waymos simultaneously, creating a spectacle of 50 driverless cars clustered together. Earlier in 2024, during Lunar New Year celebrations in Chinatown, a Waymo was vandalized, spray-painted, and set on fire.

A similar reception might await driverless taxis in London, even if not directly from black cab drivers. Steve McNamara, general secretary of the Licensed Taxi Drivers Association, commented, “You see kids hacking Lime bikes—how long until it becomes a TikTok trend to ride on a Waymo’s roof?” He claims to be unconcerned, stating, “It’s solving a problem we don’t have. These vehicles might work in San Francisco and LA, but London is unique. I’d like to know how a driverless car will handle Charing Cross Road at 11 p.m. when pedestrians are everywhere. As soon as you spot the Lidar sensor on a Waymo, you’ll step out or pull out in front of it, knowing it will stop.”

Christian Wolmar, author of “Driverless Cars: On a Road to Nowhere,” agrees: “We don’t have jaywalking laws here, and if Google thinks we’ll introduce them for their cars…” Despite experiences in the U.S., he remains doubtful that fully driverless taxis will appear in London next year, saying, “Without a human operator, there’s absolutely zero chance.”

Waymo has announced its plans for London partly to get ahead of public sightings as test cars begin mapping the streets. The company is confident after completing over 100 million autonomous miles in San Francisco—a city known for its hills and chaos—and trials in a dozen other locations.

Operators have long argued that regulation, not technology, is the main hurdle. Even with fast-tracking, there are limits: recent consultation results should allow pilot programs to proceed, though this isn’t confirmed. Waymo still needs to meet requirements from the Department for Transport and Transport for London to start testing, and broader legislation won’t be in place for at least two more years. Insurers, in particular, point out that liability issues remain unresolved.

Similar pilot schemes have left other new transport modes in limbo; e-scooter trials are set to last eight years. Tony Travers, an LSE government professor, believes driverless cars have a better chance: “They have to follow the rules. They might cause congestion, but not the chaos that e-scooters have.”

Even if driverless taxis do arrive, Wolmar questions their impact, asking, “So what?” According to Waymo co-CEO Tekedra Mawakana, the benefits lie in the cars’ “reliability, safety, and magic,” with a strong focus on safety. So far, Waymo vehicles have been involved in far fewer incidents than human-driven cars.Compared to human-driven cars covering the same distance, Waymo also aims to offer a new kind of independence to those who previously had limited options. The Royal National Institute of Blind People praised the announcement, calling it the beginning of technology that allows for safe, on-demand self-driving travel.

Waymo noted that entering the UK market will involve investing in facilities, charging infrastructure, cleaning and support staff, and for now, human specialists behind the wheel.

Transport Secretary Heidi Alexander has highlighted that the upcoming autonomous vehicle revolution could generate 38,000 jobs in the UK. However, professional drivers are clearly more vulnerable: around 300,000 licensed private hire drivers, and eventually another million in trucking and delivery roles. Many of Britain’s 82,000 bus drivers have recently secured substantial pay increases, and the 27,000 train drivers are famously well-paid.

It’s no surprise that polls show UK public opinion is only slightly favorable toward driverless cars, especially amid broader concerns about artificial intelligence replacing human jobs, if not people themselves.

Regulatory approval and legislation are still pending. McNamara remains optimistic, joking, “Who’s going to approve it? If I were aiming for a successful political career, I wouldn’t want my name on that document.”

Frequently Asked Questions
Of course Here is a list of FAQs about selfdriving cars in the UK designed with clear questions and direct answers

Understanding the Basics

1 What exactly is a selfdriving car
A selfdriving car is a vehicle that can sense its environment and operate with little or no human input It uses a combination of cameras radar and lidar to see the road

2 Are selfdriving cars legal on UK roads right now
Yes but with strict conditions Certain vehicles with approved selfdriving features can be used on some motorways but you must always be ready to take back control Fully autonomous cars are not yet legal for public use

3 Whats the difference between assisted driving and selfdriving
Assisted driving helps you drive but requires you to be fully engaged at all times A true selfdriving car is designed to take over the entire task of driving on certain roads allowing you to do other things

Benefits and Opportunities

4 What are the main benefits of selfdriving cars
The key benefits are increased safety greater mobility for those who cant drive and less stress during commutes as you could use travel time for work or relaxation

5 Will selfdriving cars reduce traffic and pollution
Potentially yes They can be programmed to drive more efficiently reducing fuel consumption and emissions If widely adopted as shared services they could also lead to fewer cars on the road overall

6 Could they help older people or those with disabilities
Absolutely Selfdriving technology could offer unprecedented independence to people who are unable to drive a conventional car providing a new form of reliable transport

Challenges and Concerns

7 What are the biggest challenges facing selfdriving cars in the UK
The main hurdles are handling complex unpredictable UK weather and road layouts creating clear laws about who is liable in a crash and ensuring the technology is completely secure from hacking

8 How do they handle bad weather like heavy rain or fog
This is a significant challenge Sensors like cameras and lidar can be impaired by poor weather which is a major area of development Current systems may disengage and require the driver to take over

Related Posts