Tone Questions - Dyscalculia

Created on 8 May 2025, 4 days ago

Problem/Motivation

I had a odd issue trying to generate an Dyscalculia tone for CKEditor. I used this as a sample page.

https://www.fiscal.treasury.gov/reports-statements/financial-report/mda-...

I set up a taxonomy with the Dyscalculia, and came up with with:

Rewrite the text provide (including the links) but ensure that it is following the rules here:

  • Use words instead of numerals when possible – especially for small numbers (e.g., “three” instead of “3”)
  • Avoid using multiple numbers in a single sentence – separate complex ideas clearly
  • Explain numbers in context – clarify what they mean and why they matter
  • Use consistent number formatting – avoid switching between decimals, fractions, or percentages
  • Don’t assume numeracy – describe trends or insights in plain language, not mathematical shorthand
  • Avoid unnecessary precision – round numbers to whole numbers when it doesn’t change the meaning
  • Describe charts and data summaries in full sentences – explain what the numbers represent
  • Use comparisons and analogies – “twice as many” or “one in ten people” is easier to grasp than 10%
  • Provide units next to each number – like “12 months” instead of just “12”
  • Break long numbers with commas or spaces – use 1,000 instead of 1000 where appropriate
  • Use visual aids to reinforce number meaning – icons, color blocks, or annotated bars help
  • Group related data into categories – help reduce cognitive load
  • Avoid negative numbers if possible – reframe values to be positive if it aids understanding
  • Add explanatory text to image captions or data visualizations – don’t assume users can infer meaning
  • Don’t use Roman numerals – they are harder to process for many users
  • Explain mathematical terms – define things like “median,” “range,” or “percent change”
  • Use tables with row and column headers – and keep layouts consistent and clearly labeled
  • Offer text summaries for CSV files – describe key patterns, totals, and outliers in plain language
  • Do not change the meaning of the text or drop useful pieces of information.

When I select the text and then ask for

Dyscalculia's Look at Numbers

A look at the numbers, a bit like a complicated puzzle.

Numbers That Don't Add Up

It's like trying to understand a long list of figures (Financial Report), to get a grip on how the numbers might change. The Financial Report has a long look ahead (SLTFP), with notes (Note 24). It shows how the government's money might look over 75 years. For 2024 and 2023, the numbers are all over the place.

Steps to reproduce

Add that description for Dyscalculia into a taxonomy for the Tone.

This is using the Google Vertex Provider.

Run it by some text from https://www.fiscal.treasury.gov/reports-statements/financial-report/mda-...

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

💬 Support request
Status

Active

Version

1.0

Component

AI CKEditor

Created by

🇨🇦Canada mgifford Ottawa, Ontario

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @mgifford
  • 🇨🇦Canada mgifford Ottawa, Ontario

    I'm confused as to why Dyscalculia references keep getting added to the header:

    • A Wobbly Understanding of Numbers
    • A Challenging Understanding of Numbers
    • Dyscalculia: Number Recognition Challenges

    I have used this easily enough working for Dyslexia with:

    Write in plain language and following this guidance:

    • Use clear, plain language – avoid jargon, complex words, and abstract phrases
    • Break information into short, simple sentences – one idea per sentence
    • Avoid italic or all-uppercase text – these styles reduce readability
    • Use bold for emphasis – avoid underlining or italics for highlighting
    • Keep paragraphs short – 3 to 5 lines is ideal
    • Use bullet points or numbered lists – organize information clearly
    • Align text to the left – avoid justified or centered text blocks
    • Use consistent layout and formatting – avoid sudden changes in font, size, or color
    • Use headings and subheadings – help guide readers through the content
    • Include images or icons where helpful – reinforce meaning but avoid clutter
    • Don’t overcrowd the page – use white space to separate sections
    • Use consistent language – stick to the same terms for key concepts
    • Use clear and descriptive links – avoid “click here” or vague phrases

    Do not change the meaning of the text or drop useful pieces of information.

    And for Plain Language:

    Write in plain language, following the guidance in https://www.plainlanguage.gov/

    • Use short sentences – aim for an average of 15–20 words per sentence
    • Use common, everyday words – replace jargon or technical terms with simpler alternatives
    • Explain necessary technical terms – define complex words clearly and immediately
    • Use active voice – make the subject do the action
    • Use personal pronouns – favor “you,” “we,” and “us” when appropriate
    • Stick to one idea per sentence – break up complex or compound sentences
    • Group related ideas together – keep similar information in the same paragraph
    • Use descriptive headings – help readers scan and find what they need
    • Avoid acronyms and abbreviations unless well known – spell them out or remove them
    • Use bulleted or numbered lists – organize information for easier reading
    • Use positive language – say what people should do, not just what they shouldn’t do
    • Avoid legal or bureaucratic terms – replace with clear, direct language
    • Use consistent terminology – don’t switch between synonyms without reason
    • Write for reading level Grade 8 or below – use readability tools to check
    • Include examples where useful – clarify abstract ideas with concrete examples
    • Avoid metaphors or idioms – keep language literal and clear
    • Prefer verbs over nouns – say “decide” instead of “make a decision”
    • Use clear formatting – left-aligned text, short paragraphs, and white space
    • Define numbers clearly – write out one to nine, use numerals for 10 and above
    • Test for understanding – ensure someone unfamiliar with the topic can understand it on the first read
    • Use American English unless otherwise specified

    Do not change the meaning of the text or drop useful pieces of information.

Production build 0.71.5 2024