Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/content/features/deck-browser.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ description: A browser inside the deck, so a talk can show websites without leav

# Deck browser

slide.ng's own, new in 3.0. Press `b`, or the globe button in the bar, and a browser opens as a layer over the current slide. The **Slides** button, `b` or Escape close it and bring back the same slide and click. Its tabs stay loaded while it is closed, so a page you prepared is still there when you come back to it.
slide.ng's own, new in 3.0. Press `b`, or the Chrome button in the bar, and a browser opens as a layer over the current slide. The **Slides** button, `b` or Escape close it and bring back the same slide and click. Its tabs stay loaded while it is closed, so a page you prepared is still there when you come back to it.

## Links on slides

Expand Down Expand Up @@ -69,7 +69,7 @@ The generator warns about other values.
Many sites refuse to be shown inside another page. With `slide-ng dev` on your machine, pages load through a proxy in the dev server's companion, so these sites (GitHub, most large sites) still show inside the deck, and the address field follows the clicks inside a page.

- Each site gets its own address under `localhost`, with a random key for each session, apart from the deck and from the other sites.
- The proxy drops the headers that refuse framing, keeps each site's cookies on its own address, turns off service workers and sends links that open a new window to a new tab.
- The proxy drops the headers that refuse framing, keeps each site's cookies itself and applies their SameSite rules, so a sign-in stays signed in (new in 3.4), turns off service workers and sends links that open a new window to a new tab.
- An address on your computer or your local network, such as `localhost:4200` or a router, loads only when you opened it: from the address field, a slide link, a tile or a bookmark. A page in the deck browser cannot open one.
- Some sites still break through it, for example sign-ins that check where they run. **Open in window** shows the real page.
- Google and some other search engines show a bot check through the proxy, so DuckDuckGo is the default there.
Expand Down
2 changes: 1 addition & 1 deletion src/content/guide/accessibility.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ This page lists what the slides, the presenter and the other pages do for people

## Screen readers

- Each new slide is announced with its number and title, in a polite live region. A title is read as plain text: its markdown marks go, and `$math$` is its TeX, with TeX's one-character escapes undone, so `$400\%$` is "400%".
- Each new slide is announced with its number and title, in a polite live region. A title is read as plain text: its markdown marks go, and `$math$` is its TeX, with TeX's one-character escapes undone, so `$400\%$` is "400%". A `<br>` and `&ngsp;` are a space and a picture is its `alt` text, so `Open Source 101<br>with <img alt="Angular">` is "Open Source 101 with Angular".
- Elements that wait for a click are hidden from screen readers until they show. They are inert too: their links and buttons take no focus, also with the `fade` preset, where they are visible but dimmed.
- The slide, with the bar, is the main landmark of the audience page. The presenter, `/overview` and `/notes` each have a main landmark and a level-one heading, and `/entry`, `/notes-edit` and the notes print page have a main landmark.
- The presenter page has three named regions: Current slide, Next step and Notes. The next-step picture is skipped, so headings are not read twice. Line numbers of code and of Magic Move are skipped too.
Expand Down
Loading