Skip to content

Conversation

@RokeJulianLockhart
Copy link

  • Each line actually has a \n, to adhere to CommonMark.

    This remediates inconsistent line-heights, and ensures that brs are replaced with ps, for WHATWG HTML LS conformance (and, thereby, WCAG AA).

  • Values, and their measures, conform to ISO 31-0.

  • Electronic values utilise IEC {60027-2 / 80000-13} / IEEE 1541-2002.

  • Erroneously absent commas and periods have been appended where relevant.

  • Quotation style has been made consistent; previously, double and single were utilised interchangeably, in the same sentence.

  • Some characters were replaced with semantic UTF counterparts:

    Original Replacement
    ~
    ...
  • <IDEA_HOME>” was replaced with “$HOME”, because it exists by default on Windows's (via PowerShell), and every Linux OS (via bash/sh).

    This means that users don't need to ascertain what their $HOME path is.

-	Each line actually has a `\n`, to adhere to CommonMark.

	This remediates inconsistent `line-height`s, and ensures that `br`s are replaced with `p`s, for WHATWG HTML LS conformance (and, thereby, WCAG AA).

-	Values, and their measures, conform to ISO 31-0.

-	Electronic values utilise IEC {60027-2 / 80000-13} / IEEE 1541-2002.

-	Erroneously absent commas and periods have been appended where relevant.

-	Quotation style has been made consistent; previously, double and single were utilised interchangeably, in the same sentence.

-	Some characters were replaced with semantic UTF counterparts:

	Original | Replacement
	---------|------------
	~        | ≈
	...      | …

-	“`<IDEA_HOME>`” was replaced with “`$HOME`”, because it exists by default on Windows's (via PowerShell), and every Linux OS (via `bash`/`sh`).

	This means that users don't need to ascertain what their `$HOME` path is.
@RokeJulianLockhart RokeJulianLockhart changed the title Improve accessibility and standard conformance in the README. Improve accessibility, ease of use, and standard conformance, in the README. Jan 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant