Navigation problems with binomial notation represented using <mmultiscripts>

Aperta
  • Qualcosa non va?
#823 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
68/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust, yaml
Ambito
accessibility

Direzione di ricerca

Reproduce the MathML example in NVDA with MathCAT 0.7.6-rc.3, then read the relevant into-or-out-of-mmultiscripts rules in navigate.yaml and the rules that skip none and mprescripts. Done means Enhanced/Simple navigation announces semantic parts rather than literal base/subscript roles, while Character mode avoids the redundant subscript transition.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug rules

Navigation of a binomial coefficient represented using <mmultiscripts> produces unexpected structural labels in all three navigation modes.

MathML

<math id="0" display="block" xmlns="http://www.w3.org/1998/Math/MathML">
    <mmultiscripts id="1">
        <mi id="2">C</mi>
        <mi id="3">m</mi>
        <none id="4"/>
        <mprescripts id="5"/>
        <mi id="6">n</mi>
        <none id="7"/>
    </mmultiscripts>
</math>

This represents a binomial coefficient with presubscript n and postsubscript m.

Settings

  • Language: English
  • Speech style: SimpleSpeak
  • Speech verbosity: Medium
  • Overview: False
  • Navigation verbosity: Verbose
  • Auto zoom out: True

Tested through NVDA with MathCAT 0.7.6-rc.3 installed as an addon.

Observed behaviour

Enhanced and Simple (identical)

  1. ZoomIn

    • land on id="6"
    • hear: "zoom in; in base; n"

  2. MoveNext

    • land on id="3"
    • hear: "move right; in subscript; m"

The landing order n → m appears correct for the inferred binomial semantics, but the structural labels do not.

MathCAT's binomial-mmultiscripts inference converts this expression into a semantic binomial whose children are n and m. Therefore n is no longer the literal base of the original <mmultiscripts>, and m is no longer being navigated as its literal postsubscript.

I would expect semantic navigation to describe these as arguments/parts of the binomial rather than as "base" and "subscript".

For example, with the current generic navigation behaviour for semantic structures, something approximately like:

  1. ZoomIn

    • land on id="6"
    • hear: "zoom in; in part 1; n"

  2. MoveNext

    • land on id="3"
    • hear: "move right; in part 2; m"

would seem more consistent.

Character

  1. ZoomIn

    • land on id="2"
    • hear: "zoom in; in base; c"

  2. MoveNext

    • land on id="3"
    • hear: "move right; in subscript; m"

  3. MoveNext

    • land on id="6"
    • hear: "move right; out of subscript; in subscript; in pre-subscript; n"

Character mode correctly follows the literal MathML structure and lands on the expected nodes.

However, the third announcement appears to contain a redundant structural transition:

"out of subscript; in subscript; in pre-subscript; n"

When moving from the postsubscript m across <none> and <mprescripts> to the presubscript n, I would expect something more like:

"move right; out of subscript; in pre-subscript; n"

or another equivalent transition that does not temporarily announce "in subscript" again.

Possible causes

There appear to be two potentially relevant areas in navigate.yaml.

For Enhanced/Simple, the inferred binomial still originates from <mmultiscripts>. The into-or-out-of-mmultiscripts navigation rule applies when:

@data-from-mathml='mmultiscripts'

and assigns roles according to literal child positions (base, subscript, superscript, etc.).

This may cause the two children of the inferred semantic binomial(n, m) to be incorrectly labelled as though they were still the first two children of the original <mmultiscripts>.

For Character mode, the rules that skip <none> and <mprescripts> perform additional Move2D/MoveNextZoom operations while moving to the following real script. This may be responsible for the extra "in subscript" announcement while crossing from the postscript to the prescript.

Disclosure: I asked ChatGPT for help to dig into the cause of this, so these guesses might well be wrong.

Lingua principale
Rust
Stelle
130
Fork
96
Merge medio
1g 1h
PR unite (30g)
84

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di daisy/MathCAT

Tutte le issue di daisy/MathCAT

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.