=== AccessPlus ===
Contributors: vtinnovations
Tags: accessibility, a11y, wcag, alt text, subtitles
Requires at least: 6.4
Tested up to: 6.7
Requires PHP: 8.1
Stable tag: 1.10.2
License: GPL-2.0-or-later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Find accessibility problems, draft fixes with AI review, and publish the
statement and feedback channel accessibility law asks for.

== Description ==

AccessPlus works inside wp-admin. It is not a hosted overlay service.

* **Finds problems two ways.** A fast content scan reads your database directly;
  a page scan runs axe-core against your real rendered pages to catch the CSS and
  DOM issues a database cannot see.
* **Drafts fixes for you to approve.** AI-written alt text, subtitles and
  plain-language rewrites. Every one is a draft. Nothing reaches your site
  without a human approval click, and existing text is never overwritten.
* **Adds a comfort layer for visitors** — contrast modes, font controls,
  text-to-speech, reading aids — all optional, all individually switchable.
* **Produces the two documents most accessibility laws require:** an
  accessibility statement and a public feedback channel.
* **Monitors and documents.** Scheduled re-scans, a severity-weighted score,
  trend history, and an append-only log with undo for every automated write.

= Honest about what this is =

The findings and drafts are suggestions for a human to review. They are not a
compliance certification and not legal advice. The visitor-facing comfort overlay
is a convenience for readers — it does not fix your content, and no accessibility
tool that claims otherwise is telling you the truth.

= A licence is required =

AccessPlus is a licensed product. Activate your V-T.ONE licence key under
**Settings > vtone packages** before use. Until you do, the plugin behaves as
though it were not installed: no scans, no drafts, no overlay, no statement, no
feedback form.

A licence is issued for specific web addresses and applies to the site it was
issued for. `example.com` and `www.example.com` are different addresses, and a
licence for one will not activate on the other — check the address shown on the
licence screen. On a multisite network each site licenses separately.

Licence checks send your licence key, this site's own web address and the product
identifier to V-T.ONE. They send no page content, no media and no visitor data.
Removing a licence switches the features off and leaves every finding, draft,
approval and setting exactly where it was.

= No site content leaves your server by default =

Requests to an AI provider are switched **off** on installation. Until you
deliberately enable them and add an API key, no content of yours is sent anywhere.
When you do enable them, only the item being worked on is sent: one image, one
passage, one snippet — never a page or site dump. Licence checks are separate and
always run; see above for exactly what they contain.

API keys are encrypted with libsodium. The encryption key is stored in a
restricted file outside the database, so a database backup contains nothing
usable.

== Frequently Asked Questions ==

= Will it change my content automatically? =

No. Not alt text, not anything. Generating a description is mechanical, but
deciding whether it is *true of this image* is a judgement, and a plugin that
writes confidently wrong alt text has made the page worse for the exact person it
claims to help — while hiding the problem from the next audit. Every fix is a
proposal you approve or reject, and every automated write can be undone.

= Does the overlay make my site compliant? =

No, and be sceptical of anything that says it does. An overlay helps some visitors
adjust how your site looks and reads. It cannot add a missing label, describe an
image or fix a heading structure. Those are content fixes, which is what the rest
of the plugin is for.

= What does it send to the AI provider? =

Only the single item being worked on, and only when you have enabled external
requests. Errors are logged as a category — authentication, rate limit, transport
— never as a raw provider response, and never with your key. When a request fails,
the provider's own one-line explanation is shown on screen to the administrator who
triggered it, with anything key-shaped redacted; that detail is never written to a log.

= What does a licence check send? =

Your licence key, this site's own web address and the product identifier, to
V-T.ONE only. Nothing else: no page content, no media, no visitor data, no list of
your findings. The address is read from your WordPress settings rather than from the
incoming request, so it cannot be influenced by a visitor.

Opening the licence screen for the first time in an administrator session also
reports the key and the address once, from the server. The key is never sent to your
browser, never written to a log, and never included in any other request.

= What happens when my licence expires? =

The features switch off and the site returns to how it behaves without the plugin.
Nothing is deleted — findings, drafts, approvals, settings and the audit history all
stay exactly as they are, and everything reappears when you renew and choose
**Update licence**. There is no reduced free mode: AccessPlus is Pro-only.

= Do I need Composer or a build step? =

No. The plugin ships ready to run. Composer is used for development tooling only.

= Where is the encryption key, and what if I lose it? =

`wp-content/uploads/vt-access-plus/secret.key`. Include it in backups, exclude it
from version control and deploy bundles. If it is lost or replaced — a server
move, a partial restore — stored API keys become unreadable. The status screen
reports this plainly and you re-enter the key.

== Documentation ==

German is this project's default documentation language; a complete English
version accompanies every document.

* README.md — German, the canonical project README
* README.en.md — English
* Documentation/Installation.md · Installation.en.md
* Documentation/Konfiguration.md · Configuration.en.md
* Documentation/Funktionen.md · Features.en.md
* Documentation/Lizenzierung.md · Licensing.en.md
* Documentation/Sicherheit.md · Security.en.md
* Documentation/Bekannte-Einschraenkungen.md · Known-Limitations.en.md
* Documentation/Fehlerbehebung.md · Troubleshooting.en.md
* Documentation/Entwicklung.md · Development.en.md

== Screenshots ==

1. System status: schema, network setting and secret storage at a glance.

== Changelog ==

= 1.10.2 =
* The preview keeps the outlined element on screen while the page is still loading. A frame
  fires "load" before an embedded PDF viewer, a lazy gallery or a slider has finished, and
  anything of that kind above the element pushes it down after the scroll has already happened
  — a link outlined correctly ended up 988px down a 754px frame, with the bar still saying it
  had been found. The scroll is now repeated for about two seconds, and only when the page has
  actually changed height, so a page that was right the first time is not moved again.
* The page scan says "1 finding resolved" rather than "1 findings resolved". The count is not
  known where the sentence is prepared, so both forms are now sent and the browser picks.
* The overlay's +/− buttons say when they have reached the end of their range: they are
  announced as unavailable and dimmed, and pressing them does nothing at all. They stay
  focusable on purpose — a button that disables itself takes the focus away from the reader
  who just pressed it.
* The findings filter lists every check that has findings, not only the five content checks.
  Page-scan rules like "list" and "region", and the PDF checks, can be filtered for now; they
  were missing because their ids only exist once a scan has recorded them.

= 1.10.1 =
* "Show on page" works as it did in 1.9.8 again: the page opens in the preview screen inside
  wp-admin, with the element outlined in the frame. The change made in 1.10.0 — sending the
  editor to the page itself — is withdrawn, and with it everything it needed on the front end.
  The plugin adds nothing to a public page for this feature again.
* Everything fixed in 1.9.9 is unaffected: the feedback shortcode, dark contrast and its
  handling of photographs, monochrome, and the "Edit PDF" label.

= 1.10.0 =
* **"Show on page" now opens the page itself.** It used to show the page inside a frame on an
  admin screen, which meant looking at your site in a box: the address bar said wp-admin, the
  layout was the width of the frame rather than the window, and every link inside it went
  somewhere you did not mean to go. The click now takes you to the page, scrolls to the element
  and outlines it there — on the real site, at the real width, with the site's own scripts
  running.
* A bar at the top of the page carries what is wrong, what to do about it, which element it is,
  and a link back to the findings list. It can be dismissed to look at the rest of the page, and
  it says plainly when there is nothing to outline — a finding about the page as a whole, an
  element that is hidden, or one that has gone since the scan.
* Findings about images, text, headings, links and anything else the scans report all take the
  same route. Nothing changes about which findings offer the link, or what it is called.
* **A visitor sees none of it.** The outline is added only for a signed-in editor who holds the
  plugin's capability and arrived from the findings list with a valid link, on a licensed site.
  For anybody else the page is byte-for-byte what it always was; a page carrying the bar is also
  kept out of every page cache, so it can never be served to somebody else.

= 1.9.9 =
* **[vtap_feedback_form] no longer takes the page down.** The form's hidden action field named a
  class PHP could not find — the name was written without its namespace, so it resolved inside
  the feedback namespace instead of the admin one. The page white-screened, REST returned 500,
  and the page could not be opened in the editor either, because rendering it is part of
  loading it. One missing import; it has been there since 1.1.1, because nothing ever rendered
  that form. There is now a test that does, and a second that checks every class reference in
  the plugin resolves at all.
* **Dark contrast is readable.** A page whose background comes from `body` has that background
  painted by the browser across the whole window, outside the filter that inverts the page — so
  the background stayed white while the text inverted to near-white. Measured at 1.36:1, where
  4.5:1 is the minimum for body text. It now measures 15.46:1.
* **Dark contrast leaves photographs alone.** The filter that restores media was `invert` plus
  `hue-rotate`, and a `hue-rotate` applied twice does not return the original colour: a
  saturated red came out washed to rgb(173,63,63). Both halves are now plain `invert`, which
  cancels exactly — the same red measures rgb(230,20,20) again. The page's own hues invert as a
  result, so a blue heading comes out orange; that is the cost of photographs that are still
  the colour they were, and this mode exists for readability rather than for brand colours.
* **Monochrome greys the page background too.** Same cause as the dark-mode background: a
  coloured page stayed exactly as colourful with monochrome on as off. Epilepsy-safe mode turns
  monochrome on, so this mattered beyond the setting itself.
* **A PDF finding offers "Edit PDF" rather than "Edit image".** The link always led to the right
  screen; only the wording was wrong.

= 1.9.8 =
* "Show on page" now outlines a PDF. Every finding about an uploaded file was looked for as an
  image — the only kind of attachment the preview had ever been asked about — so a PDF sitting
  in plain sight on the page was reported as "this element is no longer on the page, so the
  page has changed since the scan". Nothing had changed; the preview was looking for an <img>.
* All four shapes a PDF reaches a page in are recognised: the embedded viewer and the link that
  WordPress's File block writes together, and the <embed> or <iframe> a page builder uses. Where
  a page has both, the viewer is outlined, because that is the part a reader sees.
* A PDF that no page on the site shows is offered as the file itself, and the preview now says
  so instead of claiming the page has changed. A browser opens a PDF in its own viewer, where
  there is nothing for any outline to point at.
* Images are unaffected.

= 1.9.7 =
* The "how to fix this" text of a page-scan finding is now translated as well. 1.9.6 translated
  the finding's heading but not the advice under it, so the Show-on-page banner and the detail
  in the Findings list still opened with "Fix all of the following:" under a German heading.
* The cause was the shape of the stored text. axe writes that advice as a header and one line
  per check; the row stores it with its line breaks collapsed into spaces, and 1.9.6 translated
  it a line at a time — of which a stored summary has exactly one, matching nothing. It is now
  translated phrase by phrase, which works on the stored text and on axe's original alike.
* Findings already in the database are covered: the translation happens when a row is read, so
  nothing needs re-scanning.

= 1.9.6 =
* Page-scan findings are now shown in the reader's language. The Findings list mixed the two:
  a content-scan finding appeared in German while a page-scan one, beside it in the same list,
  appeared in English. Page-scan findings are written by axe-core in the browser and stored as
  finished prose with nothing to translate them by, so they stayed in the language the scanner
  speaks.
* The key was there all along — the axe rule id, which every one of those findings already
  stores. axe-core publishes its own translations under exactly that key, so the finding's text
  and its "How to fix this" detail are now said in the language of whoever opens the screen.
* The stored row is not rewritten, which is the point: it keeps the scanner's wording, and two
  administrators who do not share a language read the same database each in their own. This is
  how every other finding on that screen already worked.
* A rule or a line the catalogue does not cover stays in English rather than disappearing, and
  a site in a language axe has no translation for is exactly as it was.

= 1.9.5 =
* The page scan no longer reports the WordPress toolbar as findings on your site. The scan
  drives a browser signed in as you, so the page it loads carries the toolbar a visitor never
  receives — and its markup is WordPress's, not yours. On a small site those findings
  outnumbered the real ones. Nothing a visitor can see is excluded, this plugin's own overlay
  widget included.
* Page names in the scan progress line read correctly. WordPress returns a title with its
  typographic punctuation as HTML entities, and the progress line is plain text, so a title
  containing a dash or an apostrophe was shown as "&#8211;".
* Content scaling no longer pushes the page sideways. Everything sized in per cent, pixels or
  ems reflows under it; a length written in viewport units does not, so a full-width header
  came out wider than the screen and its right-hand end was unreachable. Those elements are
  now measured and capped, and the cap is lifted the moment scaling is turned off.
* The comfort panel's focus trap counts every kind of control. It knew about buttons, selects
  and links, so a text field or anything with its own tab order was not treated as a stop and
  Tab could leave the open dialog.
* German is complete. The entire licence surface — about a hundred strings across activation,
  renewal, removal and every licence state — had no German at all, and neither did the history
  screen. The README described this as a few strings added in 2026; it was the whole surface.
* Plural messages are translated. WordPress looks a plural up by both of its forms together,
  and the catalogues stored each form as a separate entry, so every counted message in the
  plugin fell back to English for any number but one — in German catalogues that already
  contained both translations. All fourteen are now stored as real plural entries.
* The PDF scan reports its result as sentences that can be translated, instead of one string
  with "PDF(s)" and "issue(s)" in it. A bracketed s cannot express German, let alone a
  language with more than two plural forms.
* The Subtitles screen is called Subtitles, matching the menu item that leads to it. It read
  "AI Subtitles" while the menu said "Subtitles".
* The catalogue build no longer breaks on a character containing the byte 0x85 — "★" among
  them — which it treated as a line ending.

= 1.9.4 =
* The comfort overlay now stays inside the screen in all six of its positions, on every
  viewport we can measure. Its panel is anchored 80px in from the edge the button sits on,
  but the height it was allowed on a phone and on a short screen did not subtract that
  offset — so the panel ran past the far edge, taking the heading and its close button off
  the top at the bottom positions and the "Reset all" button off the bottom at the top ones.
  Because the panel is fixed, nothing could be scrolled back into view.
* The middle-left position gave its panel the wider width allowance meant for a layout only
  the middle-right position used, so on a phone the whole right-hand column of switches sat
  off the side of the screen.
* Every offset is now derived from one set of values, so the button's inset and the panel's
  height cannot drift apart again.
* The panel measures the viewport with `dvh` where the browser supports it, so a mobile
  browser's own toolbar no longer counts as space the panel can use.
* The two top positions now sit below the WordPress admin bar for a logged-in editor instead
  of on top of it, and the widget keeps clear of a notched phone's safe area.

= 1.9.3 =
* The plain-language switch now rewrites the passages it was skipping. A passage is matched
  by its text, and a paragraph containing a link, bold text or a line break is several
  pieces of text in the browser rather than one — so those paragraphs were passed over while
  the plain ones around them were rewritten. Turning the switch on visibly did nothing to
  much of a page.
* Passages are also matched through WordPress's own typographic conversion, which turns
  straight quotes into curly ones, `--` into a dash and `...` into an ellipsis. Any passage
  containing an apostrophe used to miss for that reason alone.
* A rewritten passage loses inline links inside it, which is inherent to swapping a whole
  passage for a rewrite of that passage. Passages containing an image, an embed or a form
  control are left alone rather than rewritten.
* The floating button now names what the next click does — the register when the original is
  showing, "Original text" when a rewrite is. It previously named the register either way,
  so nothing indicated the page was already simplified or how to get back.
* Double-clicking the button no longer cycles twice and lands back where it started, and a
  browser that refuses the cookie now gets the rewrite applied to the page it is on instead
  of a button that does nothing.
* Passages rendered by the theme after the page loads are picked up by a second pass.

= 1.9.2 =
* "Reset all" in the comfort overlay now also puts the reader back on the original text.
  It cleared every display preference but left a plain-language register switched on, so
  the one control that changes the words on the page was the one thing reset did not
  undo. Picking "Original text" from the panel still works exactly as before.

= 1.9.1 =
* The Area picker on the Plain language screen now lists pages as well as posts. It was
  filtering on the post body, which is the right rule for the checks that read heading
  structure and link text and the wrong one here — plain language also reads the custom
  fields where page builders and theme elements keep their copy. On a site built that way
  a page has an empty body and plenty of text, so the picker offered the posts and hid
  exactly the pages most in need of simplifying.
* A site-wide run now reaches those pages too, so "All content" and picking one page agree
  about what exists.
* Entries are grouped by type — Pages, Posts, and any custom type under its own name — so
  one can be told from another at a glance. Pages are listed first.
* Each type is listed separately rather than sharing one overall cap, so a plugin with
  hundreds of entries of its own can no longer push pages and posts out of the control.

= 1.9.0 =
* Plain language can now be pointed at a single page. The screen has an **Area** picker —
  one page, or all content across the site — alongside the register and the language, and
  everything below it follows that choice: the drafts you review, the counts on the status
  tabs, and what the Rewrite button works on.
* This was a real limitation rather than a missing convenience. Drafting walked the site
  in id order and stopped at a scan limit, so on a site of any size the later pages were
  never reached, and there was no way to ask for one page however many times you ran it.
* The language box lets you draft in a language other than the site's first configured
  one, without changing that setting for everything else.
* Your choice stays put as you work — switching status tabs or turning a page keeps the
  same area — and the address bar reflects it, so a particular page's drafts can be
  bookmarked or passed to a colleague.

= 1.8.0 =
* New **History** screen under AccessPlus. Every change the plugin has applied to your
  site is listed newest first — what was written, to which item, what was there before,
  who did it and when — and any of them can be undone from there. The trail itself has
  been recorded since the first automated write shipped; until now the only way to see
  an entry was to find the one item it belonged to on the Alt text or Subtitles screen,
  and older writes could not be reached at all.
* Undo from the History screen behaves exactly as it does elsewhere: it restores the
  previous value and returns the draft to pending, and it refuses if the value has been
  changed since, so it can never overwrite an edit made by hand. A previous value that
  was absent is restored as absent rather than as an empty string.
* Long values are excerpted in the list, with the rest behind a disclosure. A subtitle
  entry records the whole caption file, and a page of those shown in full would take a
  long time to load and be no easier to read.
* Undo still works when the draft behind a change has since been deleted. The recorded
  entry holds everything needed to put the site back, and refusing because the draft was
  tidied away would leave content applied with no way to reverse it.

= 1.7.2 =
* "Hide images" now hides the images declared in a stylesheet. It only ever reached
  images written into an element's own `style` attribute, which is almost none of
  them, so a reader who asked for no images was still shown every hero photograph,
  banner and tiled backdrop on the page. Backgrounds, list markers, border images,
  masks and pictures used as generated content are all covered now, wherever they
  are declared.
* Gradients are deliberately left alone. A gradient and a photograph are the same CSS
  property, so the two are told apart by reading what each element actually resolves
  to — hiding pictures should not strip a site's colour scheme.
* Inline SVG is now hidden too, along with image inputs and image objects. An icon or
  logo drawn as markup was never an image as far as the old rule was concerned.
* Images that arrive after the page has loaded — lazy-loaded galleries, slider
  slides, deferred backdrops — are caught as they appear rather than being missed by
  a single pass at load.
* The widget's own panel is exempt, so nothing in the control a reader is operating
  can vanish underneath them.

= 1.7.1 =
* Switching off one of the overlay's accessibility modes no longer switches off
  another one that was on. Epilepsy-safe mode and ADHD-friendly mode both stop
  animations, and turning either one off removed that shared setting outright — so
  the mode left on no longer matched its own definition and its switch flicked back
  to off with it. Worse, the settings that mode had applied stayed applied, leaving
  a reader looking at a greyscale page with every switch reading off. A setting two
  modes share is now kept as long as either of them is on.

= 1.7.0 =
* A licence change sent by V-T.ONE can now withdraw entitlement as well as grant or
  renew it. Previously a withdrawal was refused as though it had failed its signature
  checks — it had not; it was correctly signed and said the site was no longer
  entitled — so the one message that needed to arrive was the one that could not.
  A withdrawal now takes effect the moment it arrives, switches the protected
  features off, and leaves findings, drafts, captions, settings and the audit trail
  untouched.
* A licence that moves to another website now releases the site it left. The losing
  site is told, in the same authenticated message, that the address it was licensed
  for is no longer one of the licence's addresses.
* A withdrawal survives a restored backup. The record of the highest licence revision
  a site has accepted is kept outside the stored licence file, so putting an older
  copy of that file back — or deleting it, or removing the licence and activating
  again — no longer restores entitlement that V-T.ONE has withdrawn.
* A licence can carry its own deadline for re-checking with V-T.ONE, honoured on the
  daily scheduled run. If V-T.ONE cannot be reached the licence keeps working for a
  further grace period that is also part of the licence, and only then falls back to
  "Needs re-checking" — so a brief outage changes nothing, while a site that never
  checks in does not stay licensed indefinitely. Licences issued without a deadline
  are unaffected.
* Two new licence states appear on the licence screen, "Withdrawn" and "Needs
  re-checking", kept distinct from "Expired" and "Cannot be checked" because each
  calls for something different from the site's administrator.

= 1.6.20 =
* A revised subtitle now reaches readers immediately. Approving an edited transcript
  rewrites the caption file at the path its naming convention fixes, so the URL in the page
  was identical before and after the edit — and nothing between the file and the reader had
  any way to know it had changed. The browser answered the next request from its own cache,
  as did any CDN in front of the site, and the video went on showing the old text while the
  new text sat correctly on disk. The caption URL now carries a version token that changes
  with the file, so a revision cannot be served from a cache keyed on the old one.
* The caption endpoint sends an ETag and a Last-Modified, and answers a browser that
  already holds the current version with an empty 304 rather than the file. Replaying a
  video is cheaper than before; a corrected caption arrives sooner.

= 1.6.19 =
* "Readable font" and "Dyslexia-friendly font" are now mutually exclusive: turning one on
  turns the other off. Both rewrite the page's font family with the same weight, so with
  both on the winner was whichever rule sits later in the stylesheet rather than the one
  the reader had just asked for — a switch that read as on and did nothing.
* A pair saved from an earlier version is reduced to one the next time the page loads, and
  Low-vision mode, which turns the readable font on as part of its bundle, no longer
  collides with a dyslexia font the reader already had on.

= 1.6.18 =
* The panel now looks the same on a desktop as it does on a phone. The phone's padding,
  text size, row spacing and stepper spacing are now the panel's at every width — the
  layout the phone arrived at turned out to be the better one for a 340px desktop panel
  too, which is barely wider than a phone screen.
* The link navigator takes a line of its own everywhere: its label on the first line, the
  dropdown below it. A dropdown of link text needs more width than a switch or a stepper,
  and beside a label it either squeezed the label to a few characters or ran off the edge of
  the panel, which clips it.
* The mobile block now holds only what is genuinely about a phone: hyphenation for long
  German compounds, the panel's height limit, and keeping a row of three buttons together.

= 1.6.17 =
* A label and its control now stay side by side on every screen size, not only on a phone.
  "Inhaltliche Skalierung" and its stepper had started wrapping onto two lines in the
  desktop panel, because a flex row wraps on its items' natural widths and 1.6.16's
  fixed-width value box was enough to push the pair past the panel's inner width. The row
  no longer wraps; the label shrinks and wraps its own text instead, which is what a phone
  has done since 1.6.9.
* The rule now lives in one place rather than being repeated per screen size, so the two
  copies cannot drift apart.

= 1.6.16 =
* The minus and plus buttons of a stepper no longer move when its value changes. The value
  reads "Standard" at the default and "+1" or "-2" either side of it, and its box was sized
  to whatever it happened to say — so the buttons closed in and the whole group slid along
  the row the moment you pressed one, which made pressing the same button twice a game of
  chase. The box now has a fixed width, on every screen size and at every value.

= 1.6.15 =
* On a phone, a widget at the middle left or middle right reserves 40px beside the toggle
  button rather than 88px, and a widget at the middle right sits 14px inside the toggle. At
  320px the panel was left 232px, which is what made every row inside it a squeeze; it now
  runs from 10px to 30px off the two edges, with nothing cut off at any width.
* Wider screens are unaffected, and a widget at the middle left keeps its own offset.

= 1.6.13, 1.6.14 =
* Superseded by 1.6.15, which is these two arrived at in one step. Neither is worth
  deploying on its own: 1.6.13 moved the panel further than intended, and 1.6.14's wider
  cap without the matching offset let the left end of every label run off a narrow screen.

= 1.6.12 =
* Findings are now shown in the language of whoever is reading them. Set your language under
  Users > Profile, or change the site language, and the messages and suggested fixes follow
  immediately — no re-scan needed.
* Why they did not before: the text was translated by the scan that *wrote* the finding and
  stored as finished prose, and nothing translated it again. Worse, which language that was
  depended on where the scan ran, because WordPress resolves the locale per context: a scan
  started from wp-admin used the signed-in user's own language, while the nightly scheduled
  scan and the page-scan ingest used the site language. A German site with an
  English-speaking administrator therefore got English rows from the button and German rows
  from the nightly scan, each overwriting the other.
* Message and suggestion are now stored as the untranslated original plus the values that go
  into it, and translated when a screen renders them. Composed messages — a post title
  inside a message, where the title may itself be "Untitled (#12)" — translate all the way
  through.
* **Findings recorded before this release keep the language they were written in until a
  scan refreshes them.** Those rows hold only the finished text and nothing can recover
  which words were the placeholders. Run a content scan once and they are rewritten.
* Page-scan findings remain in English: their text comes from axe-core through the browser,
  already written, with no key to look up. Documented as a limitation in both languages
  along with the element pointer, which is usually raw data and is not translated either.
* The findings search now looks in both the stored wording and the untranslated original, so
  a search finds a finding whichever of the two languages the words came from.
* Database schema version 3. The columns are added automatically on upgrade.

= 1.6.11 =
* On a phone, the text-alignment row now takes two lines: the label on one, its three
  buttons on the next. It is the only row whose control is three separate buttons, and
  beside them the label was left a column a few characters wide — "Textausrichtung" broke
  across four lines. Every other row still keeps its label and control side by side, and
  wider screens are unaffected.

= 1.6.10 =
* Removed the "Go" button from the link navigator. The dropdown is the control: choosing a
  link still follows it, and with a keyboard Enter still does — which is what Enter does on
  a link anyway. Nothing else about the navigator changed.
* The mobile layout fix from 1.6.9 is now confined to screens 480px and narrower, which is
  all it was ever meant to cover. Wider screens are back to exactly the layout they had
  before 1.6.9.

= 1.6.9 =
* Fixed the panel's layout on a phone. A label and its control stay on one line and it is
  the label's text that wraps, instead of the row breaking apart and dropping a toggle
  switch onto the next line hard against the left edge, where it read as a separate control
  belonging to nothing. Whether a given row broke depended on how long the translation
  was, so it showed in German and not in English: "Sehbehinderten-Modus" fitted and stayed
  put, "Epilepsie-sicherer Modus" did not.
* The steppers keep their three parts together on a narrow screen — tighter spacing and a
  value sized to its own text, rather than the minus, the value and the plus wrapping away
  from each other.
* The link navigator's dropdown and its Go button are now one group. On a phone that pair
  cannot share a line with a label, so this row alone still stacks — deliberately, with the
  label on its own line and the controls right-aligned beneath it. On a desktop the group
  no longer pushes the row into wrapping, which the button added in 1.6.8 had started to do.

= 1.6.8 =
* The link navigator now goes to the link you choose. It used to scroll the link itself
  into view and focus it, which left you looking at the link you had just found and no
  nearer the thing it points at.
* A link into the same page goes to that section, and focus moves to the section as well,
  so a screen reader or the keyboard arrives there too rather than staying where it was —
  a browser scrolls to a fragment but only moves focus if the target happens to be
  focusable, which a section or a heading is not.
* The link itself is clicked rather than the address being assigned, so target="_blank",
  downloads, a theme's smooth scrolling, and the handler that opens the accordion or tab
  being linked to all behave as they normally would.
* With a mouse or a touch picker, choosing a link is enough. With a keyboard, arrowing
  through the list previews and Enter or the new "Go" button follows — a browser reports
  every option arrowed past as a choice, so navigating on that would carry you off the page
  while you were still reading the list.
* The list is rebuilt each time the panel opens, so links added after the page loaded — a
  menu, a section loaded in — are offered, and every entry still stands for the link it was
  built from.

= 1.6.7 =
* AccessPlus now excludes its own front-end files from minification, concatenation,
  deferral and delayed execution in WP Rocket, Autoptimize and LiteSpeed Cache, and marks
  its tags data-no-minify, data-no-optimize, data-noptimize and data-cfasync="false".
* Why this is needed: an optimisation plugin can serve its own rewritten copy of the widget
  script and never regenerate it. On a live site WP Rocket was serving a minified copy a
  day older than the file on disk, so two releases of fixes had never once executed in a
  browser — while the plugin reported the new version and the file on the server was
  correct. Nothing inside WordPress could show it.
* **If you are updating from an earlier release, clear your optimisation plugin's cache
  once, including its minified JavaScript.** In WP Rocket that is "Clear cache" plus "Clear
  used CSS and minified files"; the page cache alone leaves the rewritten copy in place.
  A service-worker accelerator such as Baqend Speed Kit needs purging too.
* Delayed JavaScript execution is excluded for a second reason: it holds the widget back
  until the visitor's first interaction, so a reader who saved Epilepsy-safe mode would
  watch the page — sliders included — animate until they touched it.
* Documented the symptom, how to confirm it and how to clear it in Troubleshooting, in both
  languages.

= 1.6.6 =
* Fixed: switching a comfort mode back off left slider text collapsed instead of restoring
  it. Removing the overlay's own font size is not the same as putting back the slider's:
  both write to the same inline style, so the slider's value was already gone, and removing
  the override left the text with no size at all — inheriting the page default while the
  slider kept the letter spacing it had calculated for a much larger size. The slider is
  now asked to lay itself out again whenever an override is released, immediately rather
  than on a delay, so there is no flash of collapsed text either.
* A plain `resize` event is not enough for this and never was: Slider Revolution, Swiper
  and Slick all remember the last width they measured and do nothing when it has not
  changed — which, after a mode toggle, it has not. Each is now asked to redraw through its
  own API, alongside the resize event that covers everything else.
* A redraw no longer restarts a slider that Epilepsy-safe or ADHD-friendly mode is holding
  still.

= 1.6.5 =
* Fixed: slider headings collapsed on top of themselves while a comfort mode was on. A
  slider computes its font size, letter spacing and absolute position from each other in
  JavaScript and rewrites them on every resize. The font stepper was overriding just the
  size, with `!important`, so the slider could never correct it — and when the setting was
  restored from an earlier visit it was applied before the slider had even started, so the
  size captured was the page's default rather than the slider's. A 61px heading with -5px
  tracking ended up near 16px with the tracking untouched, and its letters overlapped.
  Slider Revolution, Swiper, Slick, Owl Carousel and Flickity layers are now left to their
  own scripts, and anything the stepper had already pinned is released.
* Epilepsy-safe mode and ADHD-friendly mode now actually stop sliders. Both switch off
  animation, but a stylesheet can only stop CSS animation — a slider animates by writing
  inline transforms from JavaScript on every frame, so the largest moving thing on most
  pages carried on moving in the mode whose whole purpose is to stop it. Slider Revolution,
  Swiper and Slick are stopped through their own APIs, re-asserted over sliders that start
  late, and only motion the overlay stopped is started again afterwards. Any other script
  can join in by listening for the `vtap-overlay-motion` event on `document`.
* Every comfort setting now ends by telling script-driven layouts to measure again, so a
  slider that sized itself before a filter, a zoom or a font change was applied is no longer
  working from a stale measurement.
* Documented two limits that cannot be fixed from a stylesheet: a filter mode (monochrome,
  dark contrast) makes a theme's fixed-position header scroll away with the page, and a
  slider library other than the five named above is not recognised.

= 1.6.4 =
* "Show on page" now takes you to the page an image is actually on, in far more cases.
  The lookup already found featured images and images inserted through the editor, but
  it only read post content — so an image placed by a page builder or a custom field
  (Elementor, Divi, WPBakery, Beaver Builder, ACF, most theme options) was never
  located, and the button opened the image file on a blank tab instead of the page.
  Post meta is now searched as well, and the image is outlined on the page as usual.
* The attachment id on its own is deliberately not searched for. A meta row holding
  just `42` could be a menu item, a price or a sort order, and a page found that way
  would have nothing to do with the image — you would be sent somewhere unrelated and
  told the image was missing from it. An image referenced by nothing but its id is
  still not located, and the file itself is offered, as before.

= 1.6.3 =
* Fixed: confirming or dismissing a finding did nothing and left you on a blank page.
  The findings table submits to WordPress's own bulk-action field, which overwrote the
  field the form used to route on, so the decision never reached the handler. Row
  actions and bulk actions both work again; nothing about how they behave has changed.
* "Show on page" no longer claims to have highlighted something you cannot see. A
  finding about the page as a whole — a viewport that blocks zooming, a missing page
  title, a missing language attribute — lives in the page's head, where no browser
  draws anything. Those used to report "element highlighted below" and show an
  ordinary page with no box on it anywhere.
* Where the element is present but not rendered — hidden, collapsed inside a menu, or
  shown only at another screen width — the part of the page containing it is outlined
  instead, and the banner says that is what happened.
* The link now says where it goes: "Show on page" outlines an element, "Open the page"
  opens a page with nothing to outline, "Open the PDF" opens a file. One label for all
  three promised an outline that two of them could not draw.
* The preview banner now carries the fix as well as the problem, so what to change is
  readable while looking at the thing that needs changing, and offers a way back to
  the findings list.
* Every status message on that screen has been rewritten to say what happened and what
  it means for you, and all of them are translated into German.
* Added tools/i18n-build.php, which compiles the .po catalogues to the .mo files
  WordPress reads and lists any translatable string that has no translation.

= 1.6.2 =
* The comfort overlay panel now has a close button beside its heading. Escape and
  a second click on the toggle already closed it, but neither is discoverable — a
  reader who did not know either had no visible way to dismiss a panel sitting over
  the page.
* Opening the panel still lands on the first setting rather than on the close
  button, and closing returns focus to the toggle, which is where Escape already
  returned it. The button is reachable by keyboard as the first stop backwards from
  the first setting.

= 1.6.1 =
* Rebuilt the documentation. German is now the project's default documentation
  language: README.md is German, README.en.md is the complete English version, and
  a Documentation/ folder carries installation, configuration, features,
  licensing, security, known limitations, troubleshooting and development guides
  in both languages.
* Replaced the previous docs/ folder. Two of its documents described internal
  structure at a level of detail that belongs in a repository and not in a shipped
  package. The operational content customers actually need has been rewritten at
  administrator level; the internal detail has been removed.
* Licensing is now documented at the level an administrator operates it: the
  states, what each one means, what to do about it, and exactly what each licence
  operation transmits. How enforcement is implemented is no longer described.
* Standardised the file headers across the first-party source files with the
  project's Composer metadata. No functional code changed.
* No feature behaviour changed in this release.

= 1.6.0 =
* AccessPlus now requires an activated V-T.ONE licence. Activate under Settings >
  vtone packages. Every feature is gated server-side; an unlicensed site behaves as
  though the plugin were not installed, and no findings, drafts, approvals or
  settings are touched.
* Licences are issued for exact web addresses and are cryptographically verified
  before they are applied. A licence for one address does not activate on another,
  including the same domain with and without "www".
* Licence state is replaced in a single operation, so a failed update leaves the
  working licence in place rather than half-applied.
* A renewal or a change can now be delivered to the site without an administrator
  logging in. Only fully authenticated messages are accepted, and a replayed
  message is refused.
* Corrected an inaccurate claim in the previous documentation: the plugin's
  external-requests switch governs what is sent to an AI provider, and never
  governed licence checks. What the licence exchange sends is now documented
  precisely — the key, this site's address and the product id, and nothing else.
* Each site in a multisite network now licenses independently.

= 1.5.2 =
* Tidied the language instruction for English sites. Covering every language in one sentence
  meant it had to carry its own exception - "do not answer in English unless English is that
  language" - which is logically fine and reads as a riddle. English now simply gets the
  requirement stated once; other languages keep the explicit "not English" clause.

= 1.5.1 =
* Fixed: AI drafts sometimes came back in English even though Content languages was set to
  German. The prompts passed the raw language code, so the model was told to write "in the
  language de" - a real instruction, but a weak one. In the same run of three images it would
  produce one German description and two English ones.
* Prompts now name the language in full, including in its own language ("German (Deutsch)"),
  and repeat the requirement as the final sentence rather than only the first. This applies to
  all three AI features: alt text, accessible names and plain-language rewrites.
* Regional variants that change the written form are now distinguished too, so a site set to
  pt-BR gets Brazilian Portuguese and zh-Hant gets Traditional Chinese, rather than whichever
  the model defaults to.

= 1.5.0 =
* The whole admin interface is now available in German. Previously only the visitor-facing
  comfort overlay was translated, so a German site still had English settings, findings,
  dashboards and messages. All 590 strings the plugin can show are now translated: every
  screen, every button, every notice and every explanation.
* It follows your WordPress site language automatically (Settings - General - Site Language),
  and a user who sets a personal language on their own profile gets that instead. Any other
  language falls back to English exactly as before. There is no setting to configure.
* Covers de_DE, de_DE_formal, de_AT and de_CH.
* The reader-facing overlay wording is unchanged - it is still taken verbatim from the
  original Contao product.

= 1.4.7 =
* The comfort overlay now sits above other popups. Its stacking order was well below what
  consent banners, chat bubbles and some sticky headers use, so those could cover the panel
  while a reader was using it — with no way to get underneath. It now uses the same values
  as the original Contao product, near the top of the range browsers allow.
* Deliberately not the absolute maximum: a site that has something which genuinely must come
  first, such as a consent dialog that has to be answered, can still place it above.
* Fixed a related ordering slip: the plain-language button was stacked *above* the overlay,
  so it could overlap the panel. It now sits just below it.

= 1.4.6 =
* Fixed: on a phone, the comfort overlay's panel ran off the left edge of the screen when the
  button was set to "Middle right" or "Middle left", cutting the first characters off every
  label. Those two positions push the panel inwards to clear the button, and that clearance
  was never subtracted from the panel's width limit — so it wanted 420px of screen and a
  360px phone gave it 360. The four corner positions were never affected.
* The panel now also uses tighter padding and allows labels to sit closer to their controls
  below 480px, and scrolls rather than being clipped on a landscape phone.
* No feature behaviour changed. Only the panel's own size and spacing on small screens.

= 1.4.5 =
* A page containing no video is now returned completely untouched, without the caption
  scan running over it at all. That was true of the original product and had been lost in
  this port: every front-end page was being pattern-matched in full, whether or not it had
  any media. A site with no video anywhere is now provably byte-for-byte unchanged.
* Fixed a latent whole-page failure. If that pattern hit PHP's backtracking limit — which a
  long page containing an unclosed <video> tag can genuinely cause — the result was cast to
  a string, turning "no match" into an empty page. It now returns the page unchanged.

= 1.4.4 =
* Fixed: the overlay's contrast modes and background-colour option erased progress bars.
  Those modes force a background colour onto every element on the page — which is what makes
  them work on a themed site, and which also repaints an element whose background *is* its
  value. A progress bar's fill became the same colour as its track, so a bar at 100% looked
  identical to one at 0%. Meters and any element the page marks as role="progressbar" were
  affected the same way.
* Progress indicators now keep their own colours in every mode. The exemption is keyed on
  role="progressbar", <progress> and <meter> — what a page declares about itself — rather
  than on any one page builder's class names, so it works for Elementor, Bootstrap and
  hand-written bars alike.
* Note: these preferences are stored per visitor in the browser, so if a mode looked stuck
  on, "Reset all" in the overlay clears it.

= 1.4.3 =
* Fixed: the caption track was being added in the wrong place. A <video> element's content
  model is sources, then tracks, then fallback content — and WordPress's [video] shortcode
  writes an <a> link inside the element as a fallback, which Contao does not. Appending
  before </video> therefore landed the track after that link, producing invalid markup a
  player is entitled to ignore. It now goes directly after the last <source>, which is the
  same shape the original product produces.
* Caption files are now served by the plugin itself when the web server will not serve them
  as "text/vtt". Adding the type to .htaccess only works on Apache; on nginx, IIS, or a host
  whose configuration you cannot edit, subtitles could never appear. A public REST endpoint
  now streams the file with the correct header, and is used only when the direct URL is known
  not to work — so where the server can do the job, it still does.
* New option, Settings → AI provider → Video player: "Use the browser's own video player".
  WordPress normally substitutes its bundled MediaElement.js player; the browser's own one
  renders subtitle tracks natively, which is the arrangement the original Contao product had.
  Off by default, because it changes how every player on the site looks.

= 1.4.2 =
* Fixed the last reason approved subtitles stayed invisible, and it was not in the plugin's
  markup at all. Web servers do not know the .vtt extension out of the box — Apache's shipped
  mime.types has no entry for it — so the caption file was served with no Content-Type header,
  and both Chrome and Firefox refuse a subtitle track that is not served as "text/vtt". The
  file existed, the track element was correct, the video played, and there were no subtitles
  and no error anywhere.
* AccessPlus now adds the mapping to wp-content/uploads/.htaccess, on activation and after
  every approval, so it also repairs itself if a deploy or a security plugin replaces that
  file. The block is appended, never replacing what is already there, is wrapped in
  <IfModule mod_mime.c> so it cannot break a server that lacks the module, and is skipped
  entirely if the type is already declared.
* System status has a new "Caption delivery" row saying whether subtitles will actually
  reach visitors, with the exact line to add by hand on nginx, IIS, or an Apache install
  where uploads is not writable.

= 1.4.1 =
* Fixed: approved subtitles were written correctly but never appeared on the video. The
  `[video]` shortcode — what the classic editor's media button inserts — renders its source
  URL with a cache-busting `?_=1` appended, and the plugin took that whole string as a file
  path, so it never found the video and never added the caption track. Videos inserted with
  the block editor were unaffected, which is why this looked like it worked: which editor you
  had used decided whether captions appeared.
* Caption tracks are now also found when the page is served over https while the stored
  uploads URL is http (sites behind a proxy or TLS terminator), when the source URL is
  root-relative, and when the file name arrives percent-encoded.

= 1.4.0 =
* Failed AI requests now tell you what the provider actually said. Every rejection used to
  produce the same sentence — "the configured model does not accept this kind of request" —
  whatever the real cause, which was a guess stated as a diagnosis. The provider's own
  one-line explanation is now shown alongside it, with anything key-shaped redacted first
  (OpenAI's own error responses quote your key back at you) and never written to a log.
* Silent video is now detected before it is uploaded. A video with no audio track cannot
  produce subtitles, and sending one cost an upload to be told so. Such files are marked in
  the media list and given no button, exactly like files over the size limit, and the
  automatic batch skips them.
* Fixed: one oversized file used to stop the whole automatic batch. A property of a single
  file says nothing about the next one, so the run now skips it and carries on. Only a
  failure that would repeat for every remaining file — a rejected key, an exhausted quota —
  stops a run.
* Settings now shows the first and last few characters of the stored API key, so you can
  confirm which key is saved. The whole key is deliberately never printed: it would put a
  live credential into page HTML, browser caches, screenshots and screen shares in exchange
  for information the ends already give you.

= 1.3.1 =
* Fixed a fatal error when saving an API key on a server without the PHP sodium extension —
  which includes a stock XAMPP install, where the extension ships disabled. WordPress's bundled
  pure-PHP fallback encrypts perfectly well but refuses, by throwing, to scrub the encryption key
  from memory afterwards. The plugin treated that refusal as a failure of the save itself, so the
  request died after encrypting the key and before storing it: a white screen, and no saved key.
  Reading a key back had the same problem more quietly — it always came back as "no key set".
* Wiping the key from memory is now best-effort, as it should always have been. It is defence in
  depth; what actually keeps your key safe is the restricted key file and its separation from the
  database, and neither of those changes.
* The System status screen now says which implementation your server uses, and what the pure-PHP
  one cannot do, rather than leaving you to assume a guarantee you are not getting. If you can
  enable the `sodium` extension in your php.ini, do — you get the memory scrubbing back and
  noticeably faster encryption.

= 1.3.0 =
* The Subtitles screen now lists your audio and video files. Each one shows its size, whether the
  site actually uses it, and its own language picker and "Generate subtitles" button — so you
  caption the file you came to caption, instead of hoping an automatic batch reaches it.
* Files already carrying a draft show its status inline, with a link to the review area, and their
  button reads "Regenerate".
* Files larger than the 25 MB provider limit, and files whose bytes are missing from disk, are
  marked as such instead of being given a button that was always going to fail.
* Files that are uploaded but not embedded anywhere are now listed too. Previously the screen only
  ever considered files it could find on a page, so a video uploaded ahead of a page that had not
  been published yet was invisible.
* If your site is configured for more than one language, the screen gets language tabs and each
  file can be transcribed into any of them.
* The automatic batch button is still there, below the list, for working through embedded files
  without picking each one.

= 1.2.0 =
* "Show on page" now shows you the problem, not just the page. It opens the page the finding was
  reported on and draws a red box round the element itself, scrolled into view — so an image with
  no alt text is pointed at directly instead of leaving you to hunt for it.
* Image findings now open the page the image is used on, rather than the image file on a blank
  tab. If nothing on the site uses the image, the file is still offered.
* Heading and link findings are located by their text, so a report about "H4: What we do" lands on
  that heading.
* Where a finding cannot be pinned to a single element — a PDF, for instance — "Show on page"
  behaves exactly as before and opens the page. The button never guesses: if the page has changed
  since the scan and the element is gone, it says so rather than outlining something else.
* The preview only ever opens pages on your own site, and it uses no inline JavaScript, so it
  works under a strict Content-Security-Policy.

= 1.1.1 =
* Audited the plain-language (Easy Language) feature end to end. Four issues found and fixed:
* Fixed: the register controls in Settings showed the internal names "Einfach" and "Leicht"
  regardless of which naming you had chosen, so picking the English naming still displayed German
  ids. They now show the same names your readers see.
* Fixed: "Entry inside the comfort overlay" was a checkbox that did nothing. Plain language now
  appears as a control inside the comfort overlay panel when enabled.
* Fixed: "Nav-menu link" was also a checkbox that did nothing. It now adds a plain-language link
  to your navigation menus, with no inline JavaScript so it stays compatible with a strict
  Content-Security-Policy.
* Fixed: the "AI draft, not certified Easy Language" disclaimer on the reader-facing button was
  hardcoded in English, so it stayed English on a German site — the audience that most needs to
  read it. It is now translated along with everything else.
* Clarified in Settings that the reader toggles only appear once at least one draft is approved.

= 1.1.0 =
* Added a German translation. The comfort overlay and its settings now appear in German when your
  WordPress site language is German (de_DE, de_DE_formal, de_AT or de_CH). The feature names are
  taken verbatim from the original Contao product, so readers see exactly the same wording.
* Clarified a misleading setting. "Labels shown to readers" in the Plain language section sounded
  like a language switch for the whole widget; it only ever named the two readability registers.
  It is now called "What to call the two registers" and says so, and points at the WordPress site
  language setting for everything else.
* Fixed: the plugin shipped no translation files at all and the packaged zip did not include the
  languages folder, so every label fell back to English regardless of site language.
* Fixed: the "increase"/"decrease" button labels for the reading controls were built by joining two
  words in a fixed order, which cannot translate correctly. German now reads "Schriftgröße erhöhen"
  rather than a word-for-word transposition.

= 1.0.9 =
* Fixed: the overview screen could show two totals that disagreed. The headline ("N things to
  look at") counted only findings from the last content scan and was frozen at the moment that
  scan ended, while the score and the severity breakdown beside it counted content *and* page
  scan findings, live. Running a page scan after a content scan therefore left two different
  totals side by side with nothing explaining the difference. All three now come from a single
  query, so they cannot disagree.
* "How the work splits" genuinely does cover the last content scan only — it now says so,
  instead of leaving you to work out why its numbers do not add up to the totals above.

= 1.0.8 =
* Fixed: the Findings screen listed nothing, while the pagination above it correctly reported the
  real number of findings. The scan, the database and the query were all working — the table was
  being rendered with zero columns, so every row came out with no cells and the whole table was
  invisible. WordPress does not ask a custom list table for its columns unless the table declares
  them in a specific way, and that declaration was missing.
* Fixed: "First detected" was offered as a sort option on the Findings table even though there is
  no such column, so its sort link pointed at nothing. Sorting by first-detected still works when
  requested directly in the URL.
* Added a regression test for both, since neither showed up in any existing check: the code loaded,
  the queries were valid and nothing threw an error — the screen was simply blank.

= 1.0.7 =
* Fixed: the font-size stepper did nothing. It worked by changing the root font size, which only
  moves text sized in relative units — and Elementor and most WordPress page builders set explicit
  pixel sizes, so nothing moved. Font size is now applied to each piece of text individually and
  works on any theme.
* Headings stay larger than body text: each element is scaled from its own original size rather
  than everything being forced to one size, so the type hierarchy is preserved.
* Stepping up and back down returns text to exactly its original size, however many times it is
  adjusted — the original is measured once and never re-measured from an already-scaled value.
* Note: text loaded into the page after the stepper was last used (an AJAX section, infinite
  scroll) keeps its original size until the stepper is nudged again.

= 1.0.6 =
* Fixed properly: the background-colour picker now recolours the whole page, the way the dark and
  high-contrast modes do. The 1.0.5 attempt only cleared the background off a list of known theme
  wrappers, which was a losing game — there is always another theme with another wrapper name.
  The colour is now applied with the same selector the contrast modes use, so it works on any
  theme.
* As with those contrast modes, this means sections and cards lose their own background colours
  while a colour is selected, and background images are cleared so the colour is not patchy.
  Photos, video, SVG and canvas are left alone. Choosing "Standard" restores everything.

= 1.0.5 =
* Fixed: the background-colour picker appeared to do nothing. The colour was being applied
  correctly to the page body, but essentially every WordPress theme and page builder wraps the
  whole page in an opaque full-width container that paints straight over the body — so nothing
  was visible. The chosen colour now also clears the background off the theme's page wrapper, so
  it fills the page around your content the way it is meant to.
* Content sections, cards and footers that carry their own deliberate background colour are left
  untouched, so your design survives — only the page shell behind them changes.
* Note: this is an intentional difference from the Contao original, which only paints the body
  because that is sufficient on Contao. A theme using an unusual wrapper name may still hide the
  colour; see Documentation/Known-Limitations.en.md for the list of wrappers covered.

= 1.0.4 =
* Fixed: the reading guide never appeared, which also made "ADHD-friendly mode" look broken —
  that mode turns on the reading guide and stops animations, so with the guide invisible only
  half of it was observable. The guide's stylesheet rule used `display: none !important`, and an
  `!important` declaration cannot be overridden by the inline style the script was setting, so
  the guide was permanently hidden. Visibility is now toggled with a class instead.
  (The `!important` came from the 1.0.1 theme-isolation work; the reference implementation this
  widget is ported from used no `!important` at all, which is why it did not hit this.)
* Fixed: the colour-picker section headings ignored their intended styling for the same reason —
  an inline style losing to an `!important` rule — and rendered as accent-coloured group headers
  instead of plain sub-labels.
* Verified the three preset modes (epilepsy-safe, low-vision, ADHD-friendly) now compose exactly
  the same set of options as the reference implementation.

= 1.0.3 =
* Audited all 30 comfort-overlay features one by one. All were wired up, but five were broken
  in practice; all five are fixed:
* Fixed: the dyslexia-friendly font could never actually use OpenDyslexic, because the
  `@font-face` rule that loads it was missing — adding the font file would have had no effect
  at all. The rule is now present, so dropping the file into assets/fonts/ works as documented.
* Fixed: "Mute sound" un-muted audio and video that the *site* had muted deliberately when a
  reader switched the option back off. A background video with `autoplay muted` would stop
  playing entirely, because browsers refuse to autoplay unmuted media. Only elements the widget
  muted itself are now un-muted again.
* Fixed: the link-navigator dropdown had its native arrow stripped, leaving it looking like an
  empty box with no hint that it opens a list.
* Fixed: the widget's own panel and button grew or shrank along with the reader's "Font size"
  setting, because its chrome was sized in `rem` and that setting changes the root font size.
  The panel now stays a fixed size while the page text scales, as intended.
* The panel's own title, buttons and messages are now translatable like the rest of the plugin,
  instead of being hardcoded English in the JavaScript while the feature labels beside them
  were translatable. Relevant for non-English sites.

= 1.0.2 =
* Fixed: the comfort overlay could be switched on in Settings and still show nothing at all,
  with no explanation. The overlay deliberately renders nothing when no features are selected
  (an empty panel would be worse than none), but saving the settings form with every feature
  checkbox unticked produced exactly that state silently. The Settings screen now says so
  plainly, right under the Enable checkbox, and tells you what to do about it.
* Fixed: if the widget's stylesheet fails to load — a caching or asset-optimisation plugin
  serving a stale or stripped copy is the usual cause — the widget would lay out in the normal
  document flow at the very end of the page, adding a stray gap below the footer and reading as
  "this plugin broke my layout". It now detects that its own stylesheet did not apply, falls back
  to minimal corner positioning so it can never push the host page's layout around, and logs a
  console warning naming the likely cause.

= 1.0.1 =
* Comfort overlay: hardened the widget's own button/panel CSS against WordPress themes and
  page builders that style `button`/`select` elements globally. The reference design this
  widget is based on comes from Contao, whose themes do not typically clash this way; several
  WordPress themes do, and previously that could make the floating toggle render as a plain
  theme-styled button instead of the intended round accent-coloured control. Every widget-chrome
  rule is now scoped under `#vtap-overlay-root` with explicit resets and `!important`, isolating
  it from the host theme's styling.
* No functional changes — this is a visual-isolation fix only. If you already have this plugin
  installed, re-upload this version and do a hard refresh (or clear any page/CDN cache) so the
  browser fetches the updated stylesheet instead of a cached copy of the old one.

= 1.0.0 =
* Subtitles: transcribes embedded audio/video into a reviewable VTT draft, publishes an approved
  draft as a real caption file next to the source, and wires it onto matching `<video>` markup
  automatically. Files over 25 MB are rejected before upload.
* Plain language: drafts an easier-to-read rewrite of a passage, in either of two registers, with
  a labelled reader toggle. Approved drafts show only for readers who turn plain language on, in
  their own browser — your stored content is never changed.
* Comfort overlay: an opt-in, keyboard- and screen-reader-accessible widget giving visitors control
  over font size, spacing, contrast, motion, cursor size and more. Every feature is independently
  toggleable from one settings screen.
* PDF scan: checks every PDF linked from your content for a title, a declared language and a tagged
  structure, without ever modifying the file. Shown as its own finding category, separate from your
  score.
* Accessibility statement and feedback shortcodes: `[vtap_accessibility_statement]` assembles a
  statement page from fields you fill in, with a computed conformance-status suggestion you can
  accept or override. `[vtap_feedback_form]` gives visitors a way to report a problem, landing in
  a new Feedback inbox screen.
* Monitoring: re-scans your content automatically after a save (throttled, and never able to fail
  the save it is attached to) and once daily via WP-Cron, alongside the existing on-demand
  `wp accessplus scan` command.
* This release completes every feature in the port specification that was in scope. Multisite
  support remains explicitly out of scope, confirmed with the client; see Documentation/Known-Limitations.en.md for
  every feature's known constraints, including the two capability gaps this build could not close
  without internet access during development (no bundled OpenDyslexic font file, no bundled PDF-
  parsing library — both degrade honestly rather than silently).

= 0.7.0 =
* Accessible names: the page scan now guesses a name for icon links, unlabelled buttons and
  untitled frames, and you review each one before it is used.
* An approved name is applied wherever that element appears, so one approval covers a header or
  footer link across the whole site.
* A name is only ever added to an element that still has nothing to announce. It never replaces
  text somebody wrote, and it can be withdrawn at any time.
* Optionally asks the AI for a better name than the automatic guess. If that is unavailable for
  any reason, the automatic guess is kept and nothing is reported as broken.
* This is the first feature that adds anything to your public pages. A site with no approved
  names is completely unchanged — no script, no markup.

= 0.6.0 =
* Page scan: tests your published pages as a visitor actually receives them, after CSS and
  JavaScript have run. Catches colour contrast, focus behaviour and theme-generated markup that
  a content scan cannot see.
* The testing engine (axe-core 4.10.3, MPL-2.0) is bundled with the plugin. Nothing is fetched
  from a CDN and no page content leaves your server.
* Resumable: progress is saved after every page, so an interrupted scan continues instead of
  starting over.
* If any page could not be scanned, nothing is marked as fixed — a page the scanner could not
  read tells it nothing about the problems on it.

= 0.5.0 =
* AI-drafted alt text for images that have none. Every draft is reviewed beside the image it
  describes, and nothing is written until you approve it.
* Alt text that is already set — including a deliberately empty value marking an image
  decorative — is never overwritten.
* Undo on every applied draft, which refuses if the text has been edited since.
* Append-only audit trail of every automated write, recorded before the write happens.
* New WP-CLI command: wp accessplus generate-alt.

= 0.4.0 =
* Overview screen: score with its trend, outstanding findings by severity, and where the
  problems are concentrated.
* Findings report: filter by severity, check, scan type and free text; confirm, dismiss or
  reopen findings individually or in bulk; jump straight to the editor or the live page.
* Scan history, so you can see whether the site is getting better.

= 0.3.0 =
* Content scan: five deterministic checks — missing alt text, heading structure, vague link
  text, unlabelled form fields (Contact Form 7), and the theme's page-language declaration.
* Severity-weighted score, run history, and the three-way split of findings into fixed,
  guided-remedy and manual.
* Your triage decisions survive re-scans, and a check that fails never reports its old
  findings as fixed.
* New WP-CLI command: wp accessplus scan.

= 0.2.0 =
* AI provider layer: OpenAI and any OpenAI-compatible endpoint, including
  self-hosted servers. Nothing can reach the network while external requests are
  switched off.
* Settings screen for the provider, API key, base URL and model, plus a connection
  test that sends a single fixed word and none of your content.

= 0.1.0 =
* Foundation: database schema, configuration store, encrypted secret storage,
  network egress kill-switch (default on) and the system status screen.
